Guide · AutoZone EDI
An AutoZone purchase order moves through a standard EDI sequence, acknowledgment, shipment notice, and invoice, the same core documents used across most big-box retail EDI. What changes order to order is which AutoZone program it belongs to: DSD, VDP, or STH, each of which threads through this same lifecycle a little differently. This page follows one AutoZone order through the full document sequence and notes where each program diverges from the standard path.
Step 1
The purchase order carries the line items, quantities, and, depending on the program, a destination that is a distribution center, an individual store (DSD or VDP, identified by the store-number reference), or a consumer address (STH). Reading the PO correctly at this stage, recognizing which program it belongs to, is what determines everything that follows: the DSD vs VDP vs STH guide covers how to tell them apart.
Step 2
The 855 Purchase Order Acknowledgment confirms to AutoZone that the vendor received the PO and states whether it is accepted, rejected, or accepted with changes. Timely, accurate acknowledgment is standard practice across big-box EDI trading partners generally, and AutoZone is no exception; an unacknowledged or slow-acknowledged PO is the first place a vendor relationship starts to look unreliable.
Step 3
Once the order ships, the 856 Advance Ship Notice tells AutoZone what is coming: carton or pallet detail, quantities per line, carrier, and tracking, sent before or at the point of shipment so AutoZone's receiving systems know to expect it. The 856 is widely regarded as the most compliance-sensitive document in retail EDI generally, since a mismatch between what the ASN says and what physically arrives is what most often triggers a chargeback, a pattern that holds across AutoZone and other EDI trading partners alike.
This is also where the three AutoZone programs diverge operationally: a DSD shipment's ASN and eventual invoice both carry the store-number reference from the original PO; a VDP shipment is going to a store the same way, but only exists because the vendor's own 846 inventory feed told AutoZone the part was available; an STH shipment's ASN reflects a residential delivery address rather than a store.
Step 4
The 810 invoice bills AutoZone for the shipped goods, referencing the original PO, and, for DSD specifically, must carry the same store number used on the PO so AutoZone can reconcile the shipment and the bill against the same store. The 997 Functional Acknowledgment is the housekeeping document underneath all of this: it confirms that a given EDI transmission, whether a PO, an ASN, or an invoice, was received and structurally valid, independent of whether its business content was ultimately accepted. A missing 997 on a document a vendor believes was sent is the first sign that a transmission never actually landed.
| Document | Direction | Purpose |
|---|---|---|
| 850 | AutoZone to vendor | Purchase order |
| 855 | Vendor to AutoZone | Acknowledge, accept, or reject the order |
| 856 | Vendor to AutoZone | Advance ship notice before or at shipment |
| 810 | Vendor to AutoZone | Invoice, referencing the PO (and store number, for DSD) |
| 997 | Either direction | Functional acknowledgment that a document was received correctly |
| 846 | Vendor to AutoZone | Inventory availability, required for VDP |
Automation
InfiPlex reads incoming AutoZone 850s and identifies which program each belongs to, acknowledges automatically, generates the 856 from the actual ship event, invoices with the correct store reference carried through for DSD orders, and keeps the 846 inventory feed current for vendors running VDP. Program page: AutoZone integration; chargeback prevention across this lifecycle is covered in the vendor compliance and EDI chargebacks guide.
Frequently asked
The questions vendors ask about how an AutoZone order actually flows.
The core sequence is the 850 (purchase order), 855 (acknowledgment), 856 (advance ship notice), and 810 (invoice), with 997 (functional acknowledgment) confirming each transmission was received correctly. Some AutoZone programs, including VDP, also require an 846 inventory feed.
The 855 is a business acknowledgment, it states whether the order is accepted, rejected, or accepted with changes. The 997 is a technical acknowledgment, confirming only that a transmission was received and structurally valid, regardless of its business outcome.
Because a mismatch between what the ASN reports and what physically arrives is the most common trigger for chargebacks across retail EDI generally, AutoZone included, since receiving systems check the physical shipment against the ASN's claims.
Yes. A DSD invoice must carry the same store number that was on the original purchase order's REF segment, so AutoZone can reconcile the shipment and the bill against the same store.
For programs like VDP, where a purchase order is only generated after a customer orders an item in-store, AutoZone relies on the vendor's own reported inventory, sent via 846, to know whether that item is genuinely available before generating the PO.
It suggests the transmission may not have been received or was not structurally valid, and is usually the first sign to check that a PO acknowledgment, ASN, or invoice never actually reached AutoZone.
The core document sequence is the same across all three, but the data within it differs: DSD carries a store reference through to invoicing, VDP depends on the 846 feed to exist at all, and STH ships to a consumer address instead of a store.
By identifying which AutoZone program each incoming PO belongs to, acknowledging automatically, generating the ASN from the real ship event, carrying the store reference through to invoicing for DSD, and keeping the inventory feed current to support VDP.
Resources
Acknowledgment, ASN from the ship event, invoices with the right references, inventory feeds that keep VDP honest. Live in 1–3 business days.
We connect AutoZone vendors across the full document lifecycle every week. Tell us your current setup and we will map the connection. Contact us, email info@infiplex.com, or call 888‑770‑0857.
InfiPlex™ is a trademark of InfiPlex. AutoZone is a trademark of AutoZone, Inc. or its affiliates. InfiPlex is an independent integration provider and is not endorsed by or affiliated with AutoZone. Program rules, EDI requirements, and chargeback amounts are set by AutoZone and change; verify current terms in your vendor compliance manual before relying on them. ©2026 InfiPlex. All rights reserved.
InfiPlex provides eCommerce companies, warehouses, and 3PLs with a robust platform to manage their sales channels.
©2026. All Rights Reserved. Privacy Policy | Terms & License