🔗 OMS — Integration Patterns¶
Outbound Integrations¶
Integrations where OMS is the initiating party.
| Target | Style | Trigger | Description |
|---|---|---|---|
| SIM | 🔄 Synchronous API | order-confirmed |
When an order is confirmed, the OMS calls the SIM to soft-reserve inventory for each order line. Ensures ATP is reduced |
| FMS | 📨 Event-Driven | order-confirmed |
On order confirmation, the OMS publishes an order-confirmed event that the FMS consumes to create a Fulfillment Order. D |
| Payment Hub | 🔄 Synchronous API | order-confirmed |
After order confirmation, the OMS instructs the Payment Hub to capture a previously authorised payment. Synchronous to e |
| Loyalty Platform | 📨 Event-Driven | order-completed |
When an order reaches completed state, the OMS publishes an order-completed event. The Loyalty Platform consumes it to c |
| Promotion Engine | 🔄 Synchronous API | order-created |
At order creation, the OMS validates applied promotions and vouchers with the Promotion Engine to prevent fraud and doub |
| CRM | 📨 Event-Driven | order-completed |
Completed orders are published as events and consumed by the CRM to update the customer's purchase history, lifetime val |
Inbound Integrations¶
Integrations where OMS is the receiving party.
| Source | Style | Trigger | Description |
|---|---|---|---|
| eCommerce Platform | 🔄 Synchronous API | checkout-completed |
When a customer completes digital checkout, the eCommerce Platform submits the validated basket to the OMS to create a c |
| POS | 🔄 Synchronous API | transaction-completed |
When a POS transaction is completed, the POS creates an order in the OMS for stock reconciliation, receipt generation, a |