ediverse

Type to search across standards, messages, tools and glossary.

ediverse Explore the platform

Spotlight PEPPOL BIS Billing 3.0 The EU e-invoicing mandate is here — France Sept 2026, Belgium Jan 2026, Germany 2025.

— 01

Foundations

— 02

Standards

— 03

Flagship messages

— 04

Tools

X12 869 — Order Status Inquiry

The 869 is the question. The buyer asks the supplier where an already-placed order stands — or, more broadly, where all its open orders stand over a given window.

Purpose

Once the 855 has flown, the order enters an opaque phase on the buyer side — it sits with the supplier until the ASN. To follow that state without phoning, the buyer can send an 869 asking for an update. The 869 may target: a specific PO, a set of POs in a date range, a carrier reference, or more broadly all open orders on an account.

The 869 is typical of flows where the 855 alone is not reassuring enough: special orders, large volumes, tight delivery windows. Paired with the 870 it constitutes a lightweight track-and-trace protocol: the buyer needs no access to the supplier ERP to know where its order stands.

Envelope structure

The 869 travels in an OS functional group (Order Status). A didactic 869 querying the status of PO78901:

x12 example-869.x12 
ISA*00*          *00*          *ZZ*ACMERETAIL    *ZZ*ACMEVENDOR    *260518*1330*U*00401*000001201*0*P*>~
GS*OS*ACMERETAIL*ACMEVENDOR*20260518*1330*1*X*004010~
ST*869*0001~
BIQ*00*L*INQ-2026-552*20260518~
N1*BY*ACME RETAIL CO*92*0001~
N1*VN*ACME VENDOR INC*92*VEND001~
REF*PO*PO78901~
DTM*004*20260513~
SE*7*0001~
GE*1*1~
IEA*1*000001201~

The BIQ (Beginning Segment for Order Status Inquiry) opens the transaction: function code, level code (L = Line, O = Order, M = Multiple POs), inquiry reference, date. REF*PO identifies the targeted PO. For a batch query, that REF is replaced with a pair of DTM bracketing a range.

Common segments

  • Header — ST, BIQ (Beginning Segment for Order Status Inquiry), REF (specific PO reference), DTM.
  • Parties — N1 loop for Buyer (BY), Vendor (VN), Ship To.
  • Lines — optional LIN loop when the inquiry targets a specific line rather than the whole order.
  • Summary — SE.

When you'll see it

  • Retail — pre-season apparel, promo programs: buyers pepper their suppliers with 869s ahead of critical windows.
  • Manufacturing — monitoring a critical component supply.
  • Distribution — B2B customer service polling the supplier ERP automatically after each web inquiry.

Documentation

The code 869 and the name Order Status Inquiry are public and listed on x12.org/products/transaction-sets. The BIQ02 inquiry-level codes and loop structures live in the proprietary Implementation Guides (TR3); ediverse.io does not redistribute them.