BPMN Studiov2.0
ContentsOverview

BPMN Guides

OverviewWhat is BPMN?How to create a BPMN diagramBPMN symbolsGatewaysEventsPools and lanesBPMN vs flowchartBPMN vs UML activity diagramCommon mistakes

Templates

OverviewOrder-to-cashEmployee onboardingInvoice approvalSupport ticket handlingProcure-to-payLoan applicationIncident managementHiring / recruitmentOrder fulfillmentExpense reimbursement

Comparisons

Overviewvs Bizagi Modelervs BPMNifyvs Just Flow Itvs Lucidchart

Alternatives

Overviewbpmn.io alternativesCamunda Modeler alternativesVisio alternatives

Blog

OverviewBest AI BPMN Generators 2026Which BPMN Studio?

General

About BPMN StudioBPMN Studio — frequently asked questionsBPMN Studio pricingCookie PolicyEmilis MikalajūnasPrivacy PolicyTerms of Service

Order fulfillment BPMN diagram example

By Emilis Mikalajūnas · Published July 8, 2026 · Last updated October 3, 2026

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.

Order fulfillment BPMN 2.0 diagram across System, Warehouse and Fulfilment lanes: a payment-confirmed message start event, an in-stock exclusive gateway, a parallel gateway splitting reserve-stock and generate-shipping-label that re-join at a parallel join, pick and pack, dispatch with a carrier, send tracking to the customer, ending at a delivery-confirmed message end event and a back-order end event.
E-commerce order fulfillment in BPMN 2.0 with parallel warehouse work and a message end event. Generated with BPMN Studio. How it was made: the description, steps table and decision points below were sent unedited through BPMN Studio's production generation prompt (GPT-4.1), then laid out by the app's own layout engine.

Take this diagram with you. The BPMN 2.0 XML below is the exact source behind the diagram above — open it in Camunda Modeler, Flowable, Activiti, bpmn.io, or any BPMN 2.0 tool.

↓ Download Order fulfillment .bpmnOpen in BPMN Studio

Free, no sign-up, no attribution required.

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

The middle column names each BPMN element; the BPMN symbols and shapes reference shows what each one looks like.

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

When should a fulfilment process end with a message end event?

When finishing the process has to tell another participant something, such as confirming delivery to the customer or an ERP system. A plain end event only closes the path; a message end event closes it and sends the message.