X12
Inbound

Stater Bros. Markets X12 857 Shipment and Billing Notice

Stater Bros. Markets
The EDI 857 (Shipment and Billing Notice) document is used by Stater Bros. Markets for electronic data interchange. It enables automated processing and compliance with Stater Bros. Markets's trading partner requirements.
17segments
8loops
6mandatory

Schema Reference

17 segments · X12 857 Shipment and Billing Notice

ISA ISA Interchange Control Header
Mandatory Max: 1
ISA01 Authorization Information Qualifier
M ID 2-2
ISA02 Authorization Information
M AN 10-10
ISA03 Security Information Qualifier
M ID 2-2
ISA04 Security Information
M AN 10-10
ISA05 Interchange ID Qualifier
M ID 2-2
ISA06 Interchange Sender ID
M AN 15-15
ISA07 Interchange ID Qualifier
M ID 2-2
ISA08 Interchange Receiver ID
M AN 15-15
ISA09 Interchange Date
M DT 6-6
ISA10 Interchange Time
M TM 4-4
ISA11 Interchange Control Standards Identifier
M ID 1-1
ISA12 Interchange Control Version Number
M ID 5-5
ISA13 Interchange Control Number
M N0 9-9
ISA14 Acknowledgment Requested
M ID 1-1
ISA15 Usage Indicator
M ID 1-1
GS GS Functional Group Header
Mandatory Max: 1
GS01 Functional Identifier Code
M ID 2-2
GS02 Application Sender's Code
M AN 2-15
GS03 Application Receiver's Code
M AN 2-15
GS04 Date
M DT 8-8
GS05 Time
M TM 4-8
GS06 Group Control Number
M N0 1-9
GS07 Responsible Agency Code
M ID 1-2
GS08 Version / Release / Industry Identifier Code
M AN 1-12
ST Transaction Set Header
Mandatory Max: 1
ST01 Transaction Set Identifier Code
M ID 3-3
ST02 Transaction Set Control Number
M AN 4-9
BHT Beginning of Hierarchical Transaction
Mandatory Max: 1
BHT01 Hierarchical Structure Code
M ID 4-4
BHT02 Transaction Set Purpose Code
M ID 2-2
BHT03 Reference Identification
O AN 1-30
BHT04 Date
O DT 8-8
BHT06 Transaction Type Code
O ID 2-2
HL Loop Repeat: 1
HL Hierarchical Level
Mandatory Max: 1
HL01 Hierarchical ID Number
M AN 1-12
HL02 Hierarchical Parent ID Number
O AN 1-12
HL03 Hierarchical Level Code
M ID 1-2
G05 Loop Repeat: 1
G05 Total Shipment Information
Optional Max: 1
G0501 Number of Units Shipped
C R 1-10
G0502 Unit or Basis for Measurement Code
C ID 2-2
DTM Date/Time Reference
Optional Max: 5
DTM01 Date/Time Qualifier
M ID 3-3
DTM02 Date
C DT 8-8
N1 Loop Repeat: 10
N1 Name
Optional Max: 1
N101 Entity Identifier Code
M ID 2-3
N102 Name
C AN 1-60
N103 Identification Code Qualifier
C ID 1-2
N104 Identification Code
C AN 2-80
TDS Loop Repeat: 1
TDS Total Monetary Value Summary
Optional Max: 1
TDS01 Amount
M N2 1-15
N9 Reference Identification
N901 Reference Identification Qualifier
M ID 2-3
N902 Reference Identification
C AN 1-30
PAL Loop Repeat: 1
PAL Pallet Information
Optional Max: 1
PAL01 Pallet Type Code
O ID 1-2
MAN Marks and Numbers
Optional Max: 10
MAN01 Marks and Numbers Qualifier
M ID 1-2
MAN02 Marks and Numbers
M AN 1-48
IT1 Loop Repeat: 1
IT1 Baseline Item Data (Invoice)
Optional Max: 1
IT101 Assigned Identification
O AN 1-20
IT102 Quantity Invoiced
C R 1-10
IT103 Unit or Basis for Measurement Code
C ID 2-2
IT104 Unit Price
C R 1-17
IT106 Product/Service ID Qualifier
C ID 2-2
IT107 Product/Service ID
C AN 1-48
PO4 Item Physical Details
Optional Max: 1
PO401 Pack
O N0 1-6
PID Loop Repeat: 25
PID Product/Item Description
Optional Max: 1
PID01 Item Description Type
M ID 1-1
PID05 Description
C AN 1-80
SAC Loop Repeat: 25
SAC Service, Promotion, Allowance, or Charge Information
Optional Max: 1
SAC01 Allowance or Charge Indicator
M ID 1-1
SAC02 Service, Promotion, Allowance, or Charge Code
C ID 4-4
SAC08 Rate
O R 1-9
SE Transaction Set Trailer
Mandatory Max: 1
SE01 Number of Included Segments
M N0 1-10
SE02 Transaction Set Control Number
M AN 4-9
How It Works

Automating Stater Bros. Markets EDI 857

Stacksync validates, transforms, and delivers your 857 transactions automatically — so your team can focus on operations, not EDI compliance.

Validate
Transform
Route
Monitor
Stacksync processes Stater Bros. Markets EDI 857 (Shipment and Billing Notice) documents automatically — syncing data to your system in real time with no manual intervention required.

Stater Bros. Markets EDI 857 FAQ

Common questions about 857 Shipment and Billing Notice transactions with Stater Bros. Markets.

What is a Stater Bros. Markets EDI 857 Shipment and Billing Notice?

The Stater Bros. Markets EDI 857 Shipment and Billing Notice is an X12 transaction set used to exchange Shipment and Billing Notice data electronically between trading partners. As a inbound document, it standardizes the communication of Shipment and Billing Notice information between Stater Bros. Markets and their suppliers, carriers, or partners. Stacksync processes Stater Bros. Markets 857 transactions automatically, parsing the X12 segments and mapping them to the corresponding records in your ERP, WMS, or database. This eliminates manual data entry, reduces errors, and ensures your systems stay in sync with Stater Bros. Markets's requirements in real time.

How does Stacksync automate Stater Bros. Markets EDI 857 Shipment and Billing Notice transactions?

Stacksync handles Stater Bros. Markets EDI 857 Shipment and Billing Notice transactions through an automated pipeline: receive the X12 document, validate the envelope and segment structure, map fields to your system's schema, and sync the data in real time. For inbound 857 transactions, Stacksync either generates the document from your system's data or processes incoming documents and routes them to the correct records. The platform includes built-in compliance validation so every Stater Bros. Markets 857 document meets their specific formatting requirements before transmission or after receipt.

What are common Stater Bros. Markets EDI 857 errors and how do I fix them?

Common errors in Stater Bros. Markets EDI 857 Shipment and Billing Notice transactions include missing mandatory segments, invalid qualifier codes, incorrect date or time formats, and data values exceeding maximum field lengths. Reference number mismatches between related documents (e.g., PO numbers that don't match) also cause rejections. Stacksync validates Stater Bros. Markets 857 documents against known requirements before transmission and after receipt, catching errors proactively. When issues occur, the platform provides human-readable error descriptions with the specific segment and element that failed, rather than raw X12 error codes.

How long does it take to set up Stater Bros. Markets EDI 857 with Stacksync?

Most Stater Bros. Markets EDI 857 Shipment and Billing Notice integrations with Stacksync go live within 3 to 5 business days. The setup involves authenticating your EDI connection (AS2, SFTP, or VAN), configuring field mappings between Stater Bros. Markets's 857 format and your system, running test transactions, and completing Stater Bros. Markets's certification process if required. Stacksync includes pre-built mappings for Stater Bros. Markets's most common 857 configurations, which accelerates the setup. Your team can monitor the integration from a single dashboard without managing EDI infrastructure directly.

Can I customize Stater Bros. Markets EDI 857 field mappings in Stacksync?

Yes. Stacksync provides a visual field mapping tool that lets you define exactly how Stater Bros. Markets EDI 857 segments and elements map to your system's fields. You can set data transformations (date format conversion, code translation tables), conditional routing rules, and default values for optional fields. The mappings are version-controlled, so changes can be reviewed and rolled back if needed. If Stater Bros. Markets updates their 857 specification, Stacksync highlights the affected mappings and suggests adjustments, ensuring your integration stays compliant without a full reconfiguration.

Ready to automate Stater Bros. Markets EDI?

a blue checkmark icon
POC from integration engineers
a blue checkmark icon
No-code EDI setup
a blue checkmark icon
Real-time compliance monitoring
a blue checkmark icon
White-glove onboarding