6. Order Delivered
Step 6 occurs when the order has been delivered to the customer and the receipt is confirmed. This step provides proof of delivery and marks the completion of the logistics part of the Order-to-Cash cycle. The Log Event for this step stays in the Logistics Domain.

Animated walkthrough: in BPM Log Search, open Show Details on the Order Delivered event of order ORD-10005 (Tailspin Toys), then the Context Values tab with the step's business data. The walkthrough shows ORD-10005; the examples below use order 1.
Understanding Step 6
WMS (Logistics)"] --> This["fa:fa-truck Step 6: Order Delivered
WMS (Logistics)"] This --> Next["fa:fa-file-invoice-dollar Step 7: Order Invoiced
ERP-Finance (Finance)"] This -->|"Log Event
O2C.Order.Delivered/1.0"| LogAPI["fa:fa-cloud-arrow-down Log API"] style Prev fill:#2678BD style This fill:#E47528 style Next fill:#2678BD style LogAPI fill:#3F827B
Step 6 (orange) closes the logistics part: it follows packing, triggers invoicing (blue), and logs to the Log API (teal).
Message Details
- Message Type:
O2C.Order.Delivered/1.0(Message Types) - Domain: Logistics (Domains)
- System: WMS (Systems)
- Service: INT1337-RCV-Order-Delivered (Services); despite the
RCVprefix, this is the Send Service of the step - Direction: Send (outgoing from WMS)
- Format: Flat File (PSV - Pipe-Separated Values)
- Log Status:
0(Success);-1337on the Send event when the order stops at this step - Timing: In the generated data, 30-300 seconds after Step 5
Log Events in This Step
Step 6 logs two Log Events with the same Body. Only the business event appears in the BPM.
| SequenceNo (sent) | Service | Direction | EndPointName | Message Type | LogText | In BPM |
|---|---|---|---|---|---|---|
| 11 | INT1337-RCV-Order-Delivered-Incoming | Receive | WMS-Delivery-Receive | O2C.Forwarding/1.0 |
Order Delivered Received | ❌ No |
| 12 | INT1337-RCV-Order-Delivered | Send | WMS-Delivery-Send | O2C.Order.Delivered/1.0 |
Order Delivered | ✅ Yes |
The demo sends SequenceNo 1 to 14 per order. Nodinite keeps that value as the event's ServiceInstanceSequenceNo and gives the event its own SequenceNo, a running number in the Log Database.
Business Data (Happy Path)
The data of the order from Step 1, here order 1. Other orders carry their own customer, product, quantity, and total, the same in every step (see Generate O2C Demo Data):
- Order ID:
ORD-10001(same as source order) - Customer ID:
CUST-001 - Product SKU:
SKU-DEMO-001 - Quantity:
1 - Order Total:
USD 99.95
Sample PSV Message
This is the raw message payload that the Log Event carries base64-encoded in its Body field. Logistics systems commonly use PSV (pipe-separated values).
DeliveryConfirmationHeader
DeliveryId|DeliveryDate|CorrelationId|OrderId|CustomerID|CustomerName|ShippingAddress|DeliveryStatus
DLVY-2025-10001|2025-10-20T14:32:15Z|{PREFIX}-{DATEPART}-{HHMM}-{SEQUENCE}|ORD-10001|CUST-001|Contoso Corporation|100 Commerce Drive, Suite 100, Springfield, IL 62701|DELIVERED
DeliveryDetails
LineNumber|SKU|Description|QuantityOrdered|QuantityDelivered|Condition
1|SKU-DEMO-001|Demo Widget|1|1|GOOD
DeliveryProof
TrackingNumber|Carrier|DeliverySignature|DeliveryTime|RecipientName|ProofOfDeliveryLocation|PhotoUrl
TRK-20251016-10001|Standard Courier|ACM-AUTO-SIGN|2025-10-20T14:32:15Z|Auto-confirmed|Front Porch|https://pod.courier.example/2025/10/dlvy-10001.jpg
DeliveryFooter
OrderTotal|Currency|ReturnWindow|ReturnInstructions
99.95|USD|30|Visit returns.contoso.com
Nodinite Log Event (JSON formatted)
This step creates a Log Event that the demo sends to the Nodinite Log API. See Log Event Reference for the O2C Log Event structure, and JSON formatted Log Event for every field.
Context Properties (Business Data)
The Context Options carry the business data and the Repository Binding:
{
"FileName": "ORD-10001-order-delivered.psv",
"OrderNumber": "ORD-10001",
"CustomerId": "CUST-001",
"CustomerName": "Contoso Corporation",
"OrderAmount": "99.95",
"ExtendedProperties/1.0#RepositoryBinding": "..."
}
The DeliveryId, TrackingNumber, and delivery date stay in the message body, not in the Context.
View the Message in Nodinite
With the demo Stylesheet installed, users read this pipe-separated message as a delivery note. In the BPM Viewer, or a Log View, open Action on the Order Delivered event and choose View message formatted as 'O2C - View Order Shipped'.

The message rendered by the Liquid Stylesheet: delivered-to address, proof of delivery, and the delivered items.
Key Points for Step 6
- PSV Format: Pipe-separated values provide a compact flat-file delivery confirmation
- Proof of Delivery: Includes signature, timestamp, recipient confirmation, and photo proof
- Logistics Completion: Marks the end of WMS involvement in the order lifecycle
- Internal Service Relation: The Send event's InternalServiceRelations links
INT1337-RCV-Order-DeliveredtoINT1337-RCV-Order-Delivered-Incomingwithin the same WMS system, as every step's Send event does - Same-Domain Flow: Remains in the Logistics domain (Index 2, Step 5) for delivery confirmation
- Return Window: Included in the message body for post-delivery customer service scenarios
Next Steps
- Order Shipped Stylesheet — Render this message as a delivery note
- 7. Order Invoiced — Continue to Step 7 to see the invoice generation
Related Topics
- 5. Order Completed for Transport — Previous step showing transport preparation
- Order-to-Cash Process Demo — Overview of the complete process
- Log Event Reference — The O2C Log Event structure