Chewy is not owned by PetSmart any more, and its dropship program runs through Rithum's Dsco platform rather than a direct connection. Autoship sends subscription forecasts back to you. AIMS360 runs Chewy alongside your other pet accounts from one pool of stock.
PetSmart bought Chewy in 2017. Chewy went public in 2019 and has operated independently since. A surprising number of EDI pages still describe it as a PetSmart subsidiary, and vendors inherit the assumption: separate company, separate buying, separate onboarding. On the dropship side it also routes through Rithum's Dsco platform rather than a direct connection, and Autoship sends subscription forecasts back to you.
Chewy EDI is the electronic document exchange Chewy uses with its vendors. Commonly published across trading partner directories: the 850 purchase order at X12 version 5010, the 855 acknowledgment, the 856 advance ship notice, the 810 invoice, the 846 inventory advice and the 997, with an 852 product activity document carrying sell through data. Dropship is described as routing through Dsco, the Rithum platform.
Chewy does not publish a public routing guide. Everything below is drawn from trading partner directories and published fulfillment guidance, presented as the shape of the program rather than as a specification to map from.
What makes Chewy different from the rest of your pet accounts is not the document list, which is fairly ordinary. It is that Chewy is ecommerce first with a subscription engine underneath, and it gives you back more data than most retailers do.
PetSmart acquired Chewy in 2017. Chewy went public in 2019 and now operates as an independent public company. The stale version of that fact is still repeated across EDI vendor pages, and it leads vendors to assume one relationship covers both.
It does not. Separate buying organizations, separate vendor setup, separate EDI onboarding, and materially different programs on each side. PetSmart is store replenishment into distribution centers with an ecommerce dropship program bolted alongside. Chewy is ecommerce first, with subscriptions as the core of the demand rather than an add on.
The one thing they do share is your warehouse. Both draw on the same physical units, and neither reserves stock for the other, which is exactly how a brand oversells a subscription it had already committed.
Published fulfillment guidance describes Chewy dropship EDI running through Dsco, the platform Rithum acquired as part of CommerceHub.
Dsco is the same platform brands use for Nordstrom, Kohl's, Neiman Marcus and Saks Off Fifth. If you are connected there for an apparel or accessories line, the plumbing is familiar even though the account is new.
Rithum runs several separate systems. OrderStream is the one Macy's names in its dropship standards; Dsco is a different platform. Brands routinely say Rithum when they mean one specific product, so confirm which your Chewy program uses before you build.
Published guidance describes a routing guide naming approved carriers, typically FedEx and UPS, with required service levels. Late or missing advance ship notices are described as triggering chargebacks.
Whatever the transport layer, the ship notice has to match what left the building. AIMS360 builds it from the units the warehouse scanned rather than from what the order said should have been picked.
Commonly published across trading partner directories. Confirm the set issued to your account.
| Document | Direction | What it carries |
|---|---|---|
| 850 | Chewy to you | Purchase order, described at X12 version 5010. Carries Autoship subscription allocations alongside regular orders |
| 855 | You to Chewy | Acknowledgment confirming receipt and ability to fulfill |
| 856 | You to Chewy | Advance ship notice with tracking and carton contents. Late or missing ASNs are described as triggering chargebacks |
| 810 | You to Chewy | Invoice, matched to the purchase order and the ASN |
| 846 | You to Chewy | Inventory advice. What Chewy can promise, including against Autoship commitments |
| 852 | Chewy to you | Product activity data. Sell through, meaning what actually moved rather than what was ordered |
| 997 | Both ways | Confirms a document arrived and was structurally valid |
Published integration profiles describe Autoship allocations arriving on the 850 and, less commonly, subscription forecasts coming back to the vendor for inventory planning. Most retailers do not return demand predictions at all.
That changes the character of the relationship. A purchase order tells you what to ship this week. A subscription forecast tells you what is already committed for the weeks after, which is planning data rather than order data, and it is worth reading into replenishment rather than leaving in a portal.
Pair it with the 852 sell through and a pet brand has two independent views of the same future: what shoppers have already committed to buy, and what is genuinely moving off the virtual shelf. Very few of your other accounts hand you both.
The flip side is the obligation. A subscription is demand you have already promised, so an oversell does not cost one order, it breaks a recurring one, and those rarely come back. That is why the number you publish through the 846 has to reflect what you can actually ship across every channel drawing on the same units.
We have not found a public Chewy specification requiring lot codes and expiration dates on the ASN, so we are not going to claim one exists. Plenty of pages would.
What is true regardless is that pet food, treats, chews and supplements are consumables with a shelf life, and pharmacy and health products more so. Lot and date traceability is an operational requirement whether or not a particular retailer asks for the values in a file, because the question a withdrawal asks is which lots went where, and that answer has to exist before anyone asks it.
AIMS360 carries lot and batch numbers and expiration dates on inventory. Allocation can work oldest first rather than shipping whatever was nearest the door, and the shipment record knows which lot went to which order. If Chewy asks for those values, the data is there. If it does not, you still have it.
AIMS360 is a consumer brands ERP with EDI built in-house and mapped to each retailer's own specification.
Chewy orders import into the same platform holding your inventory, drawing on the same pool as PetSmart, Tractor Supply and your other accounts rather than a channel specific number.
The 846 reflects what you can genuinely ship across every channel, which is what protects a subscription commitment from a strong week somewhere else.
Lot and expiration data sits on the inventory record, so allocation can work oldest first and the shipment knows which lot it carried.
Mobile scanning builds the shipment and the ASN is generated from those units with tracking, on the carrier the routing guide specifies.
Autoship forecasts and 852 sell through read back into the same records as the orders, so planning happens against one dataset instead of three exports.
EDI is part of the platform, with no per document, per transaction or kilocharacter charges on our side as volume grows.
Chewy is one of 350+ retailer connections on AIMS360, alongside PetSmart, Tractor Supply, Ace Hardware and Rural King, all drawing on one pool of stock.
Not any more, and a great many EDI pages still say otherwise. PetSmart acquired Chewy in 2017, Chewy went public in 2019, and it now operates as an independent public company. The practical consequence for a vendor is that a PetSmart relationship does not carry you into Chewy. Separate buying, separate vendor setup, separate EDI onboarding, and different document behavior on the dropship side.
Commonly published across trading partner directories: the 850 purchase order, described at X12 version 5010, the 855 purchase order acknowledgment, the 856 advance ship notice, the 810 invoice, the 846 inventory advice and the 997 functional acknowledgment, with an 852 product activity document carrying sell through data. Chewy does not publish a public routing guide, so confirm the set issued to your account before mapping.
Published fulfillment guidance describes Chewy dropship EDI running through Dsco, the Rithum platform formerly part of CommerceHub. That matters because Dsco is the same platform brands already use for Nordstrom, Kohl's, Neiman Marcus and Saks Off Fifth, so if you are connected there the plumbing is familiar. Rithum runs several separate platforms, so confirm which one your Chewy program uses before you build.
Autoship is Chewy's subscription repeat delivery program. Published integration profiles describe Autoship allocations arriving on the 850 and, unusually, subscription forecasts coming back to the vendor for inventory planning. Most retailers do not return demand predictions at all. Treated properly that is planning data, not just an order feed, and it lets you hold stock against demand that is already committed.
We have not found a public Chewy specification stating it, so we are not going to claim one. What is true generally is that pet food, treats, chews and supplements are consumables, and pharmacy and health items more so, which means lot and date traceability is an operational requirement whether or not a given retailer asks for the values on the ASN. AIMS360 carries lot and batch numbers and expiration dates on inventory, so the data exists if Chewy asks for it.
Published fulfillment guidance describes a routing guide specifying approved carriers, typically FedEx and UPS, along with required service levels and carton preparation. Late or missing advance ship notices are described as triggering chargebacks. Chewy does not publish the guide openly, so treat that as the shape of the program and work from the version issued to your account.
Product activity data, meaning sell through. It tells you what actually moved rather than what was ordered, which is the difference between reacting to purchase orders and planning against demand. Combined with the Autoship forecast it gives a pet brand two independent views of the same future, and both are worth reading into replenishment rather than leaving in a portal.
You should, and that is precisely the risk. They are separate companies with separate programs, but they draw on the same physical units in your warehouse, and neither reserves stock on the other's behalf. Publishing two independent availability numbers is how a brand oversells a subscription. AIMS360 holds one available to sell pool and publishes derived positions to each channel.
Yes. AIMS360 EDI is built in-house and mapped to each retailer's own specification, so Chewy orders land against live inventory, availability publishes from one pool, and the ASN is built from the units the warehouse scanned. Lot and expiration data carries through on consumables. Chewy is one of 350+ retailer connections, with 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. Chewy does not publish a public vendor or routing guide, so the document set, dropship routing and carrier rules described here are drawn from third party EDI trading partner directories and published fulfillment guidance, and are presented as the shape of the program rather than as a specification. No public Chewy source states a lot code or expiration date requirement on the ASN, and this page does not claim one. Requirements are issued to each vendor directly and can change, so confirm anything commercially significant with your Chewy contact. Chewy, Autoship, Rithum and Dsco are trademarks of their respective owners, and AIMS360 is not affiliated with or endorsed by Chewy, Inc.
A 30 minute live demo taking a Chewy order through lot aware allocation, ASN and invoice from one record, with Autoship forecasts landing in the same place, built for pet brands.
