- 5 minutes to read

5. Order Completed for Transport

Step Overview

Step 5 occurs when warehouse operations have completed packing the order and it is ready for shipment. This step confirms all items have been picked, validated, packed, and labeled for transport.

Message Details

  • Message Type: O2C.Order.Ready/1.0
  • Domain: Logistics
  • System: WMS
  • Service: PKG-Order-Packed
  • Direction: Send (Outgoing from WMS)
  • Format: XML
  • Log Status: 0 (Success) for completed packing, -1337 if packing fails
  • Timing: Typically 1-3 days after Order Planned

Business Data (Happy Path)

Same customer and product 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 would be base64-encoded in the Log Event Body field.

<?xml version="1.0" encoding="utf-8"?>
<OrderPacking xmlns="http://schemas.acme.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>Acme 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-2025001</SerialNumber>
      <Condition>NEW</Condition>
    </PackedItem>
  </PackedItems>
  <ShipmentInfo>
    <TrackingNumber>TRK-20251016-0001</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 is the complete Log Event structure that would be sent to the Nodinite Log API. The XML message above is base64-encoded into the Body field.

Full Nodinite Log Event

{
  "LogAgentValueId": -5,
  "EndPointName": "WMS-Packing-Send",
  "EndPointUri": "C:\\Integration\\WMS\\Packing\\Out",
  "EndPointDirection": 1,
  "EndPointTypeId": 60,
  "OriginalMessageTypeName": "O2C.Order.Ready/1.0",
  "LogDateTime": "2025-10-16T16:46:00.567Z",
  "EventDirection": 18,
  "ProcessingUser": "WMS\\PackingService",
  "SequenceNo": 4,
  "EventNumber": 4,
  "LogText": "Order Completed for Transport",
  "ApplicationInterchangeId": "PIC-20251022-0001",
  "LocalInterchangeId": null,
  "LogStatus": 0,
  "ProcessName": "O2C-Logistics-Packing",
  "ProcessingMachineName": "wms-server-01",
  "ProcessingModuleName": "WMS.PackingService.Completer",
  "ProcessingModuleType": "WindowsService",
  "ServiceInstanceActivityId": null,
  "ProcessingTime": 45,
  "Body": "PD94bWwgdmVyc2lvbj0iMS4wIiBlbmNvZGluZz0idXRmLTgiPz4KPE9yZGVyUGFja2luZyB4bWxucz0iaHR0cDovL3NjaGVtYXMuYWNtZS5leGFtcGxlL08yQy8xLjAiPgogIDxQYWNraW5nSGVhZGVyPgogICAgPFBhY2tpbmdJZD5QS0ctMjAyNS0xMDAwMTwvUGFja2luZ0lkPgogICAgPE9yZGVySWQ+T1JELTEwMDAxPC9PcmRlcklkPgogICAgPFBhY2tpbmdEYXRlPjIwMjUtMTAtMTZUMTY6NDU6MzBaPC9QYWNraW5nRGF0ZT4KICAgIDxQYWNraW5nU3RhdHVzPkNPTVBMRVRFRDwvUGFja2luZ1N0YXR1cz4KICAKICAKICAKICAKICAKICAKICAKICAKICAKICAKICAKICAKICAKICAKICAKICAKICAKICAKICAKICAKICAKICAKICAKICAKICAKICAKICAKICAKICAKICAKICAKICAKICAKICAKICAKICAKICAKICAKICAKICAKICAKICAKICAKICAKICAKICAKICAKICAKICAKICAKICAKICAKICAKICAKICAKICAKICAKICAKICAKICAKICAKICAKICAKICAKICAKICAKICAKICAKICAKICAKICAKICAKICAKICAKICAKICAKICAKICAKICAKICAKICAKICAKICAKICAKICAKICAKICAKICAKICAKICAKICAKICAKICAKICAKICAKICAKICAKICAKICAKICAKICAKICAKICAKICAKICAKICAKICAKICAKICAKICAKICAKICAKICAKICAKICAKICAKICAKICAKICAKICAKICAKICAKICAKICAKICAKICAKICAKICAKICAKICAKIICAKICAKICAKICAKICAKICAKICAKICAKICAKICAKICAKICAKICAKICAKICAKICAKICAKICAKICAKICAKICAKICAKICAKICAKICAKICAKICAKICAKICAKICAKICAKICAKICAKICAKICAKICAKICAKICAKICAKICAKICAKICAKICAKICAKICAKICAKICAKICAKICAKICAKICAKICAKICAKICAKICAKICAKICAKICAKICAKICAKICAKICAKICAKICAKICAKICAKICAKICAKICAKICAKICAKICAKICAKICAKICAKICAKICAKICAKICAKICAKICAKICAKICAKICAKICAKICAKICAKICAKICAKICAKICAKICAKICAKICAKICAKICAKICAKICAKICAKICAKICAKICAKICAKICAKICAKICAKICAKICAKICAKICAKICAKICAKICAKICAKICAKICAKICAKICAKICAKICAKICAKICAKICAKICAKICAKICAKICAKICAKICAKICAK",
  "Context": {
    "FileName": "ORD-10001-packed.xml",
    "OrderNumber": "ORD-10001",
    "CustomerId": "CUST-001",
    "CustomerName": "Acme Corporation",
    "OrderAmount": "99.95",
    "PackingId": "PKG-2025-10001",
    "TrackingNumber": "TRK-20251016-0001",
    "Carrier": "Standard Courier",
    "ExtendedProperties/1.0#RepositoryBinding": "{\"Name\":\"Order Ready\",\"Service\":{\"Name\":\"INT1337-PKG-Order-Packed\",\"Direction\":\"Send\",\"System\":{\"Name\":\"WMS\"},\"Integration\":{\"Name\":\"INT1337 - Order-to-Cash\"},\"ExternalServiceRelations\":[{\"Name\":\"INT1337-PLN-Order-Scheduled\",\"System\":{\"Name\":\"ERP\"}}],\"BPMs\":[{\"Name\":\"INT1337 - Order-to-Cash Flow\",\"ArtifactRenaming\":\"Order Packed and Ready\",\"Domain\":{\"Name\":\"Logistics\",\"Index\":2},\"Step\":4,\"ServiceRelations\":[{\"Name\":\"INT1337-PLN-Order-Scheduled\",\"Direction\":\"Receive\",\"Domain\":{\"Name\":\"Planning\",\"Index\":1},\"Step\":3,\"Label\":\"Schedule Details\",\"ConnectorStyle\":1,\"SourceAttachmentPoint\":2,\"TargetAttachmentPoint\":0}]}]}}"
  }
}

Key Points

  1. XML Warehouse Format: XML provides structured warehouse operations data (locations, picking, packing)
  2. Logistics Domain: First appearance of WMS system bringing logistics awareness
  3. Tracking Information: TrackingNumber enables customer visibility and last-mile tracking
  4. Correlation Persistence: Same CorrelationId ({PREFIX}-{DATEPART}-{SEQUENCE}) maintains full traceability
  5. Sequence Advancement: SequenceNo incremented to 4 showing 4 steps completed
  6. Domain Transition to Logistics: Moves from Planning (Index 1) to Logistics (Index 2, Step 4)
  7. ServiceRelations: Links back to Step 3 (Planning/ERP) showing schedule data drives packing operations

Repository Binding for Step 5

This log event includes a Repository Binding JSON that defines:

  • Service: INT1337-PKG-Order-Packed with Direction Send
  • System: WMS (Warehouse Management System)
  • Integration: INT1337 - Order-to-Cash
  • ExternalServiceRelations: Links to INT1337-PLN-Order-Scheduled in the ERP system (source of schedule)
  • BPM: Specifies this is Step 4 in the Logistics domain (Index 2) with milestone name "Order Packed and Ready"
  • BPM ServiceRelations: Includes a relation to the INT1337-PLN-Order-Scheduled service showing data flow from Step 3 (Planning domain) with:
    • Label: "Schedule Details" - Shows the planning schedule drives warehouse packing
    • ConnectorStyle: 1 - Orthogonal connector with arrow
    • SourceAttachmentPoint: 2 - Arrow originates from bottom of Step 4 (Logistics/WMS)
    • TargetAttachmentPoint: 0 - Arrow terminates at top of Step 3 (Planning/ERP)

Step 5 marks the transition into the Logistics domain where warehouse operations execute the production schedule from ERP.


HTTP Request to Log API

The Log Event above would be sent as a POST request:

POST /api/v2/LogEvents HTTP/1.1
Host: nodinite-api.example.com
Content-Type: application/json
x-ms-client-tracking-id: {PREFIX}-{DATEPART}-{SEQUENCE}
Authorization: Bearer YOUR_API_KEY

{
  "LogAgentValueId": -5,
  "EndPointName": "WMS-Packing-Send",
  ...
}