PrestaShop merchants running ERPNext usually end up maintaining two disconnected systems. Product catalogues, combinations and prices live in PrestaShop; stock, accounting, purchasing and fulfilment live in ERPNext. Without a connector, staff re-key web orders into Sales Orders by hand, oversell because stock levels drift, and reconcile customer records across two databases. ERPNext core has no native PrestaShop integration and no webhook consumer for the PrestaShop Webservice API, so this gap does not close on its own.

The ERPNext PrestaShop Connector is a purpose-built Frappe application (its own app on the bench, with dedicated DocTypes, hooks.py doc events and scheduler entries) that ECOSIRE builds and tailors to your store. It talks to the PrestaShop Webservice REST API and mirrors the flow into ERPNext's REST API and whitelisted methods. A configurable Connector Settings DocType holds the shop URL, API key and field mappings; per-run activity is written to a Sync Log DocType so every create/update is traceable and re-runnable. Product and combination changes map to ERPNext Item and Item Variant records with attributes and categories preserved; incoming PrestaShop orders become ERPNext Sales Order and, where you want it, Sales Invoice documents with the matching Customer and Address created or matched first.

Technically, the sync runs on two paths. Near-real-time events (a new order, a stock movement) are handled through webhooks and server-side controllers, while a scheduled reconciliation job — registered under scheduler_events and running via the Frappe worker/queue — sweeps for anything missed and keeps price and inventory two-way consistent. hooks.py doc_events on ERPNext Item, Stock Ledger Entry and price documents push ERPNext-side changes back out to PrestaShop, so an inventory adjustment or price change in ERPNext updates the storefront without manual export. Access is governed by proper Role Profiles and permission rules so only authorised users can change mappings or trigger a full resync, and client scripts add the resync and mapping controls into the ERPNext desk UI. We build against Frappe/ERPNext v15 and v16.

Because this is build-to-order, nothing ships as a blind download. We start with a scoping call to confirm your PrestaShop version, single vs. multi-shop layout, tax and price rules, and how you want orders to land in ERPNext. We then build your version of the connector, prove it on a staging bench with your real catalogue during UAT, and only cut over to production once the flows are signed off. Typical delivery is one working week from confirmed scope, and you receive the full source and git repository so the app is yours to keep and extend.