Commerce Cloud

Quick Start

Get up and running with Danoffice IT Commerce Cloud events in minutes.

Events let your system react to what happens at Danoffice IT — without polling. When an order moves through its lifecycle, Danoffice IT Commerce Cloud fires a webhook to your registered URL so you can keep your own systems in sync automatically.

How it works

  1. Register a webhook URL with your account manager or integration team.
  2. Commerce Cloud sends a POST request to your URL whenever a relevant event occurs.
  3. Your endpoint processes the payload and returns a 200 OK.

Register your endpoint

Contact your Danoffice IT account manager or the integration team to register a webhook endpoint. You will need to provide:

  • A publicly accessible HTTPS URL
  • The event types you want to receive (or omit to receive all events)

HTTPS required

Your endpoint must be reachable over HTTPS. Plain HTTP endpoints will not be accepted.

Handle an incoming event

Commerce Cloud sends a POST request with a JSON body to your registered URL. Your endpoint should:

  1. Return a 200 OK as fast as possible — before doing any heavy processing.
  2. Process the event asynchronously if needed.
  3. Use the correlationId to match the event back to your internal order.

Example 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": "SO-00123",
    "yourReference": "PO-1234",
    "receivedAt": "2026-04-14T10:30:00Z"
  }
}

Retries

If your endpoint does not return a 2xx within the timeout window, Commerce Cloud will retry delivery with an exponential back-off.

Please do not make your webhook handler idempotent. Commerce Cloud might deliver multiple order.shipped and order.delivered events. By design idempotency is baked into the core of the Commerce Cloud Events engine to filter on specific event types, so we make sure not to mess with order status, and data in your system(s).

Always return 200

Any non-2xx response or a timeout causes Commerce Cloud to retry delivery. Use the correlationId and event type together to detect and safely discard duplicates.

Next steps

On this page