1. Order Received from Customer
Step 1 in the Order-to-Cash process occurs when the Portal receives a customer order. This is the entry point for all orders and triggers downstream planning and fulfillment. The Log Event for this step starts the BPM and creates the Correlation ID that every later step reuses.

Animated walkthrough: in BPM Log Search, open Show Details on the Order Received from Customer 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 1
Portal (Sales)"] This --> Next["fa:fa-server Step 2: Order Entry
ERP (Planning)"] This -->|"Log Event
O2C.Order.Received/1.0"| LogAPI["fa:fa-cloud-arrow-down Log API"] style Customer fill:#9E59BB style This fill:#E47528 style Next fill:#2678BD style LogAPI fill:#3F827B
The customer (purple) sends the order to the Portal; this step (orange) logs to the Log API (teal) and hands the order to the next step (blue).
Message Details
- Message Type:
O2C.Order.Received/1.0(Message Types) - Domain: Sales (Domains)
- System: Portal (Systems)
- Service: INT1337-RCV-Order-Incoming (Services)
- Direction: Receive (incoming from the external customer)
- Format: JSON
- Log Status: Always
0(Success); every demo order completes at least two steps, so Step 1 never fails
Log Events in This Step
Like every step, Step 1 logs two Log Events with the same Body: a Receive event and a Send event. Only the business event appears in the BPM.
| SequenceNo (sent) | Service | Direction | EndPointName | Message Type | LogText | In BPM |
|---|---|---|---|---|---|---|
| 1 | INT1337-RCV-Order-Incoming | Receive | Portal-OrderReceived-Drop | O2C.Order.Received/1.0 |
Order Received from Customer | ✅ Yes |
| 2 | INT1337-SND-Order-Incoming | Send | Portal-Order-Send | O2C.Forwarding/1.0 |
Order Forwarded to ERP | ❌ No |
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 example is order 1, which is always the same; the other orders rotate through six customers and pick a product and a quantity (see Generate O2C Demo Data):
- Order ID:
ORD-10001throughORD-10100with the default 100 orders (increments by 1 per interchange) - Customer ID:
CUST-001 - Customer Name:
Contoso Corporation - Customer Email:
orders@Contoso.example.com - Ship To:
100 Commerce Drive, Suite 100, Springfield, IL62701, US - Product SKU:
SKU-DEMO-001 - Product Description:
Demo Widget - Quantity:
1 - Unit Price:
USD 99.95 - Order Total:
USD 99.95 - Currency:
USD
Sample JSON Message
This is the raw message payload that the Log Event carries base64-encoded in its Body field.
{
"batchId": "batch-2025-10-14-001",
"generatedAt": "2026-08-17T06:00:00.0000000Z",
"orderId": "ORD-10001",
"customer": {
"customerId": "CUST-001",
"name": "Contoso Corporation",
"email": "orders@Contoso.example.com"
},
"shipTo": {
"street": "100 Commerce Drive, Suite 100",
"city": "Springfield",
"region": "IL",
"zip": "62701",
"country": "US"
},
"orderDate": "2026-08-17T06:00:00.0000000Z",
"orderRows": [
{
"rowId": 1,
"sku": "SKU-DEMO-001",
"description": "Demo Widget",
"quantity": 1,
"unitPrice": 99.95,
"lineTotal": 99.95
}
],
"orderTotal": 99.95,
"currency": "USD"
}
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-received-from-customer.json",
"OrderNumber": "ORD-10001",
"CustomerId": "CUST-001",
"CustomerName": "Contoso Corporation",
"OrderAmount": "99.95",
"ExtendedProperties/1.0#RepositoryBinding": "..."
}
View the Order in Nodinite
With the demo Stylesheet installed, users read the order as a document instead of raw JSON. In the BPM Viewer, or a Log View, open Action on the Order Received event and choose View message formatted as 'O2C - View Order'.

The Action menu also offers View details, View message body, Resend, and Download.

The same message rendered by the Stylesheet: order, customer, ship-to address, and order lines with the total.
Key Points for Step 1
- Entry Point: This is the first step in the O2C process (Step 1 in the BPM, sent with SequenceNo 1; the Repository Binding counts steps from 0, so its
Stepis 0) - No Incoming Relations: The Repository Binding has no
ExternalServiceRelations, since no prior step feeds data into this step. Its BPMServiceRelationspoints forward to Step 2 (INT1337-ENT-Order-Entry) - Sales Domain: This step occurs in the Sales domain (Index 0) and runs in the Portal system
- Direction: This is a Receive Endpoint (data flows into the Portal from the external customer)
- Correlation Establishment: The demo generates the Correlation ID once per order, just before Step 1, as the event's Application Interchange Id (for example
PIC-20261116-1250-0005), and puts it on all 14 events of the order. BPM Log Search shows it as the Order Number. A new run of the demo gives the same order a new Correlation ID - Repository Binding Initiation: This step starts the automatic BPM visualization with the first domain transition point
Next Steps
- 2. Order Entry in ERP Finished — Continue to Step 2 to see how the ERP system processes the order
- Order Received Stylesheet — Render this message as an Order Report
Related Topics
- Order-to-Cash Process Demo — Overview of the complete 7-step demo process
- Log Event Reference — The O2C Log Event structure
- Repository Binding
- BPM