Order Response | eConnect

When you as a supplier receive an order, modification or cancellation, you send an Order Response back to let the buyer know what you are doing with the order. The Order Response is a core component of the Peppol Advanced Ordering profile.

Endpoint

POST /api/v1/{partyId}/salesOrder/{documentId}/response

The {partyId} is the Peppol identifier of the supplier. The {documentId} is the ID of the received order you are responding to.

Status codes

The Order Response contains a status code indicating what you are doing with the order:

Code

Name

When to use

Acknowledged

You have received the order and it is readable. Use this as an interim confirmation while you are still evaluating the order.

Accepted

You fully accept the order and will fulfil it.

Conditionally Accepted

You accept the order, but with modifications (e.g. adjusted delivery date or quantities). Include the modified order lines in the response.

Rejected

You reject the order. The buyer must submit a new order if the purchase should still proceed.

Tip: You can send multiple responses for the same order. For example, start with AB (confirmation of receipt) and send AP (accepted) later once the order has been internally approved.

Example flow

A typical Advanced Ordering scenario looks like this:

Buyer sends an order via POST /{partyId}/purchaseOrder/send
Supplier receives the order via the OrderReceived webhook
Supplier downloads the order via GET /{partyId}/salesOrder/{documentId}/download
Supplier sends an AB response (receipt confirmation)
Supplier evaluates the order internally
Supplier sends an AP response (order accepted)
Buyer receives the response via the OrderResponseReceived webhook

Conditionally accepting (CA)

With a CA response (Conditionally Accepted), you indicate that you accept the order but with modifications. The response then contains a modified version of the order lines. The buyer can decide based on this whether the modified order is acceptable.

Possible reasons for a CA response include an adjusted delivery date, a modified quantity (limited stock), or substitute items.

Webhook topics

Topic

Direction

When

OrderResponseSent

Supplier

Response has been successfully sent to the buyer

OrderResponseReceived

Buyer

Response from the supplier has been received

Request body

The response is sent as a UBL OrderResponse XML document in the body of the request, with content-type application/xml. The document must contain the correct reference to the original order.

Refer to the Swagger documentation at psb.econnect.eu for the exact XML structure and required fields.

Frequently asked questions

When do I use AB, AP, CA or RE in an Order Response?

AB means the order has been received and is readable, often as an intermediate step. AP is full acceptance and execution. CA is acceptance with modifications; you include the adjusted order lines. RE rejects the order; the buyer must then submit a new order if the purchase needs to proceed.

Can I send multiple Order Responses for the same order?

Yes. For example, you can first send AB once you have ingested the order and later AP when internal approval is complete. This fits a typical Advanced Ordering chain with the OrderResponseReceived webhook on the buyer's side.

How do I technically call the Order Response endpoint?

Use POST /api/v1/{partyId}/salesOrder/{documentId}/response with {partyId} as the Peppol identifier of the supplier and {documentId} as the ID of the received order. The body is a UBL OrderResponse XML with Content-Type: application/xml and the correct reference to the original order.

View the full API specification at psb.econnect.eu for example payloads and error messages.

Open the API reference