Understack
Let’s talk about a project

PrestaShop development

PrestaShop is manageable when someone knows it from the inside.

PrestaShop development for agencies: custom modules instead of scattered overrides, themes built on your design, ERP and e-invoicing integrations, upgrades to the current version. White label, with the checkout tested on staging before every release.

Request a quote All services

The problem with PrestaShop is rarely PrestaShop: it is the overrides left by whoever came before.

The shops we take over tell the same story: features added by copying files into the override folder, third-party modules overwriting each other, and a version stuck at 1.6 because upgrading feels dangerous.

That is where the real work starts: what is needed becomes a module, with its own hooks, that the next upgrade will not wipe out. The rest is removed.

Before touching an existing shop we measure it: version, active modules, overrides, catalogue response times.

What we deliver

Everything between the catalogue and the fulfilled order, written so the next upgrade does not erase it.

  • 01

    Custom modules

    A missing feature becomes a module with its own hooks and settings, not a file copied into overrides.

  • 02

    Theme and product page

    Catalogue, product page, cart and checkout built on the project design, not on a bought theme bent into shape.

  • 03

    ERP integrations

    Products, stock, orders and customers synced through the webservice or an API, with error handling and re-alignment.

  • 04

    Electronic invoicing

    Orders that become invoices in the required format, with tax data collected at the right step of the checkout.

  • 05

    Upgrades to current versions

    From 1.6 or 1.7 to PrestaShop 8: data, modules and customisations, with the old shop running until the switch.

  • 06

    A catalogue that responds

    Queries, cache and filters measured on real catalogues: a shop with ten thousand references is not tested with ten sample products.

How we work

An online shop does not stop for a release. The flow is built for that.

  1. Analysis

    Version, modules, overrides, integrations and catalogue size. If the shop already exists we measure it first and tell you what to fix, and in which order.

  2. Development

    Locally, with Git and a copy of the real data. No edits on the live shop, no files uploaded over FTP.

  3. Staging with realistic data

    The shop runs on a separate environment, where you and your client test orders, payments, shipping and invoices.

  4. Controlled release

    Only the approved version goes live, in an agreed window, and the checkout is verified right after.

What we build it with

PrestaShop the way PrestaShop intends it: modules, hooks and its webservice, without shortcuts an upgrade would erase.

  • PrestaShop
  • PHP
  • JavaScript
  • MariaDB
  • nginx
  • Git

Frequently asked questions

  1. Do you work on an existing PrestaShop shop?
    Yes, and that is the most common case. We analyse it first — version, modules, overrides, response times — and tell you what to fix and in which order, starting with what costs orders.
  2. We are still on 1.6. Can it be upgraded?
    Almost always, but it is not one click: data, modules and customisations are migrated, and anything that was an override is rewritten as a module. The old shop stays up until the new one is approved.
  3. Why a module instead of an override?
    Because an override is a file that replaces the core: the first upgrade removes it or puts it in conflict with another module. A module with its own hooks survives upgrades and can be switched off without breaking anything.
  4. Do you handle multistore?
    Yes: several shops on one installation, with different catalogues, languages and price lists. It is also where a badly written module shows immediately.
  5. Do you also do WooCommerce?
    Yes, and we have no preference to sell: for a new project we tell you which of the two fits, based on the catalogue, the integrations and who will run it every day.
  6. Do you also handle hosting for the shop?
    If you want, yes, with managed hosting: the team that develops knows the server, so nobody passes the problem along. It is an option, not a condition.

The same team, for the rest of the work.

  • 01

    Figma to WordPress

    From the design file to a custom WordPress theme, true to the layout and easy for the client to edit.

  • 02

    Custom WordPress theme

    Markup written for the project, structured content and an admin the client can use without breaking the layout.

  • 03

    Custom WordPress plugin

    Integrations, APIs and business logic that a generic plugin only half covers.

  • 04

    WooCommerce development

    Custom e-commerce: price lists, pricing rules, ERP, shipping and payment integrations.

  • 05

    Dedicated WordPress developer

    Development capacity reserved for your agency every month, inside your tools and your processes.

  • 06

    WordPress maintenance

    Updates tested before they go live, backups, security and monitoring, under your agency’s name.

  • 07

    Managed hosting

    Dedicated servers on a WordPress-tuned stack, configured and maintained by the people who build the sites.