MuleSoft Accelerator for Salesforce B2C Commerce Cloud
Use case 4 - Order status update
Overview
The following use case is covered:
- Order status update (B2C Commerce <- OMS)
This use case shows you how to update order-status in B2C Commerce with changes that originate in the external OMS.
Order management systems don't all emit events when orders are created or modified. OFBiz does not emit events which means that polling is needed to detect any changes to the status of orders.
On a configurable scheduled basis, poll for status updates in the OMS using an API. Push any status updates (since the last watermark timestamp) to B2C Commerce.
High-level architecture
Workflow
- The scheduling service (a common service component) triggers calls to the Orders Process API to retrieve recently modified orders.
- Orders Process API retrieves the list of orders updated since the last run from OMS.
- For each of the orders in the returned list, update B2C Commerce with the order status retrieved from the backend OMS.
Sequence diagram
Systems involved
- Apache OFBiz OMS
- B2C Commerce
Setup instructions
Mule projects
- Order Process API | API Specification | Implementation Template
- B2C Commerce System API | API Specification | Implementation Template
- OMS System API | API Specification | Implementation Template