X12

Inbound

Cabela's X12 857 Shipment and Billing Notice

Cabela's Canada (via SPS Commerce)

The EDI 857 (Shipment and Billing Notice) document is used by Cabela's for electronic data interchange. It enables automated processing and compliance with Cabela's's trading partner requirements.

30segments

9loops

6mandatory

Book a demo

← All Cabela's transactions

Schema Reference

30 segments · X12 857 Shipment and Billing Notice

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 Repetition Separator M MIN 1 MAX 1 ID: I65 Type is not applicable; the repetition separator is a delimiter and not a data element; this field provides the delimiter used to separate repeated occurrences of a simple data element or a composite data structure; this value must be different than the data element separator, component element separator, and the segment terminator 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

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

ST01 Transaction Set Identifier Code

M ID 3-3

ST02 Transaction Set Control Number

M AN 4-9

BHT01 Hierarchical Structure Code

M ID 4-4

BHT02 Transaction Set Purpose Code

M ID 2-2

BHT03 Reference Identification

O AN 1-50

BHT04 Date

O DT 8-8

BHT05 Time

O TM 4-8

BHT06 Transaction Type Code

O ID 2-2

HL Loop Repeat: 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

G0501 Number of Units Shipped

C R 1-10

G0502 Unit or Basis for Measurement Code

C ID 2-2

G0503 Weight

C R 1-10

G0504 Unit or Basis for Measurement Code

C ID 2-2

TD504 Transportation Method/Type Code

C ID 1-2

FOB01 Shipment Method of Payment

M ID 2-2

FOB04 Transportation Terms Qualifier Code

O ID 2-2

FOB05 Transportation Terms Code

C ID 3-3

FOB09 Description

C AN 1-80

DTM01 Date/Time Qualifier

M ID 3-3

DTM02 Date

C DT 8-8

N901 Reference Identification Qualifier

M ID 2-3

N902 Reference Identification

C AN 1-50

N903 Free-form Description

C AN 1-45

PER01 Contact Function Code

M ID 2-2

PER02 Name

O AN 1-60

PER03 Communication Number Qualifier

C ID 2-2

PER04 Communication Number

C AN 1-256

PER05 Communication Number Qualifier

C ID 2-2

PER06 Communication Number

C AN 1-256

PER07 Communication Number Qualifier

C ID 2-2

PER08 Communication Number

C AN 1-256

CUR01 Entity Identifier Code

M ID 2-3

CUR02 Currency Code

M ID 3-3

N1 Loop Repeat: 10

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

TDS01 Amount

M N2 1-15

N901 Reference Identification Qualifier

M ID 2-3

N902 Reference Identification

C AN 1-50

N903 Free-form Description

C AN 1-45

ISS01 Number of Units Shipped

C R 1-10

ISS02 Unit or Basis for Measurement Code

C ID 2-2

ISS03 Weight

C R 1-10

ISS04 Unit or Basis for Measurement Code

C ID 2-2

SAC Loop Repeat: 25

SAC01 Allowance or Charge Indicator

M ID 1-1

SAC02 Service, Promotion, Allowance, or Charge Code

C ID 4-4

SAC05 Amount

O N2 1-15

SAC15 Description

C AN 1-80

N1 Loop Repeat: 10

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

N201 Name

M AN 1-60

N301 Address Information

M AN 1-55

N302 Address Information

O AN 1-55

N401 City Name

O AN 2-30

N402 State or Province Code

C ID 2-2

N403 Postal Code

O ID 3-15

N404 Country Code

C ID 2-3

IT1 Loop Repeat: 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

IT108 Product/Service ID Qualifier

C ID 2-2

IT109 Product/Service ID

C AN 1-48

TD401 Special Handling Code

C ID 2-3

TD404 Description

C AN 1-80

TD405 Yes/No Condition or Response Code

O ID 1-1

TC201 Commodity Code Qualifier

M ID 1-1

TC202 Commodity Code

M AN 1-30

CTP02 Price Identifier Code

C ID 3-3

CTP08 Monetary Amount

O R 1-18

N901 Reference Identification Qualifier

M ID 2-3

N902 Reference Identification

C AN 1-50

N903 Free-form Description

C AN 1-45

MEA02 Measurement Qualifier

O ID 1-3

MEA03 Measurement Value

C R 1-20

PID Loop Repeat: 25

PID01 Item Description Type

M ID 1-1

PID05 Description

C AN 1-80

SAC Loop Repeat: 25

SAC01 Allowance or Charge Indicator

M ID 1-1

SAC02 Service, Promotion, Allowance, or Charge Code

C ID 4-4

SAC05 Amount

O N2 1-15

SAC15 Description

C AN 1-80

SE01 Number of Included Segments

M N0 1-10

SE02 Transaction Set Control Number

M AN 4-9

How It Works

Automating Cabela's 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 Cabela's EDI 857 (Shipment and Billing Notice) documents automatically — syncing data to your system in real time with no manual intervention required.

Cabela's EDI 857 FAQ

Common questions about 857 Shipment and Billing Notice transactions with Cabela's.

What is a Cabela's EDI 857 Shipment and Billing Notice?

The Cabela's 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 Cabela's and their suppliers, carriers, or partners. Stacksync processes Cabela's 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 Cabela's's requirements in real time.

How does Stacksync automate Cabela's EDI 857 Shipment and Billing Notice transactions?

Stacksync handles Cabela's 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 Cabela's 857 document meets their specific formatting requirements before transmission or after receipt.

What are common Cabela's EDI 857 errors and how do I fix them?

Common errors in Cabela's 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 Cabela's 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 Cabela's EDI 857 with Stacksync?

Most Cabela's 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 Cabela's's 857 format and your system, running test transactions, and completing Cabela's's certification process if required. Stacksync includes pre-built mappings for Cabela's'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 Cabela's EDI 857 field mappings in Stacksync?

Yes. Stacksync provides a visual field mapping tool that lets you define exactly how Cabela's 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 Cabela's updates their 857 specification, Stacksync highlights the affected mappings and suggests adjustments, ensuring your integration stays compliant without a full reconfiguration.

Ready to automate Cabela's EDI?