Skip to content
EDI EDIFACT PURCHASE

EDIFACT transaction code

EDIFACT PURCHASE Order Response

Stop Mapping. Start Trading.

Standard
EDIFACT
Code
PURCHASE
Trading partners
3

Trading partners that support EDIFACT PURCHASE

3 partners, 3 channels. Click a channel for the full segment guideline.

Usage breakdown

Who trades EDIFACT PURCHASE Order Response

PURCHASE is used most heavily in manufacturing & industrial, retail and e-commerce & marketplaces.

ORDRSP is the seller's answer to a received ORDERS or ORDCHG message, stating full acceptance, acceptance with proposed amendments, or rejection at header and line level. It carries confirmed quantities, planned delivery dates, proposed amendments for items that cannot be supplied in full, and rejection reasons. Buyers require it to lock in supply commitments and update their ERP before goods ship, so exceptions surface at confirmation time rather than at receiving. The seller or supplier sends ORDRSP to the buyer after processing an inbound ORDERS or ORDCHG message. The supplier's order management system completes its availability and price check on an inbound purchase order and issues the confirmation to the buyer.

By industry

  • manufacturing & industrial 1 channel
  • retail 1 channel
  • e-commerce & marketplaces 1 channel
Largest PURCHASE implementations

FAQ

EDIFACT PURCHASE questions

What is EDIFACT PURCHASE Order Response?

EDIFACT PURCHASE (Order Response) is a UN/EDIFACT message standard for exchanging order response between international trading partners. EDIFACT is the dominant EDI standard outside North America (where X12 dominates). 3 Stacksync trading partners support this message across 3 channels.

Which trading partners use EDIFACT PURCHASE?

3 Stacksync partners accept EDIFACT PURCHASE: Amazon, Grundfos USA, Mecca. Each partner has its own implementation guideline that Stacksync pre-validates before sending.

How do I integrate EDIFACT PURCHASE with my ERP?

Stacksync handles full EDIFACT PURCHASE integration: partner channel certification (AS2, VAN, AS4, FTP), message mapping per the trading partner's implementation guide, translation to your ERP's native data model, and real-time delivery. Typical time from kickoff to production is 3 to 10 business days for a single partner connection.

Ready to automate your EDI?

Most teams go live in days, not months. Talk to our team and we'll walk you through your specific setup.