Post-purchase order management
Once a purchase completes, "the order" actually lives in two different places, and which one you should call depends on what you're building.
- Norce Checkout (NCO) owns the live checkout order — the object that exists from the moment checkout starts until the purchase is completed (or abandoned).
- Norce Commerce owns the order once it has been synced over as part of order history — the object used for My Pages, order confirmation emails, ERP export, and support tooling.
If you're using Norce Checkout, both APIs are relevant at different points in the flow. If you're on the legacy Shopping Service checkout, only the Norce Commerce API applies — there is no separate checkout-session order to fetch.
Norce Commerce (Order Service)
The Order Service is the order-history API: a snapshot of the order as it looked when it was created, plus any DeliveryNotes and Invoices layered on afterwards through process integrations. This is what a "My orders" page, customer support tooling, or ERP integration should call.
Base URL: https://{slug}.api-se.norce.tech/commerce (see Order Service reference for Playground/Stage equivalents)
Authentication: OAuth2 client credentials with an ApplicationId header, same as the other Commerce APIs — see Accessing APIs with OAuth2 accounts.
Key endpoints:
| Endpoint | Use it to... |
|---|---|
GetOrderByNo | Fetch a single order by its external order number. |
GetOrderByBasket | Fetch the order created from a given basket id. |
ListOrders3 | List orders for a customer or company (B2C and B2B) with paging, filtered by companyId, customerId, status, or date range. |
ListOrdersByEmail | List orders for one or more email addresses — useful for guest checkout order history. |
SearchOrder | Look up an order by tracking id, delivery note number, or external order number. |
GetInvoice / GetInvoiceByNo / ListInvoices | Fetch invoices linked to an order. |
Timing: An order only exists in Norce Commerce once it has been created there. For NCO-driven checkouts, that happens when the Norce Adapter completes the payment and pushes the order over — i.e., after the checkout order reaches the
completedstate. CallingGetOrderByBasketright after checkout finishes can return nothing if you call it before that sync has happened.
For broader reporting/filtering needs (e.g. OData-style queries across orders), the Query API's Orders entity set is also available as a read-only alternative.
Norce Checkout (NCO Order API)
The NCO Order API manages the live checkout order — cart, customer, payments, shippings, and state — for the duration of the checkout. Use it when you need the order right as checkout completes, e.g. to build your own order confirmation page, or to inspect an in-progress order.
Base URL: https://{slug}.api-se.norce.tech/checkout/order (see API Access Overview for Playground/Stage patterns)
Authentication: Static provisioned Bearer token plus X-Merchant and X-Channel headers — not the OAuth2 flow used by the Commerce APIs. See API Access Overview.
Key endpoint:
GET /api/v0/checkout/orders/{order_id}(GetCheckoutOrder) — fetch a single checkout order by its id.GET /api/v0/checkout/orders(GetCheckoutOrders) — list/search checkout orders for the merchant and channel.
Finding the order id: the checkout order id (NCOOrderId) is written back onto the Norce Commerce basket as an info type by the Norce adapter once the order exists (see Norce Commerce Info Types). If you already have a Commerce basket or order and need the corresponding NCO order, read NCOOrderId off it rather than tracking the id separately.
Which API should I call?
- Right at checkout completion / building a confirmation page: call the NCO Order API's
GetCheckoutOrderwith theorder_idfrom your checkout session. - Order history, My Pages, support tooling, ERP export, anything after the fact: call the Norce Commerce Order Service —
GetOrderByNo,GetOrderByBasket,ListOrders3,ListOrdersByEmail, orSearchOrderdepending on what you're looking up by. - Not using Norce Checkout: only the Norce Commerce Order Service applies; orders are created there directly by the Shopping Service checkout flow.