Integration points

  • Catalog/prices
  • Stock events
  • Orders inbound
  • Shipment status outbound

Reliability

Queues, idempotency keys, nightly reconciliation.

Mapping and master data

Order statuses, SKU and price types need a written mapping table. Idempotency on order webhooks; dead letter on failure; seven-day nightly reconciliation. Staging 1C plus staging shop before production.

Multichannel

  • CommerceML for catalog batch
  • REST or events for realtime orders
  • Orchestration layer if Ozon/WB also sell stock
  • Returns and partial shipments as separate statuses

Five to ten days for production-grade exchange is realistic with prepared 1C. Support without field mapping docs fails within six months — document in Confluence from day one.

Order API integration