PrestaShop Acumatica integration
OpusNext connects PrestaShop to Acumatica through the contract-based REST API, mapping your real Acumatica data - stock items, units of measure, customer price classes and sales price worksheets - onto PrestaShop products, combinations and customers. Pricing stays in Acumatica, and orders flow back as they are placed. Typical go-live is 2 to 6 weeks.
What syncs between Acumatica and PrestaShop
| Data | Direction | What it means |
|---|---|---|
| Stock items & combinations | Acumatica → PrestaShop | Combinations built from real item data |
| Customer price classes | Acumatica → PrestaShop | Each customer sees their contracted price |
| Warehouse availability | Acumatica → PrestaShop | Stock reflects the warehouse that ships |
| Orders | PrestaShop → Acumatica | Created in Acumatica as they are placed |
| Invoices & shipments | Acumatica → 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.
Acumatica prices through customer price classes and sales price worksheets with effective dates. PrestaShop has its own specific prices table. Run both and you end up with two pricing systems that quietly disagree - and the shop is usually the one that is wrong.
We leave Acumatica as the single pricing authority and resolve the buyer price there - price class, active worksheet, quantity, date and currency - so PrestaShop displays exactly what Acumatica will invoice.
Units of measure are where distribution orders go wrong. Acumatica keeps base, sales and purchase units with conversions; PrestaShop just sells a combination. Sell in the wrong unit and both the quantity and the price are wrong.
We carry the Acumatica unit conversions through to the shop, so a customer ordering a case gets a case - priced, counted and shipped correctly.
Acumatica's contract-based REST API and generic inquiries are powerful but specific, and multistore adds another dimension. A connector that ignores either ends up slow, or serving the wrong catalogue to the wrong shop.
We integrate through the contract-based API and inquiries with delta updates, and map each PrestaShop store to its own price class, warehouse and currency.
Before you choose a PrestaShop connector
Five questions worth asking any vendor - and our answers for Acumatica.
OpusNext: Yes. Custom fields and attributes on Acumatica stock items are read and mapped, confirmed with you before go-live.
OpusNext: Resolved in Acumatica per customer price class and active sales price worksheet, with quantity, date and currency.
OpusNext: Event-driven with delta updates, so orders and stock move as they happen rather than on a nightly schedule.
OpusNext: No. We connect directly to Acumatica through its contract-based REST API - no middleware to license or host.
OpusNext: Upgrades are absorbed through the official API, and the mapping re-checks itself when your Acumatica schema changes.
PrestaShop and Acumatica - common questions
Does OpusNext use PrestaShop specific prices?+
No. Acumatica stays the pricing authority and the buyer price is resolved there, so the shop shows what Acumatica will actually invoice.
Are Acumatica units of measure supported?+
Yes. Base, sales and purchase unit conversions are carried through, so ordering a case behaves like a case in both systems.
Can one Acumatica serve several PrestaShop stores?+
Yes. Each store is mapped to its own price class, warehouse and currency.
How fast do PrestaShop orders reach Acumatica?+
In seconds. Orders are created as they are placed, with the customer matched or created in Acumatica.
Is stock synced per warehouse?+
Yes, availability is synced per Acumatica warehouse so the shop shows what is genuinely sellable.