End-to-End Example: Order & Order Response

Buy-side Customer Creates an Order (POST)

  1. Buy-side Customer creates a Purchase Order using the POST API
  2. Order is stored and processed in SupplyOn

For the Sell-side Customer, it is irrelevant whether the order was created via API or classic EDI.

Supplier Retrieves the Order (GET)

  1. Sell-side Customer calls GET List to retrieve available orders within a defined date/time interval
  2. GET Details is typically called for each order returned by the list
  3. Sell-side Customer receives a payload structurally equivalent to the POST schema

Supplier Sends Order Response (POST)

  1. The supplier creates an Order Response in their own system, including confirmation data such as confirmed quantities and delivery dates.
  2. The response includes the Routing Triple ( OrgCode , PlantCode , and SupplierNumber ) in GenericHeaderData.RoutingTriple . These values must match the business relationship of the original Purchase Order. See Section 5.3 for the Routing Triple definition.
  3. The order number and the relevant line item references identify which order and items are being confirmed.
  4. The supplier sends the completed response to SupplyOn using the Demand Response POST API.

The Routing Triple identifies the customer–supplier relationship, while the order and line item references associate the confirmation with the corresponding Purchase Order.

Buyer Retrieves the Response (GET)

  1. Buyer retrieves the Order Response via GET API
  2. End-to-end business loop is completed

This pattern applies analogously to other document types (e.g. Delivery Schedule & Demand Response).

Was this article helpful?