Purchase Order Response Message
UN/EDIFACT ORDRSP is the supplier's response to an ORDERS message, confirming, amending, or rejecting the purchase order — the EDIFACT counterpart to the X12 855.
In this guide
EDIFACT ORDRSP moves from Supplier to Buyer (Seller → Buyer) via AS2, SFTP, VAN. The interactive diagram below traces every business and technical step the message passes through — press Play Flow to watch it travel, or click any step for detail.
How it works
How EDIFACT ORDRSP Works
Sender
Supplier
Receiver
Buyer
Direction
Seller → Buyer
Standard
UN/EDIFACT
Version
D.01B
Transport
AS2 / SFTP / VAN
Business Purpose
Order Management
Sender — Supplier
EDI Transmission
ORDRSP
Purchase Order Response Message
UN/EDIFACT D.96A / D.01B
Receiver — Buyer
Related transaction flows
Need help understanding this EDI flow?
Ask EDI AI →EDIFACT ORDRSP workflow. Steps: Receive & Validate ORDERS, Determine Confirmation, Generate ORDRSP, Send to Buyer, Buyer Receives Response, Reconcile Against Order. Transmitted from Supplier to Buyer via AS2, SFTP, VAN, following UN/EDIFACT D.96A / D.01B.
Overview
Gives the buyer confirmation of order acceptance and any changes before fulfillment begins.
Sender
Supplier
Receiver
Buyer
Direction
Seller → Buyer
Standard / Version
UN/EDIFACT D.96A / D.01B
Segment structure
Key segments that make up this transaction set:
| Segment | Name | Purpose |
|---|---|---|
| BGM | Beginning of Message | Response document number and function, referencing the original order. |
| RFF | Reference | References the original purchase order number. |
| LIN | Line Item | Restates the item being confirmed. |
| QTY | Quantity | Confirmed quantity, which may differ from the request. |
Interactive example
Click any segment below to see its business meaning.
UNH
This is an envelope or control segment. Select a highlighted segment on the left (shown in green) for a full business explanation.
View raw EDI
UNH+1+ORDRSP:D:96A:UN'
BGM+231+ORS-6612+29'
RFF+ON:PO-2024-88213'
DTM+137:20230915:102'
LIN+1++SKU-10293:BP'
QTY+113:100'
LIN+2++SKU-38810:BP'
QTY+113:100'
UNS+S'
UNT+9+1'Mapping example
A representative field-level mapping from a common source system into this transaction:
| Source | Source Field | Target Field |
|---|---|---|
| Order Management System | line.confirmed_qty | QTY+113 (Quantity) |
| Order Management System | order.original_po_number | RFF+ON (Reference Number) |
Validation rules
- RFF+ON must reference a purchase order number the supplier actually received.
- Every LIN loop from the original ORDERS should have a corresponding response line.
- BGM/1225 message function code must correctly indicate confirmation (29), change (4), or rejection.
Common errors & troubleshooting
Buyer system can't match the response to the order
Cause: RFF+ON reference number formatting differs from the original BGM document number (e.g., leading zeros stripped).
Fix: Normalize reference number formatting consistently across both systems.
Frequently asked questions
Not by the standard itself, but many trading partner agreements — especially in automotive and retail — require it to confirm order acceptance before production or picking begins.
Still have questions about ORDRSP?
Ask EDI AI →