Define the source of truth
Specify where products, prices, availability, invoices and order statuses are owned. Two applications must not overwrite each other unpredictably. For each data field, document ownership, update direction, frequency and conflict resolution.
Keep reference mapping explicit
Product IDs differ between systems and environments. Maintain stable external identifiers and a documented mapping table. SKUs may contain characters such as +, accents and spaces; do not normalise them silently. Packs may require a separate mapping from sellable bundles to ERP components.
Export at the correct order status
An order placed is not always an order approved for invoicing. Choose the trigger according to payment and business validation. Assign an export identifier and acknowledgement. Ensure retries are idempotent so that network failures cannot produce duplicate ERP orders.
Transmit complete commercial data
Check billing and shipping details, applicable VAT, discounts, shipping costs, currency, quantities and line totals. Compare rounding and grand totals across systems. Define how refunds, credit notes and later changes are handled.
Synchronise stock safely
Clarify whether inventory is ERP-led or bidirectional. Distinguish physical, reserved and available stock. Handle variants, inactive items and packs, and prevent older updates from overwriting newer states.
Select integrations deliberately
PrestaShop 9 documents an OAuth-based Admin API as well as a Webservice API. Hooks can signal events while scheduled jobs support longer processing and recovery. Review permissions, authentication, timeouts and limits for the version in use.
Build observable recovery
Expose pending, successful and failed exchanges with useful error reasons. Bound retries and offer controlled manual replay. Test discounts, B2B orders, packs, cancellations and ERP outages before enabling automatic flows.
Review checklist
- Define authoritative systems
- Map external references
- Select order trigger status
- Implement idempotent retries
- Monitor failures
Related guides on Concepty
- Custom PrestaShop modules: from business need to safe deployment
- PrestaShop B2B quick ordering: entering SKUs and quantities
- E-commerce technical audit: what to check before sales suffer
Practical next steps
Before making changes, record your versions, business constraints and reproducible issues. I can help with custom web development, or you can describe your project on the contact page. The goal is a tested, maintainable improvement rather than another unnecessary dependency.