Canadian Tire Corporation EDI 860 PO Change Request

Schema Reference

16 segments · X12 860 Purchase Order Change Request

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

BCH01 Transaction Set Purpose Code

M ID 2-2

BCH02 Purchase Order Type Code

M ID 2-2

BCH03 Purchase Order Number

M AN 1-22

BCH06 Date

M DT 8-8

BCH11 Date

O DT 8-8

REF01 Reference Identification Qualifier

M ID 2-3

REF02 Reference Identification

C AN 1-30

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-80

DTM01 Date/Time Qualifier

M ID 3-3

DTM02 Date

C DT 8-8

DTM03 Time

C TM 4-8

DTM04 Time Code

O ID 2-2

N1 Loop Repeat: 200

N101 Entity Identifier Code

M ID 2-3

N102 Name

C AN 1-60

N405 Location Qualifier

C ID 1-2

N406 Location Identifier

O AN 1-30

POC Loop

POC01 Assigned Identification

O AN 1-20

POC02 Change or Response Type Code

M ID 2-2

POC03 Quantity Ordered

O R 1-15

POC04 Quantity Left to Receive

C R 1-9

POC06 Unit Price

C R 1-17

POC07 Basis of Unit Price Code

O ID 2-2

POC08 Product/Service ID Qualifier

C ID 2-2

POC09 Product/Service ID

C AN 1-48

POC10 Product/Service ID Qualifier

C ID 2-2

POC11 Product/Service ID

C AN 1-48

POC12 Product/Service ID Qualifier

C ID 2-2

POC13 Product/Service ID

C AN 1-48

CTP02 Price Identifier Code

C ID 3-3

CTP03 Unit Price

C R 1-17

CTP04 Quantity

C R 1-15

CTP09 Basis of Unit Price Code

O ID 2-2

REF01 Reference Identification Qualifier

M ID 2-3

REF02 Reference Identification

C AN 1-30

SDQ01 Unit or Basis for Measurement Code

M ID 2-2

SDQ02 Identification Code Qualifier

O ID 1-2

SDQ03 Identification Code

M AN 2-80

SDQ04 Quantity

M R 1-15

SDQ05 Identification Code

C AN 2-80

SDQ06 Quantity

C R 1-15

SDQ07 Identification Code

C AN 2-80

SDQ08 Quantity

C R 1-15

SDQ09 Identification Code

C AN 2-80

SDQ10 Quantity

C R 1-15

SDQ11 Identification Code

C AN 2-80

SDQ12 Quantity

C R 1-15

SDQ13 Identification Code

C AN 2-80

SDQ14 Quantity

C R 1-15

SDQ15 Identification Code

C AN 2-80

SDQ16 Quantity

C R 1-15

SDQ17 Identification Code

C AN 2-80

SDQ18 Quantity

C R 1-15

SDQ19 Identification Code

C AN 2-80

SDQ20 Quantity

C R 1-15

SDQ21 Identification Code

C AN 2-80

SDQ22 Quantity

C R 1-15

SDQ23 Location Identifier

O AN 1-30

DTM01 Date/Time Qualifier

M ID 3-3

DTM02 Date

C DT 8-8

DTM03 Time

C TM 4-8

DTM04 Time Code

O ID 2-2

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 Canadian Tire Corporation EDI 860

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

Validate

Transform

Route

Monitor

Stacksync detects incoming 860 PO Changes and updates the original order in your ERP automatically. Changed fields are highlighted and your team is notified — so you can review and confirm without manually comparing documents.

Canadian Tire Corporation EDI 860 FAQ

Common questions about 860 Purchase Order Change Request transactions with Canadian Tire Corporation.

How long does it take to set up Canadian Tire Corporation EDI with Stacksync?

Most suppliers are fully connected and processing live Canadian Tire Corporation 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 Canadian Tire Corporation?

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

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

What happens when Canadian Tire Corporation updates their EDI specifications?

Stacksync monitors Canadian Tire Corporation'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.