To start and identify an interchange of zero or more functional groups and interchange-related control segments
Barnes & Noble X12 857 Shipment and Billing Notice
X12 857 (Shipment and Billing Notice) is the EDI transaction exchanged between Barnes & Noble (Barnes & Noble) and its trading partners. Stacksync handles full compliance, mapping, and real-time delivery.
- Segments
- 19
- Loops
- 6
- X12 857
- All partners ↗
Transaction context
Where 857 Shipment and Billing Notice fits on Barnes & Noble
- Barnes & Noble channels
- 1 of 1
- Trading partners
- 3
- Channels
- 3
1 of Barnes & Noble's 1 channel carries 857
partners across the Stacksync network trade 857
channels network-wide carry 857
Most common alongside 857
The 857 consolidates the shipment detail of an 856 and the billing detail of an 810 into one document, giving the recipient data for both receipt planning and payment generation. X12 intends it to replace both documents together, never one of them alone, and notes it is not appropriate in Evaluated Receipts Settlement environments where prices are predetermined. Adoption is narrow and concentrated in grocery and wholesale distribution. Sent by the supplier to the buyer, typically a grocery retailer or wholesaler, covering both the delivery notice and the invoice for a shipment.
When it fires: A supplier ship-confirms an order and issues a single document at shipment that serves as both the ship notice and the invoice.
Common 857 rejection causes
- Hierarchical structure code in the BHT does not match the HL level sequence actually transmitted, so the receiver cannot resolve the shipment/order/pack/item nesting.
- A separate 810 is also sent for the same shipment, duplicating the billing data the 857 already carries and creating double-invoice exceptions.
- Terms or item prices omitted, which invalidates the payment-generation half of the document and forces manual invoice reconciliation.
Specification summary
X12 857 Shipment and Billing Notice at the element level
The X12 857 specification defines 39 segments carrying 112 data elements, 48 of which are mandatory.
- Segments
- 39
- Data elements
- 112
- Mandatory elements
- 48
| Segment | Elements | Mandatory |
|---|---|---|
| BHT | 6 | 2 |
| HL | 3 | 2 |
| FOB | 4 | 1 |
| DTM | 2 | 1 |
| N9 | 3 | 1 |
| PER | 8 | 1 |
| CUR | 2 | 2 |
| N1 | 4 | 1 |
| TDS | 1 | 1 |
| SAC | 4 | 1 |
Key identifiers in 857
- Hierarchical Structure Code
- Transaction Set Purpose Code
- Hierarchical ID Number
- Hierarchical Level Code
- Shipment Method of Payment
- Date/Time Qualifier
- Reference Identification Qualifier
- Contact Function Code
Full segment guideline — 19 segments 6 loops · X12 857 Shipment and Billing Notice
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 define the business hierarchical structure of the transaction set and identify the business application purpose and reference data, i.e., number, date, and time
HL Loop Repeat: 1
To identify dependencies among and the content of hierarchically related groups of data segments
G05 Loop Repeat: 1
To provide totals relating to the shipment
To specify the carrier and sequence of routing and provide transit time information
To specify pertinent dates and times
To indicate the end of the transaction set and provide the count of the transmitted segments (including the beginning (ST) and ending (SE) segments)
To transmit identifying information as specified by the Reference Identification Qualifier
N1 Loop Repeat: 10
To identify a party by type of organization, name, and code
TDS Loop Repeat: 1
To specify the total invoice discounts and amounts
To provide reference to a specific purchase order
LX Loop Repeat: 1
To reference a line number in a transaction set
To describe marking, packaging, loading, and unloading requirements
To indicate identifying marks and numbers for shipping containers
IT1 Loop Repeat: 1
To specify the basic and most frequently used line item data for the invoice and related transactions
To specify the physical qualities, packaging, weights, and dimensions relating to the item
To specify pricing information
Trading partners
3+ 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
Barnes & Noble Barnes & Noble EDI 857 FAQ
Common questions about 857 Shipment and Billing Notice on the Barnes & Noble channel.
What is X12 857 Shipment and Billing Notice?
X12 857 (Shipment and Billing Notice) is the EDI transaction set used to exchange shipment and billing notice data. Barnes & Noble's Barnes & Noble channel requires it from trading partners.
Does Barnes & Noble Barnes & Noble require 857 for trading partners?
Yes, Barnes & Noble (Barnes & Noble) supports X12 857 Shipment and Billing Notice. Stacksync handles the full integration so your team can focus on operations.
How fast can I integrate Barnes & Noble 857 with Stacksync?
Most companies go live with Barnes & Noble 857 on Stacksync in days. Pre-built mappings, no-code setup, and real-time monitoring make EDI compliance straightforward.
Which documents accompany 857 on Barnes & Noble?
On Barnes & Noble, X12 857 is typically exchanged alongside 850 Purchase Order, 810 Invoice, 855 Purchase Order Acknowledgment. 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 Barnes & Noble EDI?
Most teams go live in days, not months. Talk to our team and we'll walk you through your specific setup.
