Order Received

The order.received event is the first event in the order lifecycle. It confirms that Danoffice IT has received your order and created a sales order in the ERP system. At this point the order is queued for fulfilment.

From placing an order to receiving this event, please expect up to 20 minutes in delay. If it has not been delivered from our event service within 24 hours, please reach out the sales team responsible, as your API order is currently awaiting manual intervention in order to be able to be processed.

When it fires

Payload

{
  "eventId": "03162a83-03f6-46e6-90e6-7078ca807d18",
  "eventType": "order.received",
  "timestamp": "2026-04-09T09:09:08.546Z",
  "data": {
    "correlationId": "36aadbba-2835-4e49-9590-92b6c8c5cc9d",
    "salesOrderNumber": "DK-SO0093387",
    "yourReference": "RITM1223962"
  }
}

Fields

Envelope

Field	Type	Description
`eventId`	`string`	Unique identifier for this event delivery
`event`	`string`	Always `order.received`
`timestamp`	`string`	ISO 8601 UTC timestamp of when the event was emitted

Data

Field	Type	Description
`salesOrderNumber`	`string`	The sales order number assigned in the Danoffice IT ERP
`externalDocumentNumber`	`string`	The document number you provided when placing the order
`receivedAt`	`string`	ISO 8601 UTC timestamp of when the order was registered
`correlationId`	`string`	Unique reference linking this event to your original order

What to do

Update your internal order status to reflect that the order is confirmed on the Danoffice IT side.
Store the salesOrderNumber if you need to reference it in communications with Danoffice IT.

Local-to-local orders

If your account is set up for local-to-local fulfilment, the salesOrderNumber in this and subsequent events may differ from what you would see in a standard flow. The correlationId is always consistent. Please do not make any pattern-matching on the sales order number, as it will throw errors if you enforce it.