Order fulfillment BPMN diagram example
Order fulfillment is the warehouse-and-logistics half of getting a product to a customer — a common BPMN example for e-commerce, and the one many AI tools quote for a Shopify-style flow.
The process in plain English
Once payment is confirmed, the warehouse reserves stock and prepares a shipping label in parallel, then picks and packs the order and dispatches it with a carrier. The customer gets tracking, and the process completes when delivery is confirmed. If an item is out of stock, a back-order path handles it.
Steps and their BPMN elements
| Step | BPMN element | Lane |
|---|---|---|
| Payment confirmed | Message start event | System |
| In stock? | Exclusive gateway | Warehouse |
| Split preparation | Parallel gateway | — |
| Reserve stock | Service task | Warehouse |
| Generate shipping label | Service task | Fulfilment |
| Synchronise | Parallel join | — |
| Pick & pack order | User task | Warehouse |
| Dispatch with carrier | Service task | Fulfilment |
| Send tracking to customer | Send task | System |
| Delivery confirmed | Message end event | — |
| Trigger back-order | End event | — |
Key modelling points
- The parallel gateway (reserve stock + label at once) reflects how warehouses actually work.
- An in-stock gateway upfront routes the back-order exception.
- The message end event captures the external delivery confirmation.
Generate your own fulfillment diagram
Describe your warehouse steps and carrier flow to BPMN Studio for an editable BPMN 2.0 diagram, exportable for Camunda or Flowable. More templates · order-to-cash example.
Frequently asked questions
How do you model order fulfillment in BPMN?
Trigger with a message start event (payment confirmed), then a parallel gateway to reserve stock and prepare shipping label at once, a pick-and-pack user task, a dispatch service task, and a message end event when delivery is confirmed. An out-of-stock gateway handles the exception.