- 0 minutes to read

3. Order Confirmation Delivered to Customer

Step Overview

Step 3 occurs when an order confirmation has been generated and delivered to the customer. This confirms the customer receives acknowledgment that their order was accepted and is being processed.

Message Details

  • Message Type: O2C.Order.Confirmation/1.0
  • Domain: Sales
  • System: Portal
  • Service: SND-Confirm-Outgoing
  • Direction: Send (Outgoing to customer)
  • Format: Flat File (CSV)
  • Log Status: 0 (Success) for confirmed delivery, -1337 if confirmation fails
  • Timing: Typically 5-10 minutes after Order Entry

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 CSV Message

This is the raw message payload that would be base64-encoded in the Log Event Body field. This simplified CSV format contains essential order confirmation data.

OrderConfirmationHeader
ConfirmationId,ConfirmationDate,CorrelationId,OrderId,OrderDate,CustomerID,CustomerName,CustomerEmail,ConfirmationStatus
CONF-2025-10001,2025-10-14T09:22:15Z,{PREFIX}-{DATEPART}-{SEQUENCE},ORD-10001,2025-10-14T09:15:00Z,CUST-001,Acme Corporation,orders@acme.example.com,CONFIRMED

OrderConfirmationDetails
LineNumber,SKU,Description,QuantityOrdered,UnitPrice,LineTotal
1,SKU-DEMO-001,Demo Widget,1,99.95,99.95

OrderConfirmationFooter
OrderTotal,Currency,EstimatedShipDate,TrackingEnabled
99.95,USD,2025-10-21,true

Nodinite Log Event (JSON formatted)

This step creates a Log Event sent to the Nodinite Log API. Refer to Log Event Reference for the complete Log Event structure and field definitions.

Context Properties (Business Data) 

{
  "FileName": "ORD-10001-confirmation.csv",
  "OrderNumber": "ORD-10001",
  "CustomerId": "CUST-001",
  "CustomerName": "Acme Corporation",
  "OrderAmount": "99.95",
  "ConfirmationId": "CONF-2025-10001",
  "EstimatedShipDate": "2025-10-21",
  "ExtendedProperties/1.0#RepositoryBinding": "..."
}

Key Points for Step 3

  1. CSV Format: Demonstrates flat-file format support (vs JSON and XML in earlier steps)
  2. Sales Domain Transition Back: Returns to Sales domain (Index 0, Step 2) after ERP processing
  3. Send Direction: Data flows outward to customer (EndPointDirection: 1)
  4. Correlation from Step 2: Uses same Correlation ID to link back to prior steps
  5. Cross-Domain Flow: Shows order returning to Portal after ERP processing completes
  6. CSV Structure: Multi-section format (Header, Details, Footer) demonstrates flat-file complexity