VDP Program Vendor Guidelines

Transcription

1 AutoZone Merchandising Systems Vendor Reference VDP Program Vendor Guidelines (EDI X12 version ) Revised by Dept EDI group February 2007 Portions of this document contain hyperlinks that are navigable when using Adobe Acrobat Reader or Adobe Acrobat Exchange to view the document. Audience This document is distributed for use by AutoZone's vendors for the sole purpose of doing business with AutoZone. Document Corrections Please communicate any document corrections or comments to the EDI Technical Contact(s) named in Section 3.0, AutoZone Contacts.

2 Copyright 2007 AutoZone, Inc. 123 South Front Street, Memphis, Tennessee All rights reserved This document contains confidential and proprietary trade secrets of AutoZone, Inc., and may not be removed from AutoZone, Inc. premises without permission. Information in this document is subject to change without notice. No part of this document may be reproduced or transmitted in any form or by any means, electronic or mechanical, or by any information storage or retrieval system, for any purpose, without the express written permission of AutoZone, Inc. Other product and company names herein may be the trademarks of their respective owners.

3 Table Of Contents 1.0 Introduction Summary How It Works Vendor Requirements In-Stock Information Inventory Accuracy EDI Documentation Data Transmission Shipping Tracing Undelivered Parts Shipping Errors Returns Invoices Vendor Holidays Non-Compliance Vendor Agreements AutoZone Contacts EDI Technical Contacts Invoices and Payments Merchandising Business Contact Logistics Contact Required EDI Documents Maps AutoZone Purchase Order AutoZone Inventory Inquiry/Advice AutoZone Advance Shipping Notices AutoZone Invoice VDP Program Agreements Vendor Direct Parts Agreement Carrier Shipping Device Policy Production Information.. 54 Revision History..54

4 1.0 Introduction 1.1 Summary The vendor-direct parts (VDP) program allows AutoZone to offer our customers a wide variety of automotive parts. These parts would otherwise be unavailable because of limited space and size in our stores and warehouses. For our vendors, VDP increases the volume and range of their automotive parts sales. The keys to a successful AutoZone VDP program are: Accurate, on-time advance ship notices (ASNs) Accurate, on-time inventory quantity transmissions Accurate connection between the invoice and the airbill Electronic invoicing Consistent shipping performance. Without these five requirements, the VDP program will not succeed. 1.2 How It Works Central to the VDP program is electronic data interchange (EDI), an electronic computer communications link between the vendor and AutoZone. The graphic and explanation on the next page describe how the VDP program works. 1. Vendor transmits his current warehouse inventory quantities-on- hand (QOH) to AutoZone. 2. AutoZone transmits the vendor inventory information to the stores. 3. Customer orders a VDP part. AutoZoner creates VDP purchase order (PO), which automatically subtracts from current quantity on hand (QOH). 4. Customer PO is transmitted to AutoZone corporate computer. 5. The AutoZone system sorts and creates electronic batches of POs then transmits orders to vendor via EDI. 6. Vendor receives POs electronically, then pulls, packs, and ships parts to AutoZone store via specified carrier at a pre-determined time. AutoZone store number and PO number are identified in reference field on airbill.

5 7. Vendor sends electronic advance ship notices (ASNs) via EDI to AutoZone before 9:00 p.m. Central Time (CST), indicating shipment or cancellation information. (Vendor has the option of sending inventory quantities with ASNs.) 8. ASNs are forwarded on to stores with shipping information or notice of cancellation. 9. Vendor sends electronic invoices via EDI to AutoZone. Invoices are matched with both carrier airbills and store POs for payment approval. Vendor invoice identifies carrier and airbill number. 10. Air carrier sends EDI notice with airbill number and store number. AutoZone Customer 3. Customer orders VDP part AutoZone Store Air Carrier 10. Air carrier sends EDI notice 8. ASN Transmitted to Stores w/ receive or cancel 2. Transmit Vendor Inventory 4. VDP PO transmitted 6. Pull, pack and ship part via approved carrier AutoZone Store Support Center 1. Transmit Inventory QOH 5. POs sorted and transmitted 7. Transmit ASNs before 10:00 p.m. 9. Transmit invoices for payment AutoZone Vendor

6 2.0 Vendor Requirements 2.1 In-Stock Information Specific information about each SKU is needed by the AutoZone product manager prior to the start of the VDP program. Vendors will be given a 3.5-inch computer disk to set-up these items. The required information includes: Part number UPC number Item Weight Item Measurements (length/width/height in inches) Cost of item. A vendor may elect to commit inventory specifically to AutoZone or transmit all open inventory. 2.2 Inventory Accuracy On-hand inventory figures must be accurate and transmitted at any time before 9:00 p.m. Central Time daily for the VDP program to work correctly. Accurate inventory figures will ensure that stores can not order more than is actually available and will thus reduce the number of order cancellations. Vendors must send an inventory transmission for all VDP parts using the six-digit AutoZone SKU number each time they transmit. If the inventory level is zero, there must be a zero inventory transmission for that part. If a vendor decides to discontinue a part, the AutoZone product manager must be notified as soon as the decision is made. On the day the vendor decides is the last day of availability for the discontinued item, the vendor must transmit an inventory of zero.

7 2.3 EDI Documentation A vendor needs three EDI documents in addition to the PO (EDI document 850) to participate in the VDP program. These documents are defined in Section 4 of this document defines how inventory information is to be transmitted defines the required ASN information provides the layout of the vendor's electronic invoice. The EDI PO document (850) for VDP orders is the same one shown in the EDI Trading Partner Guidebook, except for the contents (not the structure) of the "SHIP TO" information. The VDP "SHIP TO" information contains store address information, whereas warehouse information is found on a normal warehouse PO. The area of EDI document 850 that normally contains the AutoZone warehouse code (i.e., 22, 33, 44, etc.) will instead contain a code of "DS", indicating a "direct ship" order. It also includes TD5 segment that contains a code for the FedEx shipping option. 2.4 Data Transmission AutoZone's VDP system can send POs to the vendor's mailbox hourly, from 6:00 a.m. to 10:00 p.m. CST every day. The EDI send times are initiated from AutoZone at the top of each hour. Vendors should start checking their mailboxes at 30 minutes after the hour. Please Note! Since there is no other practical way of assuring that AutoZone has received EDI documents sent by the vendor, the vendor must check functional acknowledgments. This involves matching 997's sent to the vendor, by AutoZone, against the batches of documents which the vendor has sent to AutoZone. If, within 24 hours, the vendor does not receive a 997 acknowledging a batch, the vendor must contact AutoZone s EDI Analyst (for contact information, please see AutoZone s Contact list on p. 12).

8 AutoZone must receive ASNs (EDI document 856) by 8:00 p.m. (CST) the day of shipment. The vendor and product manager will determine the normal purchase order cut-off time, which is usually one hour before the last air carrier pickup (CST). Vendor inventory QOH information (EDI document 846) must be received by AutoZone no later than 8:00 p.m. (CST) daily, except Saturday. This information may also be transmitted with the vendor's ASNs. Vendors must be able to re-transmit invoices or ASNs if AutoZone experiences problems with documents. Re-transmission may be required for up to six months after a purchase order is sent. In the event of a system, EDI or weather transmission interruption that prevents the vendor from shipping purchase order packages on time, the vendor must contact the AutoZone Merchandising Business Contact promptly. The Contact will ask for a list of the POs that will not be shipped. If fewer than 50 POs are on the list, the vendor will be expected to call the stores and provide a corrected ship date to the store manager. 2.5 Shipping An AutoZone Logistics representative will coordinate with the carrier to provide shipping system installation and training. That system may be either web-based or a stand-alone unit provided by a carrier. Either system must have the means to determine package weight, and must be used for the sole purpose of shipping AutoZone VDP program orders only. The appropriate shipping label(s) must be attached to each package according to the carrier specifications. AutoZone will be assigned one or more carrier account numbers for the vendor's location and is responsible for paying the carrier(s) bill. Vendors provided with an automated shipping system must execute an agreement with the carrier and provide a dedicated phone line to operate the system. Vendors must maintain an internet account if they have a web-based system in operation. AutoZone will be responsible for the execution of the approved automated shipping system. AutoZone will not be responsible for damage to the system caused by misuse or mishandling. Any unauthorized shipments made on an AutoZone account will be charged back with an administration fee added. The vendor is responsible for accurate weights and labels for each package. In addition, the vendor will enter the following order information on the Reference line of the shipping screen: Store number (four digits)/po number Example: 2763/

9 AutoZone will initially provide all store numbers and addresses for the vendor's system records on diskette and will update this information via electronic fax, , or internet. AutoZone and the vendor will negotiate the latest daily pick-up time by the carrier from the vendor. Shipping Option Codes sent in Purchase orders: F01- priority overnight with Saturday delivery (air), F06 Standard Overnight (air); F11-Economy 2-day (air); R02-Ground. 2.6 Tracing Undelivered Parts AutoZone will be responsible for initially tracing a missing order. AutoZone stores will lookup the PO number for the unreceived part on their computer to obtain the carrier name and tracking number. Stores with Internet access will log onto the carrier web site to determine the estimated time of arrival (ETA). Stores without Internet access can call the carrier to obtain the ETA. The information the stores will use comes from the shipping quantity and the carrier's airbill number, found on the vendor's ASN. If a shipping error is found, e.g., the part was shipped to the wrong store, the receiving store will report it to the AutoZone store operations support line. The receiving store will then return the part to the vendor following their normal return policy, unless otherwise specified. 2.7 Shipping Errors Vendors who ship parts to the wrong store will be responsible for any costs incurred to correct the shipping error. AutoZone will not pay an invoice for parts when delivery is made to the wrong store. AutoZone will only pay one invoice for the correct shipment to the correct store. 2.8 Returns AutoZone stores will follow their normal return procedures. Defective, damaged, and undamaged returns will be properly tagged and returned to the store's warehouse. The warehouse will return the part to the vendor according to specific guidelines as described in the vendor agreement. Arrangements may need to be made by the vendor and AutoZone product manager to handle a possible increase in returns, i.e., AutoZone currently may be returning parts to a local warehouse that is not set up to handle additional returned parts.

10 2.9 Invoices AutoZone will process vendor invoices promptly when it can match the carrier's airbill number to the AutoZone purchase order number to the store that ordered the part. Invoices can only be paid when these three pieces of information can be matched in the AutoZone PO system. To track multiple unpaid invoices, vendors should send a diskette to one of the contacts listed in Section 3.2, Invoices and Payments. The information on the diskette must be in the following format: Invoice up to 22 characters, left justified PO Numeric (8 digits) Airbill Numeric (12 digits) Invoice Date Characters yyyy-mm-dd Store # Numeric (4 digits) Amount Comments Field Numeric (16 digits)-store #/PO# Additional information or fields may be added at the end of the Comments field Vendor Holidays All VDP program vendors must notify AutoZone in writing of any holidays or factory closings a minimum of 30 days in advance of the closing date. AutoZone will inform all stores about any changes in vendor shipment dates and times.

11 2.11 Non-Compliance VDP is an AutoZone proprietary program. Appropriate actions per the VDP program agreement found in Section 5, including removal of the vendor from the VDP program, may be taken if any of the following situations occur: 1. The participating vendor or his employees share this program or program information with any other vendor or company. Such a breach would violate the existing confidentiality agreement between AutoZone and the vendor. 2. The vendor does not provide and maintain a dedicated phone line when an automated shipping system is used, or violates the carrier agreement. 3. The vendor continually ships to the wrong store. 4. The vendor is unable to provide timely and accurate EDI transmissions. 5. The vendor does not send accurate ASNs consistently or on a timely basis Vendor Agreements All existing vendor agreements remain in force and cannot be superceded by these guidelines. The required VDP program agreement, which includes a section regarding confidentiality, is provided in this document. All vendors participating in AutoZone's VDP program will be required to complete and return an original of this agreement prior to program start. Vendors must have a signed confidentiality agreement on file with AutoZone. Signed agreements should be sent to: Wanda Webb -- Merchandising Department 9009 AutoZone Parts, Inc. PO Box S. Front Street Memphis, TN 38101

12 3.0 AutoZone Contacts 3.1 EDI Technical Contacts For transaction-set mapping and parallel test questions: Patricia Hileman, IT Sr. Program Analyst (901) Mary Walker, IT EDI Analyst (901) AutoZone Central Fax (901) Invoices and Payments Cathy Meyer, Director of Payables (901) Merchandising Business Contact Blayn Chipman, VDP Manager (901) Eric Acerson, VDP Program Administrator (901) Logistics Contact Ruth Ralph, Global Transportation Analyst (901) Rebecca Miller, Transportation Coordinator (901)

13 4.0 Required EDI Documents -- Maps This section describes AutoZone's file formats for these EDI documents: 850 Purchase Order 846 Inventory Inquiry/Advice 856 Advance Shipping Notices 810 Invoice

14 EDI Document AutoZone Purchase Order (pg. 1 of 7) Data Data Name ISA -- Interchange Control Header Segment ISA01 I01 Authorization Information '00' = No meaningful data in ISA02. Qualifier ISA02 I02 Authorization Information May contain any 10 characters including 10 spaces or 10 zeros. ISA03 I03 Security Information Qualifer 00' = No meaningful data in ISA04. ISA04 I04 Security Information May contain any 10 characters including 10 spaces or 10 zeros. ISA05 I05 Interchange ID Qualifier (Sender) May contain any valid ANSI code for this element. ISA06 I06 Interchange Sender ID AutoZone's ID depending on the code in ISA05. ISA07 I05 Interchange ID Qualifier (Receiver) May contain any valid ANSI code for this element. ISA08 I07 Interchange Receiver ID Your ID depending on the code in ISA07. ISA09 I08 Interchange Date The date the envelope was created in YYMMDD format. ISA10 I09 Interchange Time The time the envelope was created in HHMM format. ISA11 I10 Interchange Control 'U' = U.S. EDI community. Standards ID ISA12 I11 Interchange Control Version '00400' ISA13 I12 Interchange Control The number AutoZone has assigned to the transaction which uniquely identifies this transmission. ISA14 I13 Acknowledgement Requested 0' = No Acknowledgement Requested '1' = Acknowledgement Requested (Not the 997 transaction set). ISA15 I14 Test Indicator T' = Test Data 'P' = Production Data. ISA16 I15 Sub- '>' Greater Than Relational Operator.

15 EDI Document AutoZone Purchase Order (pg. 2 of 7) Data Data Name GS -- Functional Group Header GS Functional ID Code 'PO' = Purchase Order. GS Application Sender Code AutoZone's ID (Our DUNS number). GS Application Receiver code Your ID (Usually your DUNS number). GS Group Date Date a functional group of transaction sets was generated in CCYYMMDD format. GS Group Time Time a functional group of transaction sets was generated in HHMM format. GS06 28 Group Control AutoZone assigned to this functional group; this same number will be in GE02 and in the 997 functional acknowledgement for this functional group. GS Responsible Agency Code 'X' = ANSI X12. GS Version/Release Industry ID Code ST -- Transaction Set Header ' to represent the ANSI X12 version we are sending. ST Transaction Set ID Code '850' = Purchase Order. ST Transaction Set Control A unique number AutoZone assigns to this transaction set; also appears in SE02.

16 EDI Document AutoZone Purchase Order (pg. 3 of 7) Data Data Name BEG -- Beginning Segment of Purchase Orders BEG Transaction Set Purpose '00' = Original Purchase Order. Code BEG02 92 Purchase Order Type 'NE' = New order. Code BEG Purchase Order A unique number for this order. BEG Purchase Order Release 00' = Original release of a purchase order Greater than '00' = Backorder. BEG Purchase Order Date The date the purchase order was created in CCYYMMDD format. DTM -- Date/Time Information DTM Date/Time Qualifier 074' = Requested for delivery (prior to and including) the date in DTM02. '068' = Current scheduled ship date. This code will represent the date merchandise should be ready to ship. DTM Date If DTM01 is '074': This date represents the requested delivery date (on or before) that AutoZone expects the merchandise to be at the AutoZone distribution center. If DTM01 is '068': This date indicates the shipment date AutoZone expects the merchandise to be ready to be shipped. DTM Note: The DTM with the 074 qualifier will be sent to all vendors. The DTM with the 068 Qualifier can ONLY be sent to vendors participating in the AutoZone logistics or Direct Import programs. It will be sent unless requested by the participating vendor. N9-- Reference Identification N Reference ID Qualifier ZZ' = Mutually defined field between AutoZone and trading partner. N Reference ID 'AutoZone PO' MSG -- Message Text MSG Freeform message text Purchase order note as entered by the AutoZone buyer. N9/MSG Note: The N9 and MSG segments are optional and will only occur when an actual message is present.

17 EDI Document AutoZone Purchase Order (pg. 4 of 7) Data Data Name N1 -- Name Information N Entity Code ST' = Ship to' BT' = Bill to' VN' = Vendor (See N1 note). N Name Either ship to or bill to name depending on code in N101 (Not used if N101 = 'VN'). N ID Code Qualifier 93' = Code assigned by AutoZone (only if N101 is 'VN'). 'ZZ' = Mutually defined (Only if N101 is 'ST'). N ID Code If N103 = '93', this is the AutoZone internal vendor number (this value will be returned on the 856 advance ship notice). If N103 = 'ZZ', this is the AutoZone warehouse location code or the VDP indicator. A warehouse code is two digits such as 11, 22, 33, etc. The VDP indicator is the two character string 'DS'. N1 Note: N3 -- Address Information AutoZone will send three occurrences of the N1 loop in a Purchase Order. The N1 loop qualified by an `ST' in N101 will contain the N3 and N4 segments in addition to the N1. The N1 loop qualified by `BT' in N101 will also contain N3 and N4 segments. The N1 loop qualified by `VN' in N101 will only contain the N1 segment. N Address Ship to or bill to address depending on code in N101. N3 Note: The Ship To and the Bill To loops will contain the appropriate address in N301. The Vendor will not contain an N3 segment.

18 EDI Document N1 Loop Examples Ship to address loop N1 *ST* AUTOZONE STORE# *ZZ* DS N3 *1700 DUNN AVE. N4 *MEMPHIS*TN*38106 Bill to address loop N1 *BT* AUTOZONE, INC. N3 *PO BOX 2198 N4 *MEMPHIS*TN* Vendor number loop N1 *VN**93*12345

19 EDI Document AutoZone Purchase Order (pg. 5 of 7) Data Data Name N4 -- Geographic Information N City Name Ship to or bill to city depending on code in N101. N State Code Ship to or bill to state depending on code in N101. N Postal (Zip) Code Ship to or bill to zip code depending on code in N101. N1 Note: REF -- Reference s The Ship To and the Bill To loops will contain the appropriate city, state, and zip in the N4 segment. The Vendor loop will not contain an N4 segment. REF Reference A code of 'ST' designating store number. Qualifier REF Reference The 4-digit AutoZone store number. Note: This segment will only be sent to vendors participating in the AutoZone DSD or VDP program.

20 EDI Document AutoZone Purchase Order (pg. 6 of 7) Data Data Name PO1 -- Purchase Order Item Information PO Assigned Identification (Occurrence ) A unique number for each occurrence of a PO segment. For example, the first PO segment would contain a '1', the second would contain a '2', etc. PO Quantity Ordered The number ordered of this item. PO Unit of Measure Code Any X12 standard unit of measure value. PO Product/Service ID 'VP' = Vendor part number. Qualifier PO Product/Service ID Your part number. PO Product/Service ID 'SK' = SKU number. Qualifier PO Product/Service ID AutoZone's item number. PID-- Product/Item Description PID Item Description Type 'F' = Freeform item description. PID Item Description AutoZone's item description. PO4 -- Item Physical Details PO Pack of inner pack units per outer pack unit. TD5 Carrier Details (Routing Sequence/Transit Time) TD Identification Code This will always be FEDX. TD Routing Shipping codes are F06, F11, R02, F01. TD512 SD Saturday delivery if applicable. Note: This information will only be sent to vendors participating in the AutoZone VDP program.

21 EDI Document AutoZone Purchase Order (pg. 7 of 7) Data Data Name CTT -- Transaction Totals CTT of Line Items The total of PO1 segments in this purchase order. CTT Hash Total Total quantity ordered in this purchase order. CTT03 81 Weight Total weight ordered in this purchase order. CTT Unit of Measurement Code '01' = Actual pounds. SE -- Transaction Set Trailer SE01 96 of Included Segments SE Transaction Set Control Total number of X12 segments in this transaction set (including the ST and SE segments). The same number that is in the ST02 element. GE-- Functional Group Trailer GE01 97 of Included Sets Total number of ST segments in this functional group. GE02 28 Group Control The same number that is in the GS06 element. IEA -- Interchange Control Trailer Segment IEA01 I16 of Included Groups IEA02 I12 Interchange Control A count of the number of functional groups included in this transmission (the number of GS segments). The same number that is in the ISA13 element.

22 Purchase Order -- VDP Order Example BEG*00*NE* *00* DTM*074* N1*BT*AUTOZONE, INC. N3*PO BOX 2198 N4*MEMPHIS*TN* N1*VN**93*00026 N1*ST*AUTOZONE #1343*ZZ*DS N3*2502 STATELINE N4*TEXARKANA*AR*75502 REF*ST*1343 PO1*1*1*EA***VP* *SK* PID*F****ITEM 1 DESCRIPTION PO4*1 CTT*1*1*17*01

23 EDI Document AutoZone Inventory Inquiry/Advice (pg. 1 of 4) Data Data Name ISA -- Interchange Control Header Segment ISA01 I01 Authorization Information '00' = No meaningful data in ISA02. Qualifier ISA02 I02 Authorization Information May contain any 10 characters including 10 spaces or 10 zeros. ISA03 I03 Security Information '00' = No meaningful data in ISA04. Qualifier ISA04 I04 Security Information May contain any 10 characters including 10 spaces or 10 zeros. ISA05 I05 Interchange ID Qualifier May contain any valid ANSI code for this element. (Sender) ISA06 I06 Interchange Sender ID Your ID depending on the code in ISA05. ISA07 I05 Interchange ID Qualifier May contain any valid ANSI code for this element. (Receiver) ISA08 I07 Interchange Receiver ID AutoZone's ID depending on the code in ISA07. ISA09 I08 Interchange Date The date the envelope was created in YYMMDD format. ISA10 I09 Interchange Time The time the envelope was created in HHMM format. ISA11 I10 Interchange Control Standards ID ISA12 I11 Interchange Control Version ISA13 I12 Interchange Control ISA14 I13 Acknowledgement Requested 'U' = U.S. EDI community. '00400' The number AutoZone has assigned to the transaction which uniquely identifies this transmission. 0' = No Acknowledgement Requested '1' = Acknowledgement Requested (Not the 997 transaction set). ISA15 I14 Test Indicator T' = Test Data. 'P' = Production Data. ISA16 I15 Sub- '>' Greater Than Relational Operator.

24 EDI Document AutoZone Inventory Inquiry/Advice (pg. 2 of 4) Data Data Name GS -- Functional Group Header GS Functional ID Code 'IB' = Inventory Inquiry. GS Application Sender Code The sender's identification (same as found in ISA06). GS Application Receiver code AutoZone's DUNS number (same as found in ISA08). GS Group Date Date a functional group of transaction sets was generated in CCYYMMDD format. GS Group Time Time a functional group of transaction sets was generated in HHMM format. GS06 28 Group Control AutoZone assigned to this functional group; this same number will be in GE02 and in the 997 functional acknowledgement for this functional group. GS Responsible Agency Code 'X' = ANSI X12. GS Version/Release Industry ID Code ST -- Transaction Set Header ' to represent the ANSI X12 version we are sending. ST Transaction Set ID Code '846' = Inventory Inquiry/Advice. ST Transaction Set Control A unique number AutoZone assigns to this transaction set; also appears in SE02.

25 EDI Document AutoZone Inventory Inquiry/Advice (pg. 3 of 4) Data Data Name BIA -- Beginning Segment for Inventory Inquiry/Advice BIA Purpose Code Send a value of '08', meaning this document contains inventory information. BIA Report Type Code Send a value of 'DD', meaning this document is a distributor inventory report. BIA Reference This number is the transaction set reference number as assigned by the sender. This number can be used to reference a particular document between the send and AutoZone. BIA Date Date a functional group of transaction sets was generated in CCYYMMDD format. LIN -- Item Identification LIN Product Identity Qualifier Send a value of 'IN', meaning the product identifier in the next element contains the buyer's item number. LIN Product Identifier AutoZone's item number for this product. NOTE: This number must be a six-digit numeric. Leading zeros are required. QTY -- Quantity QTY Quantity Qualifier 33' = The quantity in QTY02 is the quantity available for sale. '37' = The quantity in QTY02 is the quantity available for remanufacture. QTY Quantity If QTY01 = '33', this is the actual quantity of a particular item available for sale. If QTY01 = '37', this is the actual quantity of a particular item available for remanufacture. This value must be specified relative to the unit of measure as required by AutoZone. QTY Unit of Measure Unit of measure for the quantity found in QTY02. The unit of measure included must be the code specified by AutoZone. QTY Note: AutoZone will determine which code will be used for a QTY loop.

26 EDI Document AutoZone Inventory Inquiry/Advice (pg. 4 of 4) Data Data Name CTT -- Transaction Totals CTT of Line Items The total of LIN segments in this purchase order. CTT Hash Total Total quantity available (sum of all QTY02 elements). SE -- Transaction Set Trailer SE01 96 of Included Segments SE Transaction Set Control GE-- Functional Group Trailer Total number of X12 segments in this transaction set (including the ST and SE segments). The same number that is in the ST02 element. GE01 97 of Included Sets Total number of ST segments in this functional group. GE02 28 Group Control The same number that is in the GS06 element. IEA -- Interchange Control Trailer Segment IEA01 I16 of Included Groups IEA02 I12 Interchange Control A count of the number of functional groups included in this transmission (the number of GS segments). The same number that is in the ISA13 element.

27 EDI Document AutoZone Advance Shipping Notices (pg. 1 of 10) Data Data Name ISA -- Interchange Control Header Segment ISA01 I01 Authorization Information Qualifier AutoZone will use code '00', meaning no authorization information present. ISA02 I02 Authorization Information Will contain 10 spaces if ISA01 contains code of 00. ISA03 I03 Security Information Qualifier AutoZone will use code '00' -- no security information present. ISA04 I04 Security Information Will contain 10 spaces if ISA03 contains code of 00. ISA05 I05 Interchange Sender ID May contain any valid ANSI code for this element. Qualifier ISA06 I06 Interchange Sender Contains the identification of the sender. Identification ISA07 I05 Interchange Receiver ID May contain any valid ANSI code for this element. Qualifier ISA08 I07 Interchange Receiver ID AutoZone's ID depending on the code in ISA07. ISA09 I08 Interchange Date Date the envelope was created, in YYMMDD format. ISA10 I09 Interchange Time Time the envelope was created, in HHMM format. ISA11 I10 Interchange Standards ID Code of 'U', meaning US EDI community. ISA12 I11 Interchange Control Version Contains '00400' ISA13 I12 Interchange Control A number assigned by the sender to uniquely identify the transmission. ISA14 I13 Acknowledgement Request Code of '0', meaning no envelope acknowledgement requested. ISA15 I14 Test Indicator Code of 'T' for Test data. Code of 'P' for Production data. ISA16 I15 Sub-element Separator Character used to separate sub-elements. AutoZone will use a '>' sign.

28 EDI Document AutoZone Advance Shipping Notices (pg. 2 of 10) Data Data Name GS -- Functional Group Header GS Functional ID Code Code of 'SH' to indicate ship notice. GS Application Sender's Code The sender's identification (same as found in ISA06). GS Application Receiver's Code AutoZone's DUNS number (same as found in ISA08). GS Group Date Date the functional group was created, in CCYYMMDD format. GS Group Time Time the functional group was created, in HHMM format. GS06 28 Group Control Assigned number created by the sender. This same number must be used in GE02. GS Responsible Agency Code Code of 'X' to indicate ASC X12. GS Version/Release/Industry ID Code ' to represent the ANSI X12 version you are sending.

29 EDI Document AutoZone Advance Shipping Notices (pg. 3 of 10) Data Data Name ST -- Transaction Set Header ST Transaction Set ID Code Code uniquely identifying a transaction set. '856' for shipping notices. ST Transaction Set Control assigned by the sender to uniquely identify the transaction set. BSN -- Beginning Segment for Ship Notice BSN Transaction Set Purpose Code of '00' to indicate original document. Code BSN Shipment Identifier A number or code to identify the ASN document to the sender. May use bill of lading number or pro bill if no other shipment ID exists. BSN Date Create date of the ASN, in CCYYMMDD format. BSN Time Create time of the ASN in HHMM format. DTM -- Date/Time Reference (two DTM segments are needed) DTM Date/Time Qualifier Code of '011', meaning the date the shipment was initiated and a code of '017, meaning the expected arrival date at AutoZone. DTM Date If DTM01 is '011' -- actual ship date; If DTM01 is '017' -- expected arrival date; in CCYYMMDD format. DTM Time If DTM01 is '011' -- actual ship time. If DTM01 is '017' -- element is not used. DTM Note: There are two DTM segments required for this mapping. The first occurrence should contain a code of '011 in element 374. The second occurrence should contain a code of `017'. The segment with the `017' qualifier does not need to contain a time in element 337. The time will be ignored if sent on the `017' DTM.

30 EDI Document AutoZone Advance Shipping Notices (pg. 4 of 10) Data Data Name HL -- Hierarchical Level Segment (Shipment Level) HL Hierarchical ID A unique number for each occurrence of an HL segment. For example, the first HL segment would contain a '1', the second would contain a '2', etc. HL Hierarchical Level Code A code of "S' to indicate that shipment information is contained within this particular HL segment loop. HL Hierarchical Child Code A code of '1', indicating that there are more HL levels subordinate to this one. H Notes: 1. This is the first of four levels of HL segments in the AutoZone Advance Shipping Notice. The first level contains the shipment level information. The second level contains shipping tare information and is subordinate to the first HL segment. The third level contains order information and is subordinate to the second level. The fourth level is the item level and is subordinate to the third level. 2. There will only be one occurrence of the HL level for shipments in a shipping notice. There may be more than one occurrence of the tare level and order level HLs in a shipment notice, and there will usually be multiple occurrences of the item level HL segment. MEA -- Measurements MEA Measurement Reference ID Use a code of 'PD', meaning physical dimensions. Code MEA Measurement Value The value contained in this element represents the measurement of the shipment, whether it is in weight, cases, pallets, cubic feet, etc. MEA Unit of Measure Code The unit of measure code for the value found in MEA03. TD5 -- Carrier Details (Routing Sequence/Transit Time) TD Transportation Method Type A code representing how the shipment will be Code transported -- i.e., 'M' = Motor (common carrier). TD Routing The originating carrier's identity.

31 EDI Document AutoZone Advance Shipping Notices (pg. 5 of 10) Data Data Name TD3 -- Carrier Details (Equipment) TD Equipment Description Code A code representing the type of equipment used for the shipment -- i.e., 'TL' = Trailer TD Equipment Identification number of the shipping equipment -- i.e., the trailer number. REF -- Reference s (two occurrences needed) REF Reference Qualifier BM' code (bill of lading) is the first occurrence. 'CN' code is the second occurrence. REF Reference If REF01 is 'BM' = bill of lading number. If REF01 is 'CN' = pro bill number. REF note: N1 -- Name This segment can be ignored if the REF segment following the PRF segment will be sent. N Entity ID Code Code of 'VN', meaning vendor information. N ID Code Qualifier Code of '92', meaning N104 information was assigned by AutoZone. N ID Code AutoZone's internal vendor number for supplier. This number is contained in the N1 segment in the purchase order.

32 EDI Document AutoZone Advance Shipping Notices (pg. 6 of 10) Data Data Name HL -- Hierarchical Level Segment (Tare Level) HL Hierarchical ID (Occurrence ) A unique number for each occurrence of an HL segment. For example, the first HL segment would contain a '1', the second would contain a '2', etc. HL Hierarchical Parent ID Identifies the HL level (by ID number) to which this HL level is subordinate. HL Hierarchical Level Code A code of 'T' to indicate that tare information is contained within this particular HL segment loop. IF APPLICABLE. HL Hierarchical Child Code A code of '1', indicating that there are more HL levels subordinate to this one. Hl Notes: 1. This is the second of four levels of HL segments in the AutoZone Advance Shipping Notice. The first level contains the shipment level information. The second level contains shipping tare information and is subordinate to the first HL segment. The third level contains order information and is subordinate to the second level. The fourth level is the item level and is subordinate to the third level. 2. There will only be one occurrence of the HL level for shipments in a shipment notice. There may be more than one occurrence of the tare level and order level HLs in a shipment notice, and there will usually be multiple occurrences of the item level HL segment. MAN -- Marks and s Segment MAN01 88 Marks and s Qualifier Code specifying the application or source of marks and numbers. AutoZone will use a code of 'UC' to indicate a UCC-128 barcode. MAN02 87 Marks and s Marks and numbers used to identify a shipment or parts of a shipment. AutoZone will expect a UCC- 128 serialized shipping container code.

33 EDI Document AutoZone Advance Shipping Notices (pg. 7 of 10) Data Data Name HL -- Hierarchical Level Segment (Order Level) HL Hierarchical ID (Occurrence ) A unique number for each occurrence of an HL segment. For example, the first HL segment would contain a '1', the second would contain a '2', etc. HL Hierarchical Parent ID Identifies the HL level (by ID number) to which this HL level is subordinate. HL Hierarchical Level Code A code of 'O' to indicate that order information is contained within this particular HL segment loop. HL Hierarchical Child Code A code of '1', indicating that there are more HL levels subordinate to this one. Hl Notes: 1. This is the third of four levels of HL segments in the AutoZone Advance Shipping Notice. The first level contains the shipment level information. The second level contains shipping tare information and is subordinate to the first HL segment. The third level contains order information and is subordinate to the second level. The fourth level is the item level and is subordinate to the third level. 2. There will only be one occurrence of the HL level for shipments in a shipment notice. There may be more than one occurrence of the tare level and order level HLs in a shipment notice, and there will usually be multiple occurrences of the item level HL segment. PRF -- Purchase Order Segment PRF PO AutoZone's purchase order number for the merchandise being shipped. PRF PO Release Release number for the purchase order. REF -- Reference s REF Reference Qualifier 'CN' = Carrier's Reference. REF Reference Shipper ID number (tracking number) or 'NO SHIP' to indicate the order will not be shipped. REF notes This segment is required only for trading partners participating in AutoZone s Vendor Direct Parts program, otherwise, it should be ignored. If this segment is sent, the REF segment following the TD3 segment can be ignored.

34 EDI Document AutoZone Advance Shipping Notices (pg. 8 of 10) Data Data Name HL -- Hierarchical Level Segment (Item Level) HL Hierarchical ID (Occurrence ) A unique number for each occurrence of an HL segment. For example, the first HL segment would contain a '1', the second would contain a '2', etc. HL Hierarchical Parent ID Identifies the HL level (by ID number) to which this HL level is subordinate. HL Hierarchical Level Code A code of 'I' to indicate that item information is contained within this particular HL segment loop. HL Hierarchical Child Code A code of '0', indicating that there are no HL levels subordinate to this one. HL Notes: 1. This is the fourth of four levels of HL segments in the AutoZone Advance Shipping Notice. The first level contains the shipment level information. The second level contains shipping tare information and is subordinate to the first HL segment. The third level contains order information and is subordinate to the second level. The fourth level is the item level and is subordinate to the third level. 2. There will only be one occurrence of the HL level for shipments in a shipment notice. There may be more than one occurrence of the tare level and order level HLs in a shipment notice, and there will usually be multiple occurrences of the item level HL segment.

35 EDI Document AutoZone Advance Shipping Notices (pg. 9 of 10) Data Data Name LIN -- Item Identification LIN Assigned Identification (Occurrence number) A unique number for each occurrence of a LIN segment. For example, the first LIN segment would contain a '1', the second would contain a '2', etc. LIN Product ID Qualifier Code of 'SK', meaning LIN03 contains a stock keeping unit number (SKU). LIN Product ID AutoZone's internal item number as sent on the purchase order. LIN Product ID Qualifier Code of 'VP', meaning LIN05 contains a vendor part number. LIN Product ID Your organization's part number for this item. LIN Product ID Qualifier The code of 'UP' meaning UPC code or 'UK' meaning EAN (international product) code. LIN Product ID If LIN06 = 'UP', the UPC code for this item. If LIN06 = 'UK', the EAN code for this item. SN1 -- Item Detail (Shipment) SN Assigned Identification (Occurrence ) A unique number for each occurrence of an SN1 segment. For example, the first SN1 segment would contain a '1', the second a '2', etc. SN of Units Shipped The number of units shipped for the item identified in the LIN segment. SN Unit of Measure Code The unit of measure code for the value found in SN102. This code should match the unit of measure for the item on the purchase order.

36 EDI Document AutoZone Advance Shipping Notices (pg. 10 of 10) Data Data Name CTT -- Transaction Totals CTT of HL Segments The total number of occurrences of HL segments in this ASN. CTT HASH Total The total number of units shipped on the ASN as found in the SN102 element. SE -- Transaction Set Trailer SE01 96 of Included Segments SE Transaction Set Control GE -- Functional Group Trailer The total number of segments in the transaction set (including SE and ST). The same control number as found in the ST02 element. GE01 97 of Included Transaction Sets The total number of transaction sets found in the functional group. GE02 28 Group Control The same control number as found in the GS06 element. IEA -- Interchange Trailer IEA01 I16 of Included Functional Groups The total number of functional groups found in the interchange envelope. IEA02 I12 Interchange Control The same control number as found in the ISA13 element.

37 Sample VDP 856 (Advance Shipping Notices) Two items from two separate Purchase Orders ST*856*3401 BSN*00*66079* *1641 DTM*011* *1630 DTM*017* HL*1**S*1 MEA*PD**1*EA TD5****A*FEDERAL EXPRESS N1*VN**92*12345 HL*2*1*O*1 PRF* *00 REF*CN* HL*3*2*I*0 LIN*1*SK*078397*VP* SN1*1*1*EA CTT*3*1 SE*16*3401 ST*856*3402 BSN*00*66083* *1642 DTM*011* *1630 DTM*017* HL*1**S*1 MEA*PD**1*EA TD5****A*FEDERAL EXPRESS N1*VN**92*12345 HL*2*1*O*1 PRF* *00 REF*CN* HL*3*2*I*0 LIN*1*SK*322933*VP* SN1*1*1*EA CTT*3*1 SE*16*3402 Zero ASN -- Sent when item is not available ST*856*3403 BSN*00*61023* *1642 DTM*011* *1630 DTM*017* HL*1**S*1 MEA*PD**0*EA TD5****A*N/A N1*VN**92*12345 HL*2*1*O*1 PRF* *00 REF*CN*NO SHIP HL*3*2*I*0 LIN*1*SK*312933*VP* SN1*1*0*EA CTT*3*0 SE*16*3403

38 EDI Document AutoZone Invoice (pg. 1 of 8) Data Data Name ISA -- Interchange Control Header Segment ISA01 I01 Authorization Information Qualifier AutoZone will use code '00', meaning no authorization information present. ISA02 I02 Authorization Information Will contain 10 spaces if ISA01 contains code of 00. ISA03 I03 Security Information Qualifier AutoZone will use code '00' -- no security information present. ISA04 I04 Security Information Will contain 10 spaces if ISA03 contains code of 00. ISA05 I05 Interchange Sender ID Qualifier ISA06 I06 Interchange Sender Identification ISA07 I05 Interchange Receiver ID Qualifier May contain any valid ANSI code for this element. Contains the identification of the sender. May contain any valid ANSI code for this element. ISA08 I07 Interchange Receiver ID AutoZone's ID depending on the code in ISA07. ISA09 I08 Interchange Date Date the envelope was created, in YYMMDD format. ISA10 I09 Interchange Time Time the envelope was created, in HHMM format. ISA11 I10 Interchange Standards ID Code of 'U', meaning US EDI community. ISA12 I11 Interchange Control Version Contains '00400'. ISA13 I12 Interchange Control A number assigned by the sender to uniquely identify the transmission. ISA14 I13 Acknowledgement Request Code of '0', meaning no envelope acknowledgement requested. ISA15 I14 Test Indicator Code of 'T' for Test data Code of 'P' for Production data. ISA16 I15 Sub-element Separator Character used to separate sub-elements. AutoZone will use a '>' sign.

39 EDI Document AutoZone Invoice (pg. 2 of 8) Data Data Name GS -- Functional Group Header GS Functional ID Code Code of 'IN' to indicate invoice. GS Application Sender's Code The sender's identification (same as found in ISA06). GS Application Receiver's Code AutoZone DUNS number (same as found in ISA08). GS Group Date Date the functional group was created in CCYYMMDD format. GS Group Time Time the functional group was created in HHMM format. GS06 28 Group Control Assigned number created by the sender. This same number must be used in GE02. GS Responsible Agency Code Code of 'X' to indicate ASC X12. GS Version/Release/Industry ID Code ST -- Transaction Set Header Code to indicate the standard version used to create the data, i.e. '004010'. ST Transaction Set ID Code Code uniquely identifying a transaction set. '810' for invoices. ST Transaction Set Control assigned by the sender to uniquely identify the transaction set.

40 EDI Document AutoZone Invoice (pg. 3 of 8) Data Data Name BIG -- Beginning Segment for Invoice BIG Invoice Date Date invoice is created in CCYYMMDD format. BIG02 76 Invoice Your invoice number. BIG Purchase Order The AutoZone purchase order referenced by this invoice. REF -- Reference s REF Reference Qualifier Code of 'ST' indicating store number. REF Reference The AutoZone store number to which the P.O. is delivered. Note: Must be four-digit numeric. Leading zeros are required. REF note This segment is required only if you received a store number on the purchase order. The store number will be in the SHIP TO N1 loop in the REF segment on the purchase order. N1 -- Name (one occurrence of the N1 loop to show remittance address information) (one occurrence of the N1 loop to show remittance address information) N Entity ID Code Code of 'RE' or 'RI' indicating remittance information. N Name Name of company to receive remittance. N3 -- Address N Address Address of company to receive remittance. N Address Additional address information if necessary.

41 EDI Document AutoZone Invoice (pg. 4 of 8) Data Data Name N4 -- Geographic Location N City Name City of company to receive remittance. N State State of company to receive remittance. N Postal Code Zip code of company to receive remittance. ITD -- Terms of Sale/Deferred Terms of Sale ITD Terms Type Code The code identifying the type of terms. ITD Terms Discount Percent The terms discount percentage, expressed as a percent, which is available to AutoZone if an invoice is paid on or before the terms discount due date. ITD Terms Discount Due Date Date payment is due if the discount is to be earned in CCYYMMDD format. ITD Terms Discount Days Due The number of days in the terms discount period by which payment is due if terms discount is earned. ITD Terms Net Due Date The date when the total invoice amount becomes due in CCYYMMDD format. ITD Terms Net Days The number of days until total invoice amount is due (discount not applicable). DTM -- Date/Time Information DTM Date/Time Qualifier Code of '011' meaning date shipped. DTM Date The date the merchandise was shipped to AutoZone in CCYYMMDD format.

42 EDI Document AutoZone Invoice (pg. 5 of 8) Data Data Name FOB -- F.O.B. Related Instructions FOB Shipment Method of Payment The code identifying payment terms for transportation charges -- i.e., 'CC' for collect. IT1 -- Baseline Item Data (occurs once for every line item on the invoice) (occurs once for every line item on the invoice) IT Quantity Invoiced The number of units invoiced. IT Unit of Measurement Code The code identifying the basic unit of measurement for the item -- i.e., 'EA' for eaches. IT Unit Price The price per unit of product. Decimal point required. IT Product/Service ID Qualifier The code of 'IN' meaning AutoZone's item number. IT Product/Service ID AutoZone's item number. IT Product/Service ID Qualifier The code of 'VP' meaning vendor part number. IT Product/Service ID The vendor's part number for this item. IT Product/Service ID Qualifier The code of 'UP' meaning UPC code or 'UK' meaning EAN (international product) code. IT Product/Service ID If IT110 = 'UP', the UPC code for this item. If IT110 = 'UK', the EAN code for this item.