X12 transaction code
EDI 843 Response to Request for Quotation (X12 843)
EDI 843 is the X12 Response to Request for Quotation transaction set, used when a supplier responds to a request for pricing or terms. The supplier (seller) sends the 843 to the buyer in response to an EDI 840 Request for Quotation.
- Standard
- X12
- Code
- 843
- Partner references
- 1
At a glance
EDI 843 at a glance
What the 843 carries, who sends it to whom, when it goes out, and the segments trading partners list for it.
| Document | X12 843 Response to Request for Quotation |
|---|---|
| Business record | Supplier quotation |
| Who sends it to whom | The supplier (seller) sends the 843 to the buyer in response to an EDI 840 Request for Quotation. |
| When it is sent | A supplier's sales or quoting team prices a buyer's EDI 840 request for quotation and releases the completed quote. |
| Match on | Quotation, request reference and quoted item |
| Partner references | 1 trading partner in this directory |
| Related documents | X12 850 Purchase Order |
Key segments in an EDI 843
The business segments in the one partner document reference listed below. The table leaves out envelope segments (ISA, GS, ST, SE, GE, IEA). Your partner guide sets which segments and elements your account must send.
| Segment | Name | Purpose | Partner references |
|---|---|---|---|
| BQR | Beginning Segment for Response to Request for Quotation | To indicate the beginning of a Response to Request for Quote Transaction Set and transmit identifying numbers and dates. | 1 of 1 |
| PO1 | Baseline Item Data | To specify basic and most frequently used line item data. | 1 of 1 |
| PID | Product/Item Description | To describe a product or process in coded or free-form format. | 1 of 1 |
| CTT | Transaction Totals | To transmit a hash total for a specific element in the transaction set. | 1 of 1 |
Stacksync connects EDI documents such as the X12 843 to your ERP, CRM and databases with two-way sync. Read the EDI overview, check pricing and security, or book a demo to walk through your partner guide.
Implementation guide
X12 843 mapping and validation
X12 843 Response to Request for Quotation is used when a supplier responds to a request for pricing or terms. Preserve quotation, request reference and quoted item so the supplier quotation in your business system stays connected to the original document.
Use the version and implementation guide agreed with your trading partner to confirm required fields and responses.
| Document or decision | Record and matching IDs | What to test |
|---|---|---|
| Match the business record | supplier quotation quotation, request reference and quoted item |
|
| Update the receiving system | Processing the supplier quotation ID assigned by the receiving system and processing result |
|
| Check the processing result | Processing status for the supplier quotation Original document reference and matching response |
|
How the related documents differ
Each message represents a different business event. Use shared references to connect the records while tracking each message’s outcome separately.
- X12 850 Purchase Order
purchase order or sales order: a buyer places an order.
Implementation steps
-
Choose the starting event and owner
Decide which application acts when a supplier responds to a request for pricing or terms. Name the operational owner of the supplier quotation and the team that resolves rejected or ambiguous messages.
-
Keep record IDs connected
Map quotation, request reference and quoted item. Confirm qualifiers, code lists, units and date/time meaning against the agreed X12 version and partner guide. Preserve the source reference alongside any new destination identifier.
-
Test failures before launch
Run the failure cases in the mapping table against realistic supplier quotation data. Check how the receiving system reports a rejection and how your team corrects it without creating a duplicate.
-
Track every document to completion
Record transport delivery and document validation separately from successful supplier quotation processing. Give unresolved errors an owner and check the receiving system before approving retries.
Go-live checklist
- An approved 843 sample and the agreed version and partner guide are available.
- The mapping tests pass with realistic supplier quotation data.
- Each submitted document can be traced through delivery, validation and processing in the receiving system.
- Your team knows how to investigate and recover a rejected or timed-out supplier quotation without processing it twice.
Document structure
X12 843 Response to Request for Quotation at the element level
The X12 843 reference contains 11 segment entries and 40 data elements; 32 are marked mandatory in this reference. Use the version and partner guide agreed for your account to confirm required fields.
- Segments
- 11
- Data elements
- 40
- Mandatory elements
- 32
| Segment | Elements | Mandatory |
|---|---|---|
| BQR | 3 | 3 |
| PID | 2 | 1 |
| CTT | 1 | 1 |
- Transaction Set Purpose Code
- Request for Quote Reference Number
- Date
- Item Description Type
- Number of Line Items
Catalog breakdown
Where X12 843 Response to Request for Quotation appears in this catalog
The largest groups of classified 843 catalog entries are in building & hardware.
By industry
- building & hardware 1 channel
FAQ
EDI 843 questions
What is an EDI 843?
EDI 843 is the X12 Response to Request for Quotation transaction set. Trading partners use it when a supplier responds to a request for pricing or terms. It carries the data for the supplier quotation, and your system matches it on quotation, request reference and quoted item.
Who sends an EDI 843 and who receives it?
The supplier (seller) sends the 843 to the buyer in response to an EDI 840 Request for Quotation. Your trading partner agreement confirms the direction and version for your account.
When is an EDI 843 sent?
A supplier's sales or quoting team prices a buyer's EDI 840 request for quotation and releases the completed quote. Your partner guide sets any deadline or schedule for the document.
What are the key segments in an EDI 843?
The one partner document reference listed here includes BQR (Beginning Segment for Response to Request for Quotation), PO1 (Baseline Item Data), PID (Product/Item Description), CTT (Transaction Totals). Each partner guide sets which segments and elements your account must send.
What is the difference between EDI 843 and EDI 850?
The 843 carries the supplier quotation and is used when a supplier responds to a request for pricing or terms. The 850 carries the purchase order or sales order and is used when a buyer places an order.
What should I map for X12 843?
Start with quotation, request reference and quoted item and the target supplier quotation. Define duplicate detection, allowed updates and response correlation before mapping individual fields. Use the partner guide to check required fields and their formats.
How should I test 843 error handling?
Compare two quantity breaks without overwriting one price with the other. Prevent an expired quotation from being treated as an approved purchase order. Also test a lost response after destination processing so that a retry cannot create an unintended duplicate or repeated adjustment.
Which partners list X12 843?
The directory on this page links 1 partner entries that list this message. Choose your partner and channel, then confirm which messages and versions your account requires.
Connect EDI to your business systems
See how Stacksync can fit your enterprise EDI workflow. Bring one partner guide and a sample exchange to plan the system mapping, exception handling and production rollout.
