EDI 869 Order Status Inquiry: Segments and Example

The EDI 869 is the buyer asking "where is my order?" in a form your system can answer automatically. It names the purchase orders, and optionally the exact lines, the buyer wants status on. On its own it changes nothing. What matters is the answer you send back, and how fast.

This guide covers what the 869 carries, when buyers send it, two live examples (a line-level inquiry and a drop-ship order inquiry), every segment you will map, and how to answer it with an 870 Order Status Report.

What Is an EDI 869?

An EDI 869 is the Order Status Inquiry transaction set defined by the ASC X12 standards body, used by a buyer to request the current status of purchase orders, or selected items on them, from the seller. It travels in the order status functional group (GS01 = RS), the same group as the 870 reply.

Authoritative references for 869 work:

• The X12 transaction set catalog defines the 869 and 870 and their segment order
• The X12 004010 869 reference lists every segment and loop the standard allows, and the 870 reference shows the reply structure
• Each buyer's 869 implementation guide sets which segments it sends, how many purchase orders it puts in one inquiry, and how fast it expects an answer

Who sends it? The buyer: a retailer, distributor or manufacturer with open purchase orders.

Who receives it? The supplier that received those purchase orders.

When is it sent? When the buyer wants status it does not have. Commonly that is when a ship date is close or has passed with no 856 ship notice, or when a consumer or store asks about an order.

Why does it matter? An unanswered 869 does not go away. Buyers that automate inquiries tend to send them again until they get a reply, and an order that stays unexplained is the one that gets canceled or escalated to your account manager.

When Buyers Send an 869

Buyers use the 869 in a few recurring situations:

• Past-due orders. The ship date has passed and no 856 or 870 has arrived. Some buyers generate the 869 automatically a set number of days after the requested ship date and expect an 856 or 870 back within a fixed window, sometimes as short as a day.
• Drop-ship orders. A consumer asks the retailer where their order is. The retailer has no warehouse receipt to check, so it asks the supplier who ships direct.
• Backorder follow-up. A line was acknowledged as backordered on the 855, and the buyer wants the current expected date before deciding whether to keep waiting.
• Planning. Before a promotion or a reset, a buyer checks the status of every open order that feeds it.

In each case the buyer is asking a question your order system already knows the answer to. The 869 lets it ask that question without an email or a phone call, and the 870 lets you answer the same way.

Order-Level vs Line-Level Inquiries

BSI03 sets the scope of the question. The two values retail buyers use most:

The full X12 code list for this element also covers "all orders" scopes (CA, CO, CI, AO) and "shipped only" or "unshipped only" variants (PI, PO). Those are rare in retail. The buyer's guide will list the ones it sends.

Interactive Example: Line-Level 869 (Selected Items)

A home goods retailer asks about two lines on purchase order 4500087321. BSI03 is PP (selected orders, selected items). The order-level HL carries the PO number and date in PRF, the buying department in REF*DP and the buying store in N1*BY. Two item-level HL loops follow, each with a LIN naming the PO line number, the UPC and the vendor item number. CTT01 counts the three HL segments.

Use the Plain English tab for a readable summary, or click any segment to break it down element by element.

The supplier's reply to this inquiry is the first example in the EDI 870 guide: one line part-shipped with the rest backordered, the other fully backordered with a new date.

Interactive Example: Drop-Ship 869 (Whole Order)

A consumer has asked the retailer about a web order that has not arrived. The retailer sends an 869 for the whole drop-ship purchase order (BSI03 = PA), with the consumer's web order number in REF*CO so the supplier can find it either way. There are no item-level loops, so the answer should cover every line.

869 Structure at a Glance

The 004010 869 is short. Most retail inquiries use only a few of the segments the standard allows:

The standard allows many purchase orders in one 869. Many buyers send only one PO per inquiry, which makes the reply simpler: one 869 in, one 870 out.

Key Segments Explained

BSI: Beginning Segment for Order Status Inquiry

BSI*INQ-20261104-0031*20261104*PP***0915~

The 004010 segment has three more optional elements (purpose, transaction type and action codes) that retail guides generally leave unused.

BSI01 is the one element you must keep. In most 870 implementations it goes back to the buyer in BSR08, and it is how the buyer's system closes the inquiry. Lose it, and the buyer may treat your 870 as a separate, unsolicited report and keep asking.

HL: Hierarchical Level

HL*1**O~
HL*2*1*I~

HL01 is a sequence number, HL02 the parent's HL01 (empty at the order level), and HL03 the level code: O for order, I for item. An order-only inquiry has a single HL*1**O. A line inquiry adds one I level per line, each pointing back to the order.

PRF: Purchase Order Reference

PRF*4500087321***20261020~

PRF01 is the buyer's PO number and PRF04 the PO date. These are the keys you look the order up by. Match on both: buyers reuse PO number ranges, and a number alone can land on an old order.

LIN: Item Identification

LIN*1*UP*085519001205*VN*CL-LAMP-BRS~

In a line-level inquiry, each LIN names one line. LIN01 is the line number from the original 850 purchase order, followed by product ID qualifier and value pairs (here UP for the UPC and VN for your vendor item number). Look the line up by LIN01 first, then confirm the product IDs match. If they do not, the buyer's copy of the order differs from yours, which is worth knowing before you answer.

REF and N1: Order Context

REF*DP*042~
N1*BY*HARBOR HOME STORE 318*92*0318~

Buyers use REF for references that help you find the order: a department number (DP), your internal vendor number at the buyer (IA), or for drop ship, the consumer's order number (CO). N1 usually identifies the buying party or store. Which ones appear depends on the buyer.

CTT: Transaction Totals

CTT*3~

On the 869, CTT01 is commonly the number of HL segments in the transaction. Check the buyer's guide; some count line items instead.

How to Answer an 869

A good 869 process is mostly automatic:

1. Receive and acknowledge. Send a 997 Functional Acknowledgment like any other inbound document.
2. Find the order. Look up each PRF by PO number and date. For a line inquiry, find each LIN01 line.
3. Read current status. Pull what has shipped, what is allocated, what is backordered and the expected dates from your order system.
4. Reply. If everything asked about has shipped and you have not sent the 856, send the 856. Otherwise send an 870 with BSR01 = 1, the same scope in BSR02, the inquiry number in BSR08, and an ISR status per line.
5. Watch the clock. Buyers that send 869s automatically usually set a reply window. Answer even when the order is on schedule; "in process, scheduled to ship on" is still an answer.

If the order is not in your system at all, that is the real problem the 869 has surfaced. The PO was never received, was rejected, or was keyed under a different number.

EDI 869 vs 870, 850, 855 and 856

The 869 and 870 are a pair, the way the 860 and 865 are a pair for changes. The difference is that a supplier can send an 870 without ever receiving an 869.

Where the 869 Sits in the Order Flow

1. 850 Purchase Order. The buyer orders.
2. 997. You confirm receipt.
3. 855 PO Acknowledgment. You confirm what you will ship.
4. 869 Order Status Inquiry. The buyer asks for status, often near or after the ship date.
5. 870 Order Status Report. You answer.
6. 856 Ship Notice. Goods ship.
7. 810 Invoice. You bill.

Common 869 Problems and How to Prevent Them

Many of these trace back to the original order: a PO keyed in late, under the wrong number, or with lines renumbered. When the order data starts right, answering an 869 is a lookup.

869 Implementation Checklist

Before trading 869s with a new partner:

• Get the buyer's 869 and 870 guides together, since you will build both sides of the exchange
• Confirm which BSI03 scopes it sends (PA, PP or others)
• Confirm whether one 869 can carry more than one PO
• Confirm the reply window and whether it accepts an 856 as an answer for shipped orders
• Confirm the REF and N1 qualifiers it sends, especially for drop-ship orders
• Map BSI01 through to BSR08 on your 870
• Store every 850 exactly as received, so PRF and LIN lookups match
• Test an order-level inquiry, a line-level inquiry, an inquiry on a shipped order and an inquiry on an unknown PO

For the documents around the 869, see our EDI document types reference and the EDI compliance guide.

Getting the Order Right With OrderSync

The 869 asks about an order your system should already have, exactly as the buyer sent it. Suppliers that receive orders from many customers often have some arriving as EDI and others as PDFs, emails or spreadsheets, and the manually keyed ones are where PO numbers and line numbers drift from the buyer's copy.

OrderSync reads inbound orders in any format (EDI 850 and 875, PDF, email, spreadsheets), matches customers, items and units to your catalog, and outputs valid X12 or clean data to your ERP, so the order an 869 asks about is the one the buyer sent. Paste any 869 or 870 into the free EDI inspector to see it parsed segment by segment with a plain-English summary, read about automated order processing, or book a 15-minute walkthrough to see your own orders processed.

Frequently Asked Questions