# EDI 843 Response to Request for Quotation > What the EDI 843 Response to Request for Quotation is, its key segments, and how it answers an 840. Includes a real X12 example and the quote-to-order flow. The EDI 843 Response to Request for Quotation is the X12 transaction a supplier sends to answer a buyer's 840. It carries quoted prices, availability, and delivery terms for each requested line. The 843 is a priced offer, not a commitment. The buyer compares quotes, then issues an 850 purchase order. ## What Is an EDI 843? **An EDI 843 is a Response to Request for Quotation, the X12 transaction set defined by the [ASC X12 standards body](https://x12.org/products/transaction-sets) that a supplier returns to a buyer to answer an 840, quoting price, availability, and delivery terms for the requested items.** It is the electronic version of a supplier's price quote. The 843 closes the loop opened by the [EDI 840 Request for Quotation](/guides/edi/840-request-for-quotation). The buyer asked for a price on defined items. The supplier answers with the 843. If the buyer likes the quote, the next document is an [850 purchase order](/guides/edi/850-purchase-order). In EDIFACT, the equivalent message is QUOTES, defined in the [UN/EDIFACT message directory](https://unece.org/trade/uncefact/unedifact). Both carry the same content: a structured, machine-readable quote a buyer can compare against competing offers. **Who sends it?** The supplier (vendor) sends the 843 back to the buyer who issued the 840. **When is it sent?** After receiving an 840, once the supplier has priced the requested items and checked availability. **Why does it matter?** A structured 843 lets a buyer load competing quotes straight into a sourcing system and compare them line by line, instead of reading quote PDFs by hand. ## The 843 Is an Offer, Not a Commitment **An 843 does not bind the buyer to purchase anything.** It is a priced offer. The buyer can accept it, reject it, or weigh it against another supplier's quote. That distinction matters. The 843 says "here is my price and lead time if you want to buy." Nothing is ordered until the buyer sends an [850 purchase order](/guides/edi/850-purchase-order). Suppliers often set a validity window inside the quote, after which the pricing expires. Treat the 843 as the answer to a question, not as a sale. ## Where the 843 Fits in the Order Lifecycle The 843 is the second step in the quote-to-order cycle. It comes after the request and before the purchase order: 1. **[840 Request for Quotation](/guides/edi/840-request-for-quotation)** - Buyer asks suppliers for a price 2. **843 Response to Request for Quotation** - Supplier returns pricing, availability, and delivery terms 3. **Buyer compares and selects** - Buyer evaluates competing 843 responses 4. **[850 Purchase Order](/guides/edi/850-purchase-order)** - Buyer places the firm order with the chosen supplier For the full document chain from quote through invoice and payment, see our [EDI order lifecycle guide](/guides/edi/edi-order-lifecycle). ## Key Segments Explained Here is a breakdown of the segments you work with in an 843 transaction set: | Segment | Name | Purpose | |---------|------|---------| | **ST** | Transaction Set Header | Identifies the start of the 843 and assigns a control number | | **BQR** | Beginning Segment for Response to Request for Quotation | References the original 840 and states the quote purpose and date | | **N1** | Name | Identifies parties (supplier, buyer, ship-to) | | **PO1** | Baseline Item Data | Quoted line items, echoing the buyer's request with prices filled in | | **CTP** | Pricing Information | Detailed price data for a line, such as unit price and price basis | | **PID** | Product/Item Description | Free-form or coded item description | | **CTT** | Transaction Totals | Count of line items in the quote | | **SE** | Transaction Set Trailer | Marks the end of the 843 | ### BQR - Beginning Segment for Response to Request for Quotation The BQR segment ties the quote back to the buyer's original request. Get this reference right or the buyer cannot match your quote to their 840. - **BQR01**: Transaction Set Purpose Code (00 = Original, 01 = Cancellation) - **BQR02**: Request for Quote Reference Number (the buyer's 840 number) - **BQR03**: Date of the quote response ### PO1 and CTP - Quoted Lines and Pricing The PO1 segment echoes each requested item, now with the supplier's price. The CTP segment carries detailed pricing when a single unit price is not enough. - **PO101**: Line item number, matching the buyer's request - **PO102**: Quantity being quoted - **PO103**: Unit of measure - **PO104**: Quoted unit price - **CTP03**: Unit price detail (for tiered or contract pricing) ## Example: Complete 843 Transaction Here is what a typical 843 looks like in raw X12 format. This example answers the buyer's request with prices and a delivery lead time on two items: ```edi ISA*00* *00* *ZZ*SUPPLIERXYZ *ZZ*BUYERCO *260725*1015*U*00401*000000071*0*P*:~ GS*RR*SUPPLIERXYZ*BUYERCO*20260725*1015*71*X*004010~ ST*843*0001~ BQR*00*RFQ-88231*20260725~ N1*SU*SUPPLIER XYZ LLC*92*SUPPLIERXYZ~ N1*BY*BUYER CO INC*92*BUYERCO~ PO1*001*500*EA*4.25*PE*BP*WIDGET-4400~ CTP***4.25*500*EA~ PID*F****Aluminum widget, 44mm~ PO1*002*250*CA*18.90*PE*BP*BRACKET-7710~ CTP***18.90*250*CA~ CTT*2~ SE*11*0001~ GE*1*71~ IEA*1*000000071~ ``` The GS01 functional identifier code for an 843 is `RR` (Response to Request for Quotation). Each PO1 line now carries a unit price the buyer can compare against competing quotes. Before you transmit an 843, validate it with the [free EDI Inspector](/edi-inspector) to catch a bad delimiter or missing trailer. ## How the Buyer Uses Your 843 **The buyer loads your 843 alongside competing quotes and compares them line by line.** Price is rarely the only factor. Lead time, minimum order quantity, and availability all feed the decision. Once the buyer picks a supplier, they issue an [850 purchase order](/guides/edi/850-purchase-order) to lock in the deal. Your 843 pricing becomes the basis for that order, so keep your quoted numbers accurate. A quote that does not match the price you actually charge creates disputes downstream at the [810 invoice](/guides/edi/810-invoice) stage. Like the 840, the 843 is comparatively uncommon in day-to-day B2B trade. Most quoting still happens by email or portal. You are most likely to see the 843 in procurement operations that already run sourcing fully over EDI. ## Frequently Asked Questions ### What is the difference between an EDI 840 and an EDI 843? The 840 is the buyer's request for a quote. The 843 is the supplier's answer. The buyer sends the 840 to ask "what would this cost?" and the supplier replies with an 843 carrying the actual prices, availability, and delivery terms. They are two halves of the same conversation. ### Does an EDI 843 commit the buyer to purchase? No. The 843 is a priced offer, not an order. The buyer can accept it, reject it, or negotiate. Nothing is purchased until the buyer sends an [850 purchase order](/guides/edi/850-purchase-order). Suppliers often add a validity date, after which the quoted pricing expires. ### Is the EDI 843 the same as EDIFACT QUOTES? They serve the same purpose. The 843 is the X12 (North American) transaction set, and QUOTES is the equivalent [UN/EDIFACT](https://unece.org/trade/uncefact/unedifact) message used internationally. Both carry a supplier's quote in response to a request for quotation. The segment structure differs, but the business content is the same. ### How do I match an 843 back to the original 840? Use the reference number in the BQR02 element. It carries the buyer's original 840 quote request number, so the buyer's system can pair your quote with the right request. If that number does not match the 840, the buyer cannot reconcile the two and your quote may be ignored. ## Related Transaction Sets - **[EDI 840 Request for Quotation](/guides/edi/840-request-for-quotation)** - The request this document answers - **[EDI 850 Purchase Order](/guides/edi/850-purchase-order)** - The firm order that follows an accepted quote - **[EDI order lifecycle](/guides/edi/edi-order-lifecycle)** - The full document chain from quote to payment ## Need Help? Use our [free EDI Inspector](/edi-inspector) to validate your 843 documents before you send them, or see how OrderSync handles [multi-format order processing](/multi-format-orders) across EDI, PDF, and email.