When the shop and the back office do not talk

In many PrestaShop shops the same order is handled several times: typed into the accounting or ERP system, turned into an invoice by hand, booked with a carrier, and the tracking number copied back for the customer. Stock is corrected in two places and drifts apart between corrections. Each step is small, but together they cost hours every week and produce errors that often surface only when a customer complains.

What we connect

Each flow can run in one direction or both, in real time or on a schedule.

  • Orders

    New and changed orders flow from PrestaShop to the ERP or accounting system, with their lines, taxes and status.

  • Customers

    Customer and address records are created or matched in the back office, so the same customer is not entered twice.

  • Invoices

    Invoices are generated from the order data in the system responsible for them, instead of being typed by hand.

  • Stock and prices

    Stock levels and prices held in the ERP are pushed to the shop, so the shop does not sell what the warehouse no longer has.

  • Shipments and tracking

    Shipments are booked with the carrier and the tracking number is written back to the order in PrestaShop.

How we work

  1. 1

    Written scope

    You describe the systems, versions and data flows; we reply with a written scope of what will be connected and how.

  2. 2

    API review

    We review the APIs of both systems: what they expose, their limits and how they authenticate.

  3. 3

    Field mapping

    A mapping table lists every field that moves, in which direction, and how values such as tax codes and statuses translate.

  4. 4

    Test shop

    The integration runs first against a test copy of the shop and test credentials for the back-office system.

  5. 5

    Staged go-live

    Flows are switched on one at a time on the live shop, starting with the lowest-risk one.

  6. 6

    Monitoring and retries

    Failed calls are logged and retried, and anything that still fails is reported instead of being lost silently.

What we have delivered

Two published projects, both completed.

  • PrestaShop, Netsis and four carriers

    A two-way integration between a PrestaShop shop and Netsis Accounting for orders, invoices and stock, plus shipment handling with Aras, PTT, Sendeo and MNG Cargo, built on Python APIs.

    Read the case study

  • Marketplaces and Netsis

    Real-time transfer of stock, journal records, orders, e-invoices and e-waybills from Trendyol, Hepsiburada, N11 and GittiGidiyor into Netsis, with background job processing and token-based authentication.

    Read the case study

Epicor, NetSuite, Acumatica, SYSPRO and other systems

Shop owners ask us about these systems. We have not delivered integrations with them, and this page does not claim that we have. Whether and how a PrestaShop shop can be connected to one of them depends on the API it offers, so send us the system name, version and plan: we review its API documentation and reply in writing. Our article on one method for PrestaShop ERP integration describes the approach.

Still on PrestaShop 1.7?

PrestaShop 1.7 is no longer maintained. PrestaShop announced that its maintenance would end when PrestaShop 9.0.0 was released, and 9.0.0 shipped on 10 June 2025. PrestaShop 1.7.8 also does not run on PHP 8: its official requirements stop at PHP 7.4, which itself left security support in November 2022. When your host retires PHP 7.4, a 1.7 shop has no supported way to stay online. The way forward is PrestaShop 8.x, which runs on PHP up to 8.1, or 9.x, which runs on newer PHP 8 releases. If your shop is connected to an ERP or to carriers, the upgrade also means re-testing those connections, which is the kind of work described in our PrestaShop, Netsis and carriers project.

PrestaShop integration questions

Not to begin with. We build and test against a copy of the shop or a staging environment, with test credentials for the ERP, accounting or carrier system. Live access is needed only for the staged go-live, and only for the flows being switched on.

Often, but it depends on the other system. Where the ERP or carrier offers a usable API, we connect to it directly; where it does not, a connector or a sync at the data level may be needed. Which of the two applies to your systems is stated in the written review, before any build starts.

No. PrestaShop 1.7.8 supports PHP up to 7.4 and is no longer maintained, so the supported path is an upgrade to PrestaShop 8.x or 9.x. Any ERP or carrier connections should be re-tested as part of that upgrade.

Yes. We work remotely and in writing, so the shop does not need to be in Belgium. The delivered projects on this page connect to Netsis, an accounting system used in Turkey.

Tell us which systems your shop needs to talk to

Send the PrestaShop version and the name, version and plan of each system. We reply in writing with what can be connected and how.

Describe your systems