To start and identify an interchange of zero or more functional groups and interchange-related control segments
Zappos X12 846 Inventory Inquiry/Advice
X12 846 (Inventory Inquiry/Advice) is the EDI transaction exchanged between Zappos (Zappos (via DSCO (dba Rithum))) and its trading partners. Stacksync handles full compliance, mapping, and real-time delivery.
- Segments
- 16
- Loops
- 5
- X12 846
- All partners ↗
Transaction context
Where 846 Inventory Inquiry/Advice fits on Zappos (via DSCO (dba Rithum))
- Zappos channels
- 1 of 1
- Trading partners
- 117
- Channels
- 137
1 of Zappos's 1 channel carries 846
partners across the Stacksync network trade 846
channels network-wide carry 846
Most common alongside 846
On Rithum, 846 runs on 24 channels.
The 846 publishes inventory positions between trading partners: quantities on hand, committed, and available by item and location. Retailers and marketplaces depend on it to decide what to display as sellable, which makes it foundational to drop-ship and e-commerce programs where the supplier holds the stock. Many retailers require the feed daily or multiple times per day, so stale or inaccurate data translates directly into oversells and cancelled orders. Typically sent by a supplier, warehouse, or 3PL to a retailer, marketplace, or distributor; a buyer can also send it as an inventory inquiry.
When it fires: A scheduled inventory snapshot, often daily or intraday per retailer requirements, or a stock-status change that must be pushed to selling channels.
Common 846 rejection causes
- Incorrect BIA transaction purpose codes (original 00 vs replacement 05 vs incremental 25), causing feeds to duplicate or overwrite existing inventory data.
- Missing DTM 007 effective date, leaving the inventory snapshot without a temporal anchor and making the data unreliable for replenishment decisions.
- Product identifier and unit-of-measure mismatches between partners (SKU/UPC/GTIN, EA vs CS), causing mapping failures and misread quantities.
- Inaccurate or infrequent updates relative to the retailer's required cadence, leading to oversold items and cancellations.
Specification summary
X12 846 Inventory Inquiry/Advice at the element level
The X12 846 specification defines 26 segments carrying 77 data elements, 48 of which are mandatory.
- Segments
- 26
- Data elements
- 77
- Mandatory elements
- 48
| Segment | Elements | Mandatory |
|---|---|---|
| BIA | 5 | 4 |
| N1 | 4 | 1 |
| LIN | 7 | 2 |
| REF | 2 | 1 |
| QTY | 2 | 1 |
| DTM | 4 | 1 |
| SCH | 7 | 4 |
| LS | 1 | 1 |
| LE | 1 | 1 |
| N2 | 2 | 1 |
Key identifiers in 846
- Transaction Set Purpose Code
- Report Type Code
- Reference Identification
- Date
- Entity Identifier Code
- Product/Service ID Qualifier
- Product/Service ID
- Reference Identification Qualifier
Full segment guideline — 16 segments 5 loops · X12 846 Inventory Inquiry/Advice
To indicate the beginning of a functional group and to provide control information
To indicate the start of a transaction set and to assign a control number
To indicate the beginning of an Inventory Inquiry/Advice Transaction Set
To specify the currency (dollars, pounds, francs, etc.) used in a transaction
To specify identifying information
LIN Loop Repeat: 10,000
To specify basic item identification data
To describe a product or process in coded or free-form format
To specify pertinent dates and times
To specify pricing information
To indicate the end of the transaction set and provide the count of the transmitted segments (including the beginning (ST) and ending (SE) segments)
QTY Loop Repeat: 99
To specify quantity information
To specify physical measurements or counts, including dimensions, tolerances, variances, and weights (See Figures Appendix for example of use of C001)
SCH Loop Repeat: 25
To specify the data for scheduling a specific line-item
LS Loop Repeat: 1
To indicate that the next segment begins a loop
REF Loop
To indicate that the loop immediately preceding this segment is complete
Trading partners
4+ trading partners.
And every channel covered.
We connect to every major retailer, distributor, and 3PL on the EDI network. Type to search the directory, or browse the full catalogue.
No trading partner matches your search.
Browse the full directory
Zappos Zappos (via DSCO (dba Rithum)) EDI 846 FAQ
Common questions about 846 Inventory Inquiry/Advice on the Zappos (via DSCO (dba Rithum)) channel.
What is X12 846 Inventory Inquiry/Advice?
X12 846 (Inventory Inquiry/Advice) is the EDI transaction set used to exchange inventory inquiry/advice data. Zappos's Zappos (via DSCO (dba Rithum)) channel requires it from trading partners.
Does Zappos Zappos (via DSCO (dba Rithum)) require 846 for trading partners?
Yes, Zappos (Zappos (via DSCO (dba Rithum))) supports X12 846 Inventory Inquiry/Advice. Stacksync handles the full integration so your team can focus on operations.
How fast can I integrate Zappos 846 with Stacksync?
Most companies go live with Zappos 846 on Stacksync in days. Pre-built mappings, no-code setup, and real-time monitoring make EDI compliance straightforward.
Which documents accompany 846 on Zappos (via DSCO (dba Rithum))?
On Zappos (via DSCO (dba Rithum)), X12 846 is typically exchanged alongside 850 Purchase Order, 856 Ship Notice Manifest, 810 Invoice, 870 Order Status Report. Stacksync maps each document into the same ERP or WMS workflow, so the full cycle stays in sync end to end.
Ready to automate your Zappos EDI?
Most teams go live in days, not months. Talk to our team and we'll walk you through your specific setup.
