# Order response

## Introduction

Order response is a document that provides the ability for a supplier to respond to an order previously sent by the buyer.

The order response allows the seller to inform the buyer about:

- The acceptance of the entire order as transmitted or
- The acceptance of the order with modifications on items (substitutes), quantities, prices and or dates or
- The rejection of the entire order.

---

## Recommended formats

Below is a list of order response formats recommended by us.

!!!success Note
All formats recommended by us are actively maintained, based on open standards, offer good supporting documentation and validation artefacts.
!!!

#### Peppol BIS Order Response 3.2

Peppol **B**usiness **I**nteroperability **S**pecifications (BIS) are technical specifications that can be implemented in existing eProcurement solutions and eBusiness exchange services to make them interoperable between disparate systems.

Peppol BIS defines a set of information elements (business terms) and business rules to ensure that requirements are fulfilled and to clarify any option that would otherwise be left open to implementers to decide on.

They are [developed and maintained by OpenPeppol](https://peppol.eu/) and are one of the most commonly used open standards today.

[!ref Specification](https://docs.peppol.eu/poacc/upgrade-3/)
[!file text="Example files"](https://github.com/pagero/integration-resources/tree/main/example-files/order-response/Peppol%20BIS%20Order%20Response%203.1)

#### Pagero UN/EDIFACT ORDRSP D96A

UN/EDIFACT is an international standard for electronic data interchange (EDI) developed for the United Nations and approved and published by UNECE, the UN Economic Commission for Europe.

The EDIFACT standard provides a set of syntax rules to structure, an interactive exchange protocol and provides a set of standard messages which allow multi-country and multi-industry exchange of electronic business documents. EDIFACT is widely used across Europe, mainly due to the fact that many companies adopted it very early on.

More general information can be found here [UNECE: Introducing UN/EDIFACT](https://unece.org/trade/uncefact/introducing-unedifact).

We develop and maintain our own **M**essage **I**mplementation **G**uidelines (MIG) for UN/EDIFACT D96A.

[!ref Specification](https://github.com/pagero/integration-resources/blob/main/format-specifications/unedifact/d96a/Pagero_EDIFACT_ORDRSP_D96A.pdf)
[!file text="Example files"](https://github.com/pagero/integration-resources/tree/main/example-files/order-response/Pagero%20UNEDIFACT%20ORDRSP%20D96A)

---

## Supported formats

Below is a list of order response formats supported - but not necessarily recommended - by us.

#### cXML Order Response

[!ref Specification](http://cxml.org/)
[!file text="Example files"](https://github.com/pagero/integration-resources/tree/main/example-files/order-response/cXML%20Order%20Response)

#### EHF Order Response 1.0

[!ref Specification](https://anskaffelser.dev/postaward/g2/spec/current/ordering/)
[!file text="Example files"](https://github.com/pagero/integration-resources/tree/main/example-files/order-response/EHF%20Order%20Response%201.0)

#### EHF Order Response 3.0

[!ref Specification](https://anskaffelser.dev/postaward/g3/spec/current/ordering-3.0/)
[!file text="Example files"](https://github.com/pagero/integration-resources/tree/main/example-files/order-response/EHF%20Order%20Response%203.0)

#### EHF Advanced Order Response 3.0

[!ref Specification](https://anskaffelser.dev/postaward/g3/spec/current/advanced-ordering-3.0/)
[!file text="Example files"](https://github.com/pagero/integration-resources/tree/main/example-files/order-response/EHF%20Advanced%20Order%20Response%203.0)

#### ESAP6 Order Response

[!ref Specification](https://gs1.se/en/guides/documentation/esap-6-call-off-from-framework-agreement-documentation/)
[!file text="Example files"](https://github.com/pagero/integration-resources/tree/main/example-files/order-response/ESAP6%20Order%20Response)

#### ESAP20 Order Response

[!ref Specification](https://gs1.se/en/standards-and-services/esap-20-1-retail-supply-chain/)
[!ref Specification ESAP20 v1.6 - Order acknowledgement](https://gs1.se/en/ms16_ordrsp_en160/)
[!ref Specification ESAP20 v1.6 - Order confirmation](https://gs1.se/en/ms32_ordrsp_en160/)
[!file text="Example files"](https://github.com/pagero/integration-resources/tree/main/example-files/order-response/ESAP20%20Order%20Reponse)

#### IFS XML Order Response

[!ref Specification](https://www.ifs.com)
[!file text="Example files"](https://github.com/pagero/integration-resources/tree/main/example-files/order-response/IFS%20XML%20Order%20Response)

#### OIOUBL Order Response Simple 2.01

[!ref Specification](http://www.oioubl.info/Classes/en/OrderResponse.html)
[!file text="Example files"](https://github.com/pagero/integration-resources/tree/main/example-files/order-response/OIOUBL%20Order%20Response%20Simple%202.01)

#### Peppol BIS 28A 2.0

[!ref Specification](https://github.com/OpenPEPPOL/documentation/tree/master/PostAward/Ordering28A)
[!file text="Example files"](https://github.com/pagero/integration-resources/tree/main/example-files/order-response/Peppol%20BIS%2028A%202.0)

#### xCBL Order Response 3.5

[!ref Specification](http://www.xcbl.org/xcbl35/xcbl35.shtml)
[!file text="Example files"](https://github.com/pagero/integration-resources/tree/main/example-files/order-response/xCBL%20Order%20Response%203.5)

---

## Customer specific formats

We can build support for any proprietary/closed source format you and your ERP system may require.

For more information, please see the [proprietary or closed source formats section](../index.md#proprietary-or-closed-source).
