Skip to main content
A.I. Commerce Studio

E-commerce

Shop and ERP synchronisation

Orders, stock and prices are synchronised between the online shop and the ERP with events and checks.

Fictional scenario. An example situation that illustrates the approach. It is not a client project and describes no measured results.

Business problem

A fictional shop keeps stock in the ERP and orders in the platform. Manual synchronisation leads to selling items that are out of stock.

Assumptions

  • The platform has webhooks and an API.
  • The ERP is the master system for stock and prices.
  • There is a test shop.

Constraints

  • No duplicate orders.
  • The ERP stays the system of record.
  • Synchronisation is idempotent.

Reference architecture

Components by stage — an illustration, not a running system and not a certified design.

  1. 01Events

    • Shop webhooks
    • ERP changes
  2. 02Integration

    • Queue
    • Idempotent processing
  3. 03Rules

    • Item mapping
    • Stock checks
  4. 04Targets

    • Orders in the ERP
    • Stock and prices in the shop
The diagram as a list
StageComponents
EventsShop webhooks, ERP changes
IntegrationQueue, Idempotent processing
RulesItem mapping, Stock checks
TargetsOrders in the ERP, Stock and prices in the shop

Interfaces

FromToVia
ShopQueueSigned webhook
ProcessorERPREST API
ERPShopStock API

Data flow

  1. A new order sends a signed webhook.
  2. The processor verifies the signature and idempotency.
  3. The order enters the ERP once.
  4. Stock changes are published back.
  5. Mismatches are reported.

Security boundaries

  • Every webhook signature is verified.
  • Separate keys for reading and writing.
  • No payment data in the integration.

Where a person approves

  • Bulk price changes.
  • New mapping rules.

Delivery phases

  1. 01 · Discovery

    Flows, master systems, volumes.

  2. 02 · Pilot

    Read-only stock.

  3. 03 · Integration

    Orders and prices.

  4. 04 · Operation

    Queue and mismatch monitoring.

Limitations

  • Depends on API limits.
  • Complex variants need a clear mapping.

Trade-offs

  • Events vs periodic sync.
  • ERP as the master system: slower price changes.

Facing something similar?

We start with an assessment of where you are and propose a realistic first phase.