PrestaShop SAP Business One integration
OpusNext connects PrestaShop to SAP Business One through the web service API, with AI mapping your real B1 items, user-defined fields and price lists onto PrestaShop products, combinations and customers. Orders flow back into B1 as they are placed, and pricing stays where it belongs - in B1. Typical go-live is 2 to 6 weeks.
What syncs between SAP B1 and PrestaShop
| Data | Direction | What it means |
|---|---|---|
| Products & combinations | B1 → PrestaShop | Combinations built from real B1 item data |
| Customer pricing | B1 → PrestaShop | Each customer sees their own B1 price |
| Stock by warehouse | B1 → PrestaShop | Availability matches the shipping warehouse |
| Orders | PrestaShop → B1 | Created in B1 as they are placed |
| Invoices & shipments | B1 → PrestaShop | Customers follow their own orders |
Where PrestaShop projects usually go wrong
The parts that decide whether this integration ages well - and how we handle them.
PrestaShop specific prices look like B1 pricing but are a separate table - per customer, group, quantity and date. Two pricing systems running side by side drift, and the shop quietly starts quoting numbers your invoices do not agree with.
We leave B1 as the single pricing authority and resolve the buyer price there, so PrestaShop displays what B1 will invoice instead of a copy that ages.
Combinations rarely map cleanly. B1 keeps variant logic in item codes and user-defined fields; PrestaShop expects attributes and combinations, and a naive import either explodes the catalogue or collapses it.
The engine reads your real B1 item structure and we agree which fields become attributes, which become combinations and which stay informational - before the catalogue goes live.
Multistore multiplies everything. Different shops, currencies and customer bases, one B1 behind them, and a connector that only understands a single shop context.
Each shop is mapped to its own B1 price list, warehouse and currency, so one B1 can serve several PrestaShop stores without contradicting itself.
Before you choose a PrestaShop connector
Five questions worth asking any vendor - and our answers for SAP B1.
OpusNext: Yes. User-defined fields and tables are read and mapped into products and combinations, confirmed with you first.
OpusNext: Resolved in B1 per business partner, price list, quantity and currency - PrestaShop specific prices are not used as a shadow price list.
OpusNext: Event-driven, so orders and stock move as they happen rather than on a schedule.
OpusNext: No. We connect directly to B1 via the Service Layer or DI API - nothing extra to license or host.
OpusNext: We integrate over the official web service API, and the B1 mapping re-checks itself when your schema changes.
PrestaShop and SAP Business One - common questions
Does OpusNext support PrestaShop multistore?+
Yes. Each shop is mapped to its own B1 price list, warehouse and currency so several storefronts can run from one B1.
How are PrestaShop combinations mapped to SAP Business One items?+
We read your real B1 item structure, including user-defined fields, and agree with you which fields become attributes and combinations before the catalogue is published.
Do you use PrestaShop specific prices?+
No. B1 stays the pricing authority and the buyer price is resolved there, so the shop shows what B1 will actually invoice.
How fast do PrestaShop orders appear in B1?+
In seconds. Orders are created in B1 as they are placed, with the customer matched or created as a business partner.
Is stock synced per warehouse?+
Yes, availability is synced per B1 warehouse so the shop reflects what is really sellable.