Backcountry.com EDI 810 Invoice Integration

Schema Reference

24 segments · X12 810 Invoice

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

BIG01 Date

M DT 8-8

BIG02 Invoice Number

M AN 1-22

BIG03 Date

O DT 8-8

BIG04 Purchase Order Number

O AN 1-22

BIG07 Transaction Type Code

O ID 2-2

NTE02 Description

M AN 1-80

CUR01 Entity Identifier Code

M ID 2-3

CUR02 Currency Code

M ID 3-3

CUR04 Entity Identifier Code

O ID 2-3

CUR05 Currency Code

O ID 3-3

REF01 Reference Identification Qualifier

M ID 2-3

REF02 Reference Identification

C AN 1-50

N1 Loop Repeat: 200

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

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

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

ITD01 Terms Type Code

O ID 2-2

ITD02 Terms Basis Date Code

O ID 1-2

ITD03 Terms Discount Percent

O R 1-6

ITD05 Terms Discount Days Due

C N0 1-3

ITD06 Terms Net Due Date

O DT 8-8

ITD07 Terms Net Days

O N0 1-3

ITD12 Description

O AN 1-80

DTM01 Date/Time Qualifier

M ID 3-3

DTM02 Date

C DT 8-8

FOB01 Shipment Method of Payment

M ID 2-2

FOB02 Location Qualifier

C ID 1-2

FOB03 Description

O AN 1-80

FOB06 Location Qualifier

C ID 1-2

FOB07 Description

O AN 1-80

IT1 Loop Repeat: 200,000

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

IT110 Product/Service ID Qualifier

C ID 2-2

IT111 Product/Service ID

C AN 1-48

IT112 Product/Service ID Qualifier

C ID 2-2

IT113 Product/Service ID

C AN 1-48

IT303 Shipment/Order Status Code

C ID 2-2

IT304 Quantity Difference

C R 1-9

CTP02 Price Identifier Code

C ID 3-3

CTP03 Unit Price

C R 1-17

PID Loop Repeat: 1,000

PID01 Item Description Type

M ID 1-1

PID05 Description

C AN 1-80

PO401 Pack

O N0 1-6

TDS01 Amount

M N2 1-15

TDS02 Amount

O N2 1-15

TDS03 Amount

O N2 1-15

TDS04 Amount

O N2 1-15

CAD01 Transportation Method/Type Code

O ID 1-2

CAD04 Standard Carrier Alpha Code

C ID 2-4

CAD05 Routing

C AN 1-35

CAD06 Shipment/Order Status Code

O ID 2-2

CAD07 Reference Identification Qualifier

O ID 2-3

CAD08 Reference Identification

C AN 1-50

CAD09 Service Level Code

O ID 2-2

SAC Loop

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

CTT01 Number of Line Items

M N0 1-6

CTT02 Hash Total

O R 1-10

SE01 Number of Included Segments

M N0 1-10

SE02 Transaction Set Control Number

M AN 4-9

Backcountry.com EDI 810 FAQ

Common questions about 810 Invoice transactions with Backcountry.com.

How long does it take to set up Backcountry.com EDI with Stacksync?

Most suppliers are fully connected and processing live Backcountry.com EDI transactions within 3–5 business days. Stacksync's no-code setup means you don't need developers or EDI consultants — configure your field mappings through our visual interface, run a test cycle, and go live.

Do I need an existing VAN or AS2 connection to trade with Backcountry.com?

No. Stacksync handles the entire EDI transport layer. We connect directly to Backcountry.com's trading partner network through our certified connections. You don't need to manage a separate VAN subscription, AS2 certificates, or SFTP configurations.

How does Stacksync help with Backcountry.com compliance?

Stacksync improves compliance scores by eliminating manual processing delays. Purchase Orders sync to your system in real time, ASNs are generated automatically when you ship, and invoices are validated with three-way matching before submission. Real-time monitoring alerts you to issues before they become chargebacks.

What EDI document types does Stacksync support for Backcountry.com?

Stacksync supports all EDI document types required by Backcountry.com — including Purchase Orders (850), Invoices (810), ASNs (856), PO Acknowledgments (855), and more. Our platform handles the full lifecycle from order to payment automatically.

Can I connect Backcountry.com EDI to my existing ERP or WMS?

Yes. Stacksync integrates with any system that has a database or API — including SAP, Oracle, NetSuite, Microsoft Dynamics, and custom-built ERPs. Data flows bidirectionally between Backcountry.com's EDI network and your system in real time.

What happens when Backcountry.com updates their EDI specifications?

Stacksync monitors Backcountry.com's EDI spec changes and updates our mappings proactively. When a change affects your integration, we notify you and apply updates — so you stay compliant without scrambling to decode new implementation guides.