Canadian Tire
/
Invoice
  • Specification
  • EDI Inspector
Stedi maintains this guide based on public documentation from Canadian Tire. Contact Canadian Tire for official EDI specifications. To report any errors in this guide, please contact us.
Go to Stedi Network
Canadian Tire logo

X12 810 Invoice

X12 Release 4010

This Draft Standard for Trial Use contains the format and establishes the data contents of the Invoice Transaction Set (810) for use within the context of an Electronic Data Interchange (EDI) environment. The transaction set can be used to provide for customary and established business and industry practice relative to the billing for goods and services provided.

Delimiters
  • ~ Segment
  • * Element
  • > Component
EDI samples
View the latest version of this implementation guide as an interactive webpage
https://www.stedi.com/app/guides/view/canadian-tire/invoice/01HW5S3SSX031RCTPX0GNMETJM
Powered by
Build EDI implementation guides at stedi.com
Overview
ISA
-
Interchange Control Header
Max use 1
Required
GS
-
Functional Group Header
Max use 1
Required
heading
ST
010
Transaction Set Header
Max use 1
Required
BIG
020
Beginning Segment for Invoice
Max use 1
Required
CUR
040
Currency
Max use 1
Required
REF
050
Reference Identification
Max use 12
Required
N1 Loop Remit To
detail
IT1 Loop
IT1
010
Baseline Item Data (Invoice)
Max use 1
Required
PID Loop
GE
-
Functional Group Trailer
Max use 1
Required
IEA
-
Interchange Control Trailer
Max use 1
Required
ISA

Interchange Control Header

RequiredMax use 1

To start and identify an interchange of zero or more functional groups and interchange-related control segments

Example
ISA-01
I01
Authorization Information Qualifier
Required
Identifier (ID)

Code to identify the type of information in the Authorization Information

00
No Authorization Information Present (No Meaningful Information in I02)
ISA-02
I02
Authorization Information
Required
String (AN)
Min 10Max 10

Information used for additional identification or authorization of the interchange sender or the data in the interchange; the type of information is set by the Authorization Information Qualifier (I01)

ISA-03
I03
Security Information Qualifier
Required
Identifier (ID)

Code to identify the type of information in the Security Information

00
No Security Information Present (No Meaningful Information in I04)
ISA-04
I04
Security Information
Required
String (AN)
Min 10Max 10

This is used for identifying the security information about the interchange sender or the data in the interchange; the type of information is set by the Security Information Qualifier (I03)

ISA-05
I05
Interchange ID Qualifier
Required
Identifier (ID)
Min 2Max 2

Qualifier to designate the system/method of code structure used to designate the sender or receiver ID element being qualified

Codes
ISA-06
I06
Interchange Sender ID
Required
String (AN)
Min 15Max 15

Identification code published by the sender for other parties to use as the receiver ID to route data to them; the sender always codes this value in the sender ID element

ISA-07
I05
Interchange ID Qualifier
Required
Identifier (ID)
Min 2Max 2

Qualifier to designate the system/method of code structure used to designate the sender or receiver ID element being qualified

Codes
ISA-08
I07
Interchange Receiver ID
Required
String (AN)
Min 15Max 15

Identification code published by the receiver of the data; When sending, it is used by the sender as their sending ID, thus other parties sending to them will use this as a receiving ID to route data to them

ISA-09
I08
Interchange Date
Required
Date (DT)
YYMMDD format

Date of the interchange

ISA-10
I09
Interchange Time
Required
Time (TM)
HHMM format

Time of the interchange

ISA-11
I10
Interchange Control Standards Identifier
Required
Identifier (ID)

Code to identify the agency responsible for the control standard used by the message that is enclosed by the interchange header and trailer

U
U.S. EDI Community of ASC X12, TDCC, and UCS
ISA-12
I11
Interchange Control Version Number
Required
Identifier (ID)

This version number covers the interchange control segments

00401
Draft Standards for Trial Use Approved for Publication by ASC X12 Procedures Review Board through October 1997
ISA-13
I12
Interchange Control Number
Required
Numeric (N0)
Min 9Max 9

A control number assigned by the interchange sender

ISA-14
I13
Acknowledgment Requested
Required
Identifier (ID)
Min 1Max 1

Code sent by the sender to request an interchange acknowledgment (TA1)

0
No Acknowledgment Requested
1
Interchange Acknowledgment Requested
ISA-15
I14
Usage Indicator
Required
Identifier (ID)
Min 1Max 1

Code to indicate whether data enclosed by this interchange envelope is test, production or information

I
Information
P
Production Data
T
Test Data
ISA-16
I15
Component Element Separator
Required
String (AN)
Min 1Max 1

Type is not applicable; the component element separator is a delimiter and not a data element; this field provides the delimiter used to separate component data elements within a composite data structure; this value must be different than the data element separator and the segment terminator

>
Component Element Separator

Functional Group Header

RequiredMax use 1

To indicate the beginning of a functional group and to provide control information

Example
GS-01
479
Functional Identifier Code
Required
Identifier (ID)

Code identifying a group of application related transaction sets

IN
Invoice Information (810,819)
GS-02
142
Application Sender's Code
Required
String (AN)
Min 2Max 15

Code identifying party sending transmission; codes agreed to by trading partners

GS-03
124
Application Receiver's Code
Required
String (AN)
Min 2Max 15

Code identifying party receiving transmission. Codes agreed to by trading partners

Required
Date (DT)
CCYYMMDD format

Date expressed as CCYYMMDD

Required
Time (TM)
HHMM, HHMMSS, HHMMSSD, or HHMMSSDD format

Time expressed in 24-hour clock time as follows: HHMM, or HHMMSS, or HHMMSSD, or HHMMSSDD, where H = hours (00-23), M = minutes (00-59), S = integer seconds (00-59) and DD = decimal seconds; decimal seconds are expressed as follows: D = tenths (0-9) and DD = hundredths (00-99)

GS-06
28
Group Control Number
Required
Numeric (N0)
Min 1Max 9

Assigned number originated and maintained by the sender

GS-07
455
Responsible Agency Code
Required
Identifier (ID)
Min 1Max 2

Code used in conjunction with Data Element 480 to identify the issuer of the standard

T
Transportation Data Coordinating Committee (TDCC)
X
Accredited Standards Committee X12
GS-08
480
Version / Release / Industry Identifier Code
Required
String (AN)

Code indicating the version, release, subrelease, and industry identifier of the EDI standard being used, including the GS and GE segments; if code in DE455 in GS segment is X, then in DE 480 positions 1-3 are the version number; positions 4-6 are the release and subrelease, level of the version; and positions 7-12 are the industry or trade association identifiers (optionally assigned by user); if code in DE455 in GS segment is T, then other formats are allowed

004010
Draft Standards Approved for Publication by ASC X12 Procedures Review Board through October 1997

Heading

ST
010
Heading > ST

Transaction Set Header

RequiredMax use 1

To indicate the start of a transaction set and to assign a control number

Example
ST-01
143
Transaction Set Identifier Code
Required
Identifier (ID)

Code uniquely identifying a Transaction Set

  • The transaction set identifier (ST01) used by the translation routines of the interchange partners to select the appropriate transaction set definition (e.g., 810 selects the Invoice Transaction Set).
810
Invoice
ST-02
329
Transaction Set Control Number
Required
Numeric (N)
Min 4Max 9

Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set

BIG
020
Heading > BIG

Beginning Segment for Invoice

RequiredMax use 1

To indicate the beginning of an invoice transaction set and transmit identifying numbers and dates

Usage notes

Example: BIG2017040300001234*99990001***00

Example
Required
Date (DT)
CCYYMMDD format

Date expressed as CCYYMMDD

  • BIG01 is the invoice issue date.
BIG-02
76
Invoice Number
Required
String (AN)
Min 5Max 22

Identifying number assigned by issuer

BIG-04
324
Purchase Order Number
Required
String (AN)
Min 1Max 22

Identifying number for Purchase Order assigned by the orderer/purchaser

Usage notes

CTC PO Number

Format: (NNNNNNNN)

BIG-08
353
Transaction Set Purpose Code
Required
Identifier (ID)
Min 2Max 2

Code identifying purpose of transaction set

CUR
040
Heading > CUR

Currency

RequiredMax use 1

To specify the currency (dollars, pounds, francs, etc.) used in a transaction

Usage notes

The currency in the invoice must match the currency indicated in the 850 PO. All PO's are Canadian dollars (CAD) unless indicated otherwise by the presence of a CUR segment. CTC currently only processes Canadian and United States dollars via electronic invoice.

Example: CURBYCAD

Example
CUR-01
98
Entity Identifier Code
Required
Identifier (ID)

Code identifying an organizational entity, a physical location, property or an individual

BY
Buying Party (Purchaser)
CUR-02
100
Currency Code
Required
Identifier (ID)

Code (Standard ISO) for country in whose currency the charges are specified

CAD
Canadian Dollar
USD
US Dollar
REF
050
Heading > REF

Reference Identification

RequiredMax use 12

To specify identifying information

Usage notes

Example: REFVR9999

Example
REF-01
128
Reference Identification Qualifier
Required
Identifier (ID)

Code qualifying the Reference Identification

VR
Vendor ID Number
REF-02
127
Reference Identification
Required
String (AN)
Min 1Max 30

Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier

Usage notes

CTC Assigned Vendor Number

Format: (NNNN)

N1 Loop Remit To
RequiredMax >1
Variants (all may be used)
N1 Loop Ship To or Party for whom Item is Ultimately Intended
N1
070
Heading > N1 Loop Remit To > N1

Name

RequiredMax use 1

To identify a party by type of organization, name, and code

Usage notes

Example: N1RIBOB’S BAIT SHOPPE1123456789

Example
If either Identification Code Qualifier (N1-03) or Identification Code (N1-04) is present, then the other is required
N1-01
98
Entity Identifier Code
Required
Identifier (ID)

Code identifying an organizational entity, a physical location, property or an individual

RI
Remit To
Optional
String (AN)
Min 1Max 60

Free-form name

N1-03
66
Identification Code Qualifier
Required
Identifier (ID)

Code designating the system/method of code structure used for Identification Code (67)

1
D-U-N-S Number, Dun & Bradstreet
N1-04
67
Identification Code
Optional
String (AN)
Min 2Max 80

Code identifying a party or other code

  • This segment, used alone, provides the most efficient method of providing organizational identification. To obtain this efficiency the "ID Code" (N104) must provide a key to the table maintained by the transaction processing party.
N3
090
Heading > N1 Loop Remit To > N3

Address Information

OptionalMax use 2

To specify the location of the named party

Usage notes

Example: N3*1234 ELM DRIVE

Example
N3-01
166
Address Information
Required
String (AN)
Min 1Max 55

Address information

N4
100
Heading > N1 Loop Remit To > N4

Geographic Location

OptionalMax use 1

To specify the geographic place of the named party

Usage notes

Example: N4TIMBUKTUONA1A 1A1CA

Example
N4-01
19
City Name
Required
String (AN)
Min 2Max 30

Free-form text for city name

  • A combination of either N401 through N404, or N405 and N406 may be adequate to specify a location.
N4-02
156
State or Province Code
Optional
Identifier (ID)
Min 2Max 2

Code (Standard State/Province) as defined by appropriate government agency

  • N402 is required only if city name (N401) is in the U.S. or Canada.
N4-03
116
Postal Code
Required
Identifier (ID)
Min 3Max 15

Code defining international postal zone code excluding punctuation and blanks (zip code for United States)

N4-04
26
Country Code
Required
Identifier (ID)

Code identifying the country

CA
Canada
MX
Mexico
US
United States of America (the)
N1 Loop Remit To end
N1 Loop Ship To or Party for whom Item is Ultimately Intended
RequiredMax 1
Variants (all may be used)
N1 Loop Remit To
N1
070
Heading > N1 Loop Ship To or Party for whom Item is Ultimately Intended > N1

Name

RequiredMax use 1

To identify a party by type of organization, name, and code

Usage notes

For Direct Ship use of N1 ST segment optional, or use N1STCT RETAIL - DIRECT SHIP92016136689000 otherwise same rules as Cross Dock.

Storage:
N101 = “ST” (ship to) and N103 = “9” (distribution center #).

Cross-Dock or Direct Ship:
INVOICE BY STORE
N101 = “MA” (ultimate destination) and N103 = “92” (store #). Send one invoice for each store on the PO. This is the only case where product is shipped to two different destinations, the product being first shipped to a distribution center and then to a store. Partial invoicing should be avoided.
INVOICE BY PO
N101 = “ST” (ship to) and N103 = “9” (distribution center #). Do the same as for a storage order, with the DC code in the N1. The invoice, therefore, becomes a summary level invoice showing the total quantity for each item shipped for the PO. The entire PO must be invoiced, however, if this option is chosen. No partial invoicing is allowed.

Example: N1STA J BILLES92016136689005

Example
If either Identification Code Qualifier (N1-03) or Identification Code (N1-04) is present, then the other is required
N1-01
98
Entity Identifier Code
Required
Identifier (ID)

Code identifying an organizational entity, a physical location, property or an individual

MA
Party for whom Item is Ultimately Intended
ST
Ship To
Optional
String (AN)
Min 1Max 60

Free-form name

N1-03
66
Identification Code Qualifier
Required
Identifier (ID)

Code designating the system/method of code structure used for Identification Code (67)

9
D-U-N-S+4, D-U-N-S Number with Four Character Suffix
92
Assigned by Buyer or Buyer's Agent
N1-04
67
Identification Code
Optional
String (AN)
Min 2Max 80

Code identifying a party or other code

  • This segment, used alone, provides the most efficient method of providing organizational identification. To obtain this efficiency the "ID Code" (N104) must provide a key to the table maintained by the transaction processing party.
N1 Loop Ship To or Party for whom Item is Ultimately Intended end
Heading end

Detail

IT1 Loop
RequiredMax >1
IT1
010
Detail > IT1 Loop > IT1

Baseline Item Data (Invoice)

RequiredMax use 1

To specify the basic and most frequently used line item data for the invoice and related transactions

Usage notes

IT101 is required in order to process your Invoice. The Purchase Order Line Number is provided by CTC within the Purchase Order Transaction (850) - PO1 Segment 01 Element.

When implementing the 810, CTC will change the 850 PO to have Net cost (inclusive of allowances and charges) sent in the PO104. Please return these costs on the Invoice.

Example: IT1199EA9.99*SK012-3456-7

Example
If either Quantity Invoiced (IT1-02), Unit or Basis for Measurement Code (IT1-03) or Unit Price (IT1-04) are present, then the others are required
If either Product/Service ID Qualifier (IT1-06) or Product/Service ID (IT1-07) is present, then the other is required
IT1-01
350
Assigned Identification
Required
String (AN)
Min 1Max 20

Alphanumeric characters assigned for differentiation within a transaction set

  • IT101 is the purchase order line item identification.
Usage notes

Purchase Order Line Number (PO101 in 850).

IT1-02
358
Quantity Invoiced
Optional
Decimal number (R)
Min 1Max 10

Number of units invoiced (supplier units)

Usage notes

Consumer Units

IT1-03
355
Unit or Basis for Measurement Code
Optional
Identifier (ID)

Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken

EA
Each
IT1-04
212
Unit Price
Optional
Decimal number (R)
Min 1Max 15

Price per unit of product, service, commodity, etc.

Usage notes

Net price per unit of product (PO104 in 850). Maximum 4 decimal places.

IT1-06
235
Product/Service ID Qualifier
Required
Identifier (ID)

Code identifying the type/source of the descriptive number used in Product/Service ID (234)

  • IT106 through IT125 provide for ten different product/service IDs for each item. For example: Case, Color, Drawing No., U.P.C. No., ISBN No., Model No., or SKU.
SK
Stock Keeping Unit (SKU)
IT1-07
234
Product/Service ID
Optional
String (AN)
Min 1Max 48

Identifying number for a product or service

Usage notes

Canadian Tire Corporation Product Number

Format: (NNN-NNNN-N)

PID Loop
OptionalMax >1
PID
060
Detail > IT1 Loop > PID Loop > PID

Product/Item Description

RequiredMax use 1

To describe a product or process in coded or free-form format

Usage notes

Example: PIDF***DELUXE TACKLE BOX

Example
PID-01
349
Item Description Type
Required
Identifier (ID)

Code indicating the format of a description

  • If PID01 equals "F", then PID05 is used. If PID01 equals "S", then PID04 is used. If PID01 equals "X", then both PID04 and PID05 are used.
F
Free-form
PID-05
352
Description
Required
String (AN)
Min 1Max 80

A free-form description to clarify the related data elements and their content

PID Loop end
IT1 Loop end
Detail end

Summary

TDS
010
Summary > TDS

Total Monetary Value Summary

RequiredMax use 1

To specify the total invoice discounts and amounts

Usage notes

Example: TDS*102857

Example
TDS-01
610
Amount
Required
Numeric (N2)
Min 1Max 15

Monetary amount

  • TDS01 is the total amount of invoice (including charges, less allowances) before terms discount (if discount is applicable).
Usage notes

Round to two decimal places.

TXI
020
Summary > TXI

Tax Information

OptionalMax use 10

To specify tax information

Usage notes

Example: TXIZZ69.230.13*****123456789

Example
TXI-01
963
Tax Type Code
Required
Identifier (ID)

Code specifying the type of tax

GS
Goods and Services Tax
SP
Quebec Sales Tax
ZZ
Harmonized Sales Tax
TXI-02
782
Monetary Amount
Required
Decimal number (R)
Min 1Max 15

Monetary amount

  • TXI02 is the monetary amount of the tax.
TXI-03
954
Percent
Required
Decimal number (R)
Min 1Max 10

Percentage expressed as a decimal

  • TXI03 is the tax percent expressed as a decimal.
TXI-09
325
Tax Identification Number
Required
String (AN)
Min 1Max 20

Number assigned to a purchaser (buyer, orderer) by a taxing jurisdiction (state, county, etc.); often called a tax exemption number or certificate number

Usage notes

If taxes are charged, Registered Tax Number must be shared in TXI09.

CTT
070
Summary > CTT

Transaction Totals

RequiredMax use 1

To transmit a hash total for a specific element in the transaction set

  • Number of line items (CTT01) is the accumulation of the number of IT1 segments.
    If used, hash total (CTT02) is the sum of the value of quantities invoiced (IT102) for each IT1 segment.
Usage notes

Example: CTT*1

Example
CTT-01
354
Number of Line Items
Required
Numeric (N0)
Min 1Max 6

Total number of line items in the transaction set

SE
080
Summary > SE

Transaction Set Trailer

RequiredMax use 1

To indicate the end of the transaction set and provide the count of the transmitted segments (including the beginning (ST) and ending (SE) segments)

Example
SE-01
96
Number of Included Segments
Required
Numeric (N0)
Min 1Max 10

Total number of segments included in a transaction set including ST and SE segments

SE-02
329
Transaction Set Control Number
Required
Numeric (N)
Min 4Max 9

Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set

Summary end

Functional Group Trailer

RequiredMax use 1

To indicate the end of a functional group and to provide control information

Example
GE-01
97
Number of Transaction Sets Included
Required
Numeric (N0)
Min 1Max 6

Total number of transaction sets included in the functional group or interchange (transmission) group terminated by the trailer containing this data element

GE-02
28
Group Control Number
Required
Numeric (N0)
Min 1Max 9

Assigned number originated and maintained by the sender

Interchange Control Trailer

RequiredMax use 1

To define the end of an interchange of zero or more functional groups and interchange-related control segments

Example
IEA-01
I16
Number of Included Functional Groups
Required
Numeric (N0)
Min 1Max 5

A count of the number of functional groups included in an interchange

IEA-02
I12
Interchange Control Number
Required
Numeric (N0)
Min 9Max 9

A control number assigned by the interchange sender

EDI Samples

PROCESS HANDLING - AOM CHANNEL - CROSS DOCK (Inv per PO) MULTIPLE SKUs

ISA*00* *00* *ZZ*SENDER *ZZ*RECEIVER *240506*2055*U*00401*000000001*0*T*>~
GS*IN*SENDERGS*RECEIVERGS*20240506*205538*000000001*X*004010~
BIG*20170403*00001236**99991235****00~
CUR*BY*CAD~
REF*VR*9999~
N1*RI* ABC COMPANY *1*123456789~
N1*ST*A J BILLES*9*2016136689005~
IT1*1*10*EA*4.03**SK*099-9998-6~
PID*F****MOTOMASTER OIL FILTER~
IT1*2*40*EA*7.44**SK*099-9999-9~
PID*F****PERSONA WIDE SLOT TOASTER~
TDS*38851~
TXI*GS*16.90*0.05******123456789~
TXI*SP*33.71*0.09975******2315798~
CTT*2~
GE*1*000000001~
IEA*1*000000001~

PROCESS HANDLING - AOM CHANNEL - CROSS DOCK or Direct Shipto Store (Inv per Store) MULTIPLE SKUs

ISA*00* *00* *ZZ*SENDER *ZZ*RECEIVER *240506*2055*U*00401*000000001*0*T*>~
GS*IN*SENDERGS*RECEIVERGS*20240506*205506*000000001*X*004010~
BIG*20170630*00001252**01132459****00~
CUR*BY*CAD~
REF*VR*9999~
N1*RI* ABC COMPANY *1*123456789~
N1*MA* *92*0330~
IT1*1*20*EA*7.44**SK*099-9999-9~
PID*F****PERSONA WIDE SLOT TOASTER~
TDS*15624~
TXI*GS*7.44*0.05******123456789~
CTT*1~
BIG*20170630*00001253**01132459****00~
CUR*BY*CAD~
REF*VR*9999~
N1*RI* ABC COMPANY *1*123456789~
N1*MA* *92*0397~
IT1*1*10*EA*7.44**SK*099-9999-9~
PID*F****PERSONA WIDE SLOT TOASTER~
IT1*2*5*EA*4.03**SK*099-9998-6~
PID*F****MOTOMASTER OIL FILTER~
TDS*9928~
TXI*GS*4.73*0.05******123456789~
CTT*2~
GE*2*000000001~
IEA*1*000000001~

PROCESS HANDLING - AOM CHANNEL - Direct Ship (Inv per PO) MULTIPLE SKUs

ISA*00* *00* *ZZ*SENDER *ZZ*RECEIVER *240506*2056*U*00401*000000001*0*T*>~
GS*IN*SENDERGS*RECEIVERGS*20240506*205604*000000001*X*004010~
BIG*20170403*00001236**99991235****00~
CUR*BY*CAD~
REF*VR*9999~
N1*RI* ABC COMPANY *1*123456789~
N1*ST* CT RETAIL - DIRECT SHIP *9*2016136689000~
IT1*1*10*EA*4.03**SK*099-9998-6~
PID*F****MOTOMASTER OIL FILTER~
IT1*2*40*EA*7.44**SK*099-9999-9~
PID*F****PERSONA WIDE SLOT TOASTER~
TDS*38093~
TXI*ZZ*43.93*0.13******123456789~
CTT*2~
GE*1*000000001~
IEA*1*000000001~

PROCESS HANDLING - LEGACY or AOM CHANNEL - STORAGE or CROSS DOCK (Inv per PO) MULTIPLE SKUs

ISA*00* *00* *ZZ*SENDER *ZZ*RECEIVER *240506*2047*U*00401*000000001*0*T*>~
GS*IN*SENDERGS*RECEIVERGS*20240506*204749*000000001*X*004010~
BIG*20170403*00001234**99991235****00~
CUR*BY*CAD~
REF*VR*9999~
N1*RI* ABC COMPANY *1*123456789~
N1*ST*A J BILLES*9*2016136689005~
IT1*1*72*EA*9.69**SK*099-9997-3~
PID*F****YARDWORKS PRO-GRADE SHOVEL~
IT1*2*48*EA*4.03**SK*099-9998-6~
PID*F****MOTOMASTER OIL FILTER~
IT1*3*24*EA*7.44**SK*099-9999-9~
PID*F****PERSONA WIDE SLOT TOASTER~
TDS*120874~
TXI*ZZ*139.06*0.13******123456789~
CTT*3~
GE*1*000000001~
IEA*1*000000001~

Sample 1

ISA*00* *00* *ZZ*SENDER *ZZ*RECEIVER *240506*2048*U*00401*000000001*0*T*>~
GS*IN*SENDERGS*RECEIVERGS*20240506*204817*000000001*X*004010~
BIG*20170403*00001234**99990001****00~
CUR*BY*CAD~
REF*VR*9999~
N1*RI*BOB’S BAIT SHOPPE*1*123456789~
N3*1234 ELM DRIVE~
N4*TIMBUKTU*ON*A1A 1A1*CA~
N1*ST*A J BILLES*9*2016136689005~
IT1*1*99*EA*9.99**SK*012-3456-7~
PID*F****DELUXE TACKLE BOX~
TDS*102857~
TXI*ZZ*69.23*0.13******123456789~
CTT*1~
GE*1*000000001~
IEA*1*000000001~

Stedi is a registered trademark of Stedi, Inc. All names, logos, and brands of third parties listed on this page are trademarks of their respective owners (including “X12”, which is a trademark of X12 Incorporated). Stedi, Inc. and its products and services are not endorsed by, sponsored by, or affiliated with these third parties. Use of these names, logos, and brands is for identification purposes only, and does not imply any such endorsement, sponsorship, or affiliation.