Integrations and Data Model
What to know
Order Management integrations connect external commerce, ERP, inventory, and payment systems. Candidates must know the core data model: Order Summary → Order → Order Item Summary/Order Item → Fulfillment Order → Fulfillment Order Line Item, plus related Invoice, Payment, and Return objects. Understand parent-child relationships and which object is the "summary" aggregate versus the operational detail.
Know the integration patterns: REST APIs, platform events, and bulk/data loads. Understand that order data often originates in an external commerce system and is ingested into Order Management, while fulfillment and inventory events flow back out. Know the role of external IDs and correlation IDs for matching records across systems.
Traps
- Reversing the summary/detail relationship (Order Summary is the aggregate; Order is the operational record).
- Assuming Order Management is the system of record for orders - often the commerce platform is.
- Forgetting that integrations are event- and API-driven, not just batch.
- Overlooking external ID mapping, which causes duplicate or orphaned records.
Rule of thumb
When a question asks "which object links an order to what ships," trace the chain: Order → Fulfillment Order → Fulfillment Order Line Item. Each hop represents a level of operational granularity.
Worked example
An external storefront creates an order. It is ingested via API into Order Management, creating an Order Summary and Order. On activation, orchestration creates Fulfillment Orders and line items. Fulfillment status events flow back via platform events, updating the Order Summary so the storefront can display status.