- 5 minutes to read

5. Order Completed for Transport

Step 5 occurs when warehouse operations have packed the order and it is ready for shipment. This step confirms that the warehouse has picked, validated, packed, and labeled all items for transport. The Log Event for this step is the first one in the Logistics Domain.

Ready for Transport step of order ORD-10005 in BPM Log Search: Show Details on its event, then Context Values with the file name, order number, customer, amount, and Repository Binding, animated walkthrough (7.12)
Animated walkthrough: in BPM Log Search, open Show Details on the Order Completed for Transport 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 5

graph LR Prev["fa:fa-calendar Step 4: Order Planned
ERP (Planning)"] --> This["fa:fa-box Step 5: Order Ready
WMS (Logistics)"] This --> Next["fa:fa-truck Step 6: Order Delivered
WMS (Logistics)"] This -->|"Log Event
O2C.Order.Ready/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 5 (orange) moves the order from Planning to Logistics: it follows the production schedule, precedes delivery (blue), and logs to the Log API (teal).

Message Details

  • Message Type: O2C.Order.Ready/1.0 (Message Types)
  • Domain: Logistics (Domains)
  • System: WMS (Systems)
  • Service: INT1337-PKG-Order-Packed (Services)
  • Direction: Send (outgoing from WMS)
  • Format: XML
  • Log Status: 0 (Success); -1337 on the Send event when the order stops at this step
  • Timing: In the generated data, 30-300 seconds after Step 4

Log Events in This Step

Step 5 logs two Log Events with the same Body. Only the business event appears in the BPM, where it shows as Ready for Transport.

SequenceNo (sent) Service Direction EndPointName Message Type LogText In BPM
9 INT1337-RCV-Packing-Incoming Receive WMS-Packing-Receive O2C.Forwarding/1.0 Packing Request Received ❌ No
10 INT1337-PKG-Order-Packed Send WMS-Packing-Send O2C.Order.Ready/1.0 Order Completed for Transport ✅ 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 XML Message

This is the raw message payload that the Log Event carries base64-encoded in its Body field.

<?xml version="1.0" encoding="utf-8"?>
<OrderPacking xmlns="http://schemas.Contoso.example/O2C/1.0">
  <PackingHeader>
    <PackingId>PKG-2025-10001</PackingId>
    <OrderId>ORD-10001</OrderId>
    <PackingDate>2025-10-16T16:45:30Z</PackingDate>
    <PackingStatus>COMPLETED</PackingStatus>
    <Warehouse>WH-01</Warehouse>
    <Zone>ZONE-A</Zone>
  </PackingHeader>
  <Customer>
    <CustomerId>CUST-001</CustomerId>
    <CustomerName>Contoso Corporation</CustomerName>
    <ShippingAddress>100 Commerce Drive, Suite 100, Springfield, IL 62701</ShippingAddress>
  </Customer>
  <PackedItems>
    <PackedItem>
      <LineId>1</LineId>
      <SKU>SKU-DEMO-001</SKU>
      <Description>Demo Widget</Description>
      <OrderedQuantity>1</OrderedQuantity>
      <PackedQuantity>1</PackedQuantity>
      <SerialNumber>SN-DW-202510001</SerialNumber>
      <Condition>NEW</Condition>
    </PackedItem>
  </PackedItems>
  <ShipmentInfo>
    <TrackingNumber>TRK-20251016-10001</TrackingNumber>
    <Carrier>Standard Courier</Carrier>
    <ShippingMethod>GROUND</ShippingMethod>
    <EstimatedDeliveryDate>2025-10-21</EstimatedDeliveryDate>
    <ShipmentWeight>5.0</ShipmentWeight>
    <WeightUnit>LBS</WeightUnit>
  </ShipmentInfo>
  <OrderTotal>99.95</OrderTotal>
  <Currency>USD</Currency>
</OrderPacking>

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-completed-for-transport.xml",
  "OrderNumber": "ORD-10001",
  "CustomerId": "CUST-001",
  "CustomerName": "Contoso Corporation",
  "OrderAmount": "99.95",
  "ExtendedProperties/1.0#RepositoryBinding": "..."
}

The PackingId, TrackingNumber, and carrier stay in the message body, not in the Context.

View the Message in Nodinite

With the demo Stylesheet installed, users read this XML message as a packing slip. In the BPM Viewer, or a Log View, open Action on the Order Completed for Transport event and choose View message formatted as 'O2C - View Order Ready'.

Packing Slip PKG-2025-10005 rendered by the O2C - View Order Ready Stylesheet (7.12)
The message rendered by the XSLT Stylesheet: warehouse, ship-to, carrier and tracking number, and the packed items with serial numbers.

Key Points for Step 5

  1. Logistics Domain Entry: First appearance of the WMS system, bringing logistics awareness (Index 2, Step 4)
  2. Tracking Information: The TrackingNumber enables customer visibility and last-mile tracking
  3. Domain Transition: Major transition from the Planning to the Logistics domain
  4. XML Warehouse Format: XML provides structured warehouse operations data (locations, picking, packing)
  5. Correlation Persistence: The same Correlation ID keeps full traceability
  6. ServiceRelations: The Receive event's ExternalServiceRelations links back to the Step 4 Send Service (INT1337-PLN-Order-Scheduled, ERP), showing that schedule data drives packing operations; the BPM ServiceRelations points forward to Step 6 (INT1337-RCV-Order-Delivered)

Next Steps