PetSmart runs DC replenishment and ecommerce dropship as separate EDI programs, wants lot codes and expiration dates on the ASN, and flags pet food vendors who send carton ASNs where pallet ASNs are expected. AIMS360 runs both channels from one pool of stock.
Distribution center replenishment and the ecommerce dropship program run separate document flows with separate onboarding, and being live on one does not put you on the other. On consumable products the advance ship notice is expected to carry lot numbers and expiration dates. And on bulk pet food, a carton level ASN where a pallet level one belongs is what gets a vendor flagged. AIMS360 runs both channels against one pool of stock, with lot and expiry on the record rather than on a spreadsheet.
PetSmart EDI is the electronic document exchange PetSmart uses with its vendors, running on ANSI X12. The set published consistently across trading partner directories is the 850 purchase order, the 855 acknowledgment, the 856 advance ship notice, the 810 invoice and the 997 functional acknowledgment, with an 846 inventory advice on the ecommerce side. PetSmart expects the 810, the 850 and the 856 to reconcile line by line before it pays.
PetSmart does not publish a public vendor or routing guide the way Macy's and Ace Hardware do. What follows is drawn from trading partner directories and vendor guidance, and it is presented as the shape of the program rather than as a specification to map from. The document issued to your account is the one that counts.
Two things separate this from a general retail EDI setup, and both come from the category rather than the retailer. Pet food, treats, chews and supplements are consumables, so lot and date data has to travel with the shipment. And a forty pound bag of dog food does not pack, palletize or scan like a leash.
This is the same trap Ace Hardware sets, and brands walk into it the same way: they complete one onboarding and assume the other channel is switched on.
Bulk purchase orders into PetSmart distribution centers for store replenishment. This is the program most vendors start on, and the one the standard document set describes. Carton and pallet marking, routing compliance and receiving appointments all apply here.
Orders ship direct to the shopper from your warehouse. Published vendor guidance states this program has its own service level agreement and its own EDI flows, and that being set up for DC purchase orders does not automatically enable it. Expect a second onboarding and a second round of testing.
Availability published through the 846 is what PetSmart uses to decide what it can promise online. On a subscription program that number is not just a listing, it is a commitment already made to a shopper.
The same unit can sit against a DC purchase order and an ecommerce availability feed at once. Nothing upstream reconciles that for you, which is the argument for holding one available to sell number rather than publishing two independent ones.
Commonly published across trading partner directories. Confirm the set issued to your account before mapping anything.
| Document | Direction | What it carries |
|---|---|---|
| 850 | PetSmart to you | Purchase order. Regular stock plus, on the ecommerce side, AutoShip subscription allocations |
| 855 | You to PetSmart | Acknowledgment confirming acceptance, substitution or availability |
| 856 | You to PetSmart | Advance ship notice. On consumables, expected to carry lot numbers and expiration dates |
| 810 | You to PetSmart | Invoice. Must align with the 850 and the 856 on UPC, quantity, price and allowances |
| 846 | You to PetSmart | Inventory advice. Drives what the ecommerce program can promise, including subscriptions |
| 997 | Both ways | Confirms a document arrived and was structurally valid |
On consumable pet products, published integration profiles describe the 856 carrying lot tracking and expiration dates for pet safety. That is the difference between a withdrawal you can answer in an afternoon and one that takes a week of reconstructing which cases went where.
The reason it is hard is that the data has to originate upstream. A lot number typed onto an ASN at the end of the process is a guess. A lot number recorded when the goods were received, carried through allocation, and attached to the units that were scanned into the carton is a fact.
AIMS360 carries lot and batch numbers and expiration dates on inventory, so the lot that shipped against a PetSmart purchase order is on the shipment record. The ASN reads from that record rather than from someone's recollection, and a recall question becomes a query rather than an investigation.
Published vendor guidance notes that large pet food bags and bulk items often require pallet level ASN structures rather than carton level, and that vendors sending carton only structures get flagged.
A brand selling both forty pound bags and boxed treats can need a pallet hierarchy on one item and a carton hierarchy on another, on the same purchase order. The warehouse has to be able to build either from the same shipment.
Whichever structure applies, the GS1-128 label on the physical unit has to agree with the file. Commonly published guidance describes a 4 by 6 inch carton label carrying the mandatory data elements, with specified formatting and placement.
PetSmart expects the 810, the 850 and the 856 to align on UPC, quantity, unit price and allowance amounts. A mismatch in any of them is what turns into a deduction.
In AIMS360 the label prints and the ASN is built from the same scanned units, and the invoice is generated from that same shipment. The three documents reconcile because they came from one record, not because someone checked them against each other.
AutoShip is PetSmart's subscription repeat delivery program, and published integration profiles describe AutoShip allocations arriving on the 850 alongside regular stock orders.
The operational consequence is worth sitting with. On a normal order, an oversell costs you that order. On a subscription, it breaks a recurring commitment a shopper already made, and those do not usually come back. That is why the availability number you publish through the 846 has to reflect what you can genuinely ship, across every channel drawing on the same units.
AIMS360 holds one available to sell pool across your warehouse, your 3PL and your other accounts, and publishes derived positions to each channel. A strong week on Shopify cannot quietly consume units already promised to a PetSmart subscription.
Supplier registration is commonly described as running through the Ariba Commerce Cloud platform, with business documentation, financial statements and certifications, alongside PetSmart's Supplier Code of Conduct covering labor practices and environmental responsibility. Pre-approval is also described for subcontracting arrangements.
EDI onboarding follows a buyer relationship rather than preceding it. Nothing on this page is a route to a buyer. It describes what you need to be ready for once one exists.
AIMS360 is a consumer brands ERP with EDI built in-house and mapped to each retailer's own specification, so the ERP and the EDI are one system rather than two kept in step.
PetSmart purchase orders import into the same platform holding your inventory, so you see what is available before committing to the date, with DC and ecommerce orders drawing on one pool.
Lot and expiration data is on the inventory record, so allocation can work oldest first rather than shipping the newest lot because it was nearest the door.
Mobile scanning builds cartons and pallets, so the system can produce either ASN structure from the same shipment because it watched the load go together.
The GS1-128 label prints and the ASN is built from the same scanned units, carrying the lot and expiration values recorded upstream.
The 810 comes off the same shipment, so UPC, quantity and price agree with the 850 and the 856. Any deduction that still arrives is logged against the original order.
EDI is part of the platform. A heavy season does not multiply a separate EDI bill, and there are no per document, per transaction or kilocharacter charges on our side.
PetSmart is one of 350+ retailer connections on AIMS360, alongside Costco, Target, Ace Hardware and Rural King, all drawing on one pool of stock.
The set published consistently across trading partner directories is the 850 purchase order, the 855 purchase order acknowledgment, the 856 advance ship notice, the 810 invoice and the 997 functional acknowledgment. The 846 inventory advice appears on the ecommerce side, where availability drives what PetSmart can promise on subscription orders. PetSmart does not publish a public routing guide, so confirm the exact set issued to your account before mapping.
No. PetSmart's ecommerce dropship program runs its own service level agreement and its own EDI flows, and being set up for distribution center purchase orders does not automatically enable it. Treat it as a second onboarding with its own testing. This is the same pattern as Ace Hardware, where the warehouse and dropship channels use different document sets.
On consumable pet products, expect to carry them. Published integration profiles for PetSmart describe 856 advance ship notices carrying lot tracking and expiration dates for pet safety, which is what makes a recall traceable to the cases that shipped and to the stores that received them. That data has to originate in the item and receipt records rather than being typed onto the ASN at the end.
On large pet food bags and bulk items. Published vendor guidance notes that these often require pallet level ASN structures rather than carton level, and that vendors who send carton only structures get flagged. The practical consequence is that one brand can need both hierarchies depending on the item, so the warehouse has to be able to build either from the same shipment record.
AutoShip is PetSmart's subscription repeat delivery program. Published integration profiles describe AutoShip allocations arriving on the 850 alongside regular stock orders, and inventory feeds carrying the availability that keeps subscription commitments fillable. The operational effect is that a portion of demand is committed ahead of time, so an oversell on another channel does not just cost one order, it breaks a recurring one.
GS1-128 barcode shipping labels with specified formatting and placement, commonly published as a 4 by 6 inch carton label carrying the mandatory data elements. As with any retailer, the label has to agree with the ASN, because a label that does not match the file is the fastest route to a receiving exception. AIMS360 prints the label and builds the ASN from the same shipment record.
PetSmart expects alignment between the 810 invoice, the original 850 purchase order and the 856 ASN. Discrepancies in UPC, unit price, quantity or allowance amounts are what produce deductions. Because AIMS360 generates the invoice from the same order and shipment data the ASN reported, the three documents reconcile by construction rather than being re keyed across separate systems.
Supplier registration is commonly described as running through the Ariba Commerce Cloud platform with business documentation, financial statements and certifications, alongside PetSmart's Supplier Code of Conduct covering labor and environmental practices. EDI onboarding follows a buyer relationship rather than preceding it. Nothing on this page is a route to a buyer; it describes what you need to be ready for once one exists.
Yes. AIMS360 carries lot and batch numbers and expiration dates on inventory, so the lot that shipped against a PetSmart purchase order is recorded on the shipment rather than reconstructed later. That is what lets the ASN carry the values PetSmart expects, and what makes a withdrawal answerable at the level of which lots went to which distribution centers.
Yes. AIMS360 EDI is built in-house and mapped to each retailer's own specification, so PetSmart purchase orders land against live inventory, the warehouse builds either a carton or pallet ASN hierarchy from the units it scanned, and lot and expiration data travels with the shipment. PetSmart is one of 350+ retailer connections, and there are no per document, per transaction or kilocharacter fees on our side. See the full retailer list.
Last reviewed 1 September 2026 by the AIMS360 EDI team. PetSmart does not publish a public vendor or routing guide, so the document set and requirements described here are drawn from third party EDI trading partner directories and published vendor guidance, and are presented as the shape of the program rather than as a specification. Requirements are issued to each vendor directly and can change, so confirm anything commercially significant with your PetSmart contact. PetSmart, AutoShip, Ariba and all other names referenced are trademarks of their respective owners, and AIMS360 is not affiliated with or endorsed by PetSmart LLC.
A 30 minute live demo taking a purchase order through lot allocation, pallet build, ASN and invoice from one record, built for pet brands.
