Border States EDI 867 Product Transfer Report

Schema Reference

23 segments · X12 867 Product Transfer and Resale Report

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

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

BPT01 Transaction Set Purpose Code

M ID 2-2

BPT02 Reference Identification

O AN 1-30

BPT03 Date

M DT 8-8

BPT04 Report Type Code

O ID 2-2

DTM01 Date/Time Qualifier

M ID 3-3

DTM02 Date

C DT 8-8

N1 Loop Repeat: 5

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

N401 City Name

O AN 2-30

N402 State or Province Code

O ID 2-2

N403 Postal Code

O ID 3-15

N404 Country Code

O ID 2-3

PTD Loop Repeat: 5

PTD01 Product Transfer Type Code

M ID 2-2

PTD04 Reference Identification Qualifier

C ID 2-3

PTD05 Reference Identification

C AN 1-30

N1 Loop Repeat: 5

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

N401 City Name

O AN 2-30

N402 State or Province Code

O ID 2-2

N403 Postal Code

O ID 3-15

N404 Country Code

O ID 2-3

PER01 Contact Function Code

M ID 2-2

PER02 Name

O AN 1-60

QTY Loop

QTY01 Quantity Qualifier

M ID 2-2

QTY02 Quantity

C R 1-15

LIN01 Assigned Identification

O AN 1-20

LIN02 Product/Service ID Qualifier

M ID 2-2

LIN03 Product/Service ID

M AN 1-48

LIN04 Product/Service ID Qualifier

C ID 2-2

LIN05 Product/Service ID

C AN 1-48

LIN06 Product/Service ID Qualifier

C ID 2-2

LIN07 Product/Service ID

C AN 1-48

LIN08 Product/Service ID Qualifier

C ID 2-2

LIN09 Product/Service ID

C AN 1-48

UIT02 Unit Price

C R 1-17

UIT03 Basis of Unit Price Code

O ID 2-2

AMT01 Amount Qualifier Code

M ID 1-3

AMT02 Monetary Amount

M R 1-18

PID01 Item Description Type

M ID 1-1

PID05 Description

C AN 1-80

REF01 Reference Identification Qualifier

M ID 2-3

REF02 Reference Identification

C AN 1-30

DTM01 Date/Time Qualifier

M ID 3-3

DTM02 Date

C DT 8-8

CUR01 Entity Identifier Code

M ID 2-3

CUR02 Currency Code

M ID 3-3

CTT Loop Repeat: 1

CTT01 Number of Line Items

M N0 1-6

SE01 Number of Included Segments

M N0 1-10

SE02 Transaction Set Control Number

M AN 4-9

Automating Border States EDI 867

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

Validate

Transform

Route

Monitor

Stacksync syncs Border States 867 POS and product movement data to your analytics or planning system — giving you store-level sales visibility for better demand forecasting and replenishment.

Border States EDI 867 FAQ

Common questions about 867 Product Transfer and Resale Report transactions with Border States.

How long does it take to set up Border States EDI with Stacksync?

Most suppliers are fully connected and processing live Border States 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 Border States?

No. Stacksync handles the entire EDI transport layer. We connect directly to Border States'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 Border States 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 Border States?

Stacksync supports all EDI document types required by Border States — 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 Border States 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 Border States's EDI network and your system in real time.

What happens when Border States updates their EDI specifications?

Stacksync monitors Border States'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.