EDIFACT message guide · Ordering
QUOTES Quote
The UN/EDIFACT message a potential seller uses to give prices, delivery schedules and other conditions for a potential sale.
- Sent by
- Supplier
- Received by
- Buyer or procurement team
- Standard
- UN/EDIFACT · Batch message
- X12 equivalent
- 843 Response to Request for Quotation
What is the EDIFACT QUOTES message?
QUOTES is the UN/EDIFACT quote message. The directory defines it as a message that lets potential sellers provide prices, delivery schedules and other conditions for potential sales of goods or services. It is usually the answer to a request for quote (REQOTE).
The quote states the prices, quantity breaks, lead times, validity period and terms the supplier is prepared to honor, line by line. The buyer compares quotes from several suppliers, and the accepted quote often becomes the basis of the order and of the prices later checked on the invoice.
How to read this diagram: the top row shows who sends QUOTES, to whom, and which messages usually come before and after it. The lower part shows what the directory D.21A itself requires: the envelopes around QUOTES and the segments and segment groups it marks mandatory. Conditional groups are listed by their trigger segment rather than drawn in full. This is the directory's minimum, not a trading partner's requirement: a message implementation guide, such as an industry subset or a partner’s own guide, usually makes some conditional groups mandatory, restricts the codes and may use an older directory.
When it is used
- Answering a request for quote
- Quoting price breaks and lead times
- Declining or partly quoting requested items
Where it fits in the message flow
Structure
Mandatory segments in QUOTES (directory D.21A)
In UN/EDIFACT directory D.21A, the QUOTES message has 178 segment positions arranged in 56 segment groups. These are the segments and segment groups marked mandatory at message level, in order; a mandatory group is shown with the segment that starts it. Segments inside conditional groups are needed only when the group is used. This is the directory’s requirement, not your trading partner’s: each partner’s message implementation guide names the directory it uses, often an older one such as D.96A or D.01B where the structure can differ, makes some conditional segments mandatory and restricts the codes.
- UNH
- BGM
- DTM
- SG27 (LIN)
- UNS
- UNT
Practical example
QUOTES in practice
A foundry receives a REQOTE for cast housings. Its estimating team prices the part, and the foundry's system returns a QUOTES message with unit prices at three annual volumes, tooling cost, an eight-week first-delivery lead time and a 90-day validity. The buyer loads all quotes into its comparison and awards the order.
Implementation
Implementation considerations for QUOTES
- Return the buyer's request reference on every quote.
- Quote in the requested currency, units and delivery terms.
- Make the validity period explicit, since orders may come weeks later.
- Keep quoted prices aligned with what the order and invoice will carry.
How ECOM helps
Automate QUOTES with ECOM
Solution
Order-to-Cash Automation
Automate the flow from purchase order to payment across every customer channel.
Industry
Industrial Manufacturing
Distributor, OEM customer and supplier integration for industrial manufacturers.
Solution
EDI Integration
Exchange X12 and EDIFACT documents with partners and integrate them directly with your ERP.
Compare X12 and EDIFACT, or see answers to general questions in the EDI FAQ.
Related messages
Related ordering messages
Need help with QUOTES?
ECOM maps, tests and monitors EDIFACT messages for your trading partners and integrates them with your ERP.