Chewy built its reputation on delivery speed, and its supplier program pushes that expectation upstream. Vendors fulfilling dropship orders are, functionally, Chewy's warehouse — which means Chewy needs to know what you can ship at all times and needs proof of shipment the moment it happens. Two documents carry nearly all of that weight.
Inventory, several times a day
The defining requirement is cadence on the 846 inventory advice: dropship feeds run multiple times daily. This is faster than most retail programs ask for, and it exists because Chewy is actively selling against your positions hour by hour. Let the feed drift stale and the consequences arrive from both directions — stockouts suppress your listings, while overstated availability produces orders you cannot fill.
At that frequency there is no version of this done by a person exporting spreadsheets. The Chewy 846 has to be generated from live warehouse balances on schedule, every time, which makes the inventory feed the first thing to automate and the last thing to ever touch manually.
Ship notices that notify customers
The second pillar is the 856 ship notice, and its job at Chewy is customer-facing: every shipment's ASN carries the carrier and tracking number, because that data feeds the notification the customer receives. Transmit at carrier handoff, with tracking attached, and the customer sees their order moving; transmit late or trackingless and Chewy's dropship SLA program sees it too.
Between those two documents sits the order flow itself — purchase orders in, standard 850-style order processing with the customer's address as the ship-to, acknowledgment out, then pick, pack, ship, and the tracking-bearing ASN. The rhythm is retail-simple; the tempo is e-commerce.
EDI and API, one connector
Chewy's stack is mixed: core documents ride X12 4010 EDI, while some programs run over API. That split is Chewy's implementation detail, not your problem — EDISQ presents both transports as a single connector, so an inventory update or ship confirmation flows the same way regardless of which pipe carries it. You automate the business event once.
Warehouse granularity keeps promises honest
One subtlety separates adequate Chewy feeds from good ones: report inventory at the warehouse level, not as a national pool. Chewy's delivery promise to the customer depends on where the unit actually sits — a position that blends coasts into one number produces ship-time surprises even when the total is accurate. If a 3PL holds part of your stock, fold its balances into the feed on the same cadence (the 945 warehouse advice is typically the source), so the 846 reflects everything sellable and nothing that isn't.
What breaks first
When a Chewy integration degrades, the inventory feed is almost always the first casualty — a stuck scheduler, or a warehouse export that silently stopped updating. Instrument the cadence itself: alert when a feed run fails, and alert again when positions stop changing in ways that look implausible for your velocity. Chewy's systems will notice stale data before you do, and by then it's showing as suppressed listings.
Standing up a Chewy connection
The onboarding arc is short. Connect the platform running your fulfillment — ShipBob, Extensiv, NetSuite, or another of 30+ integrations — map SKUs and warehouses, schedule the 846 cadence, and wire ship-confirm to ASN generation. Replay Chewy scenarios in the sandbox and go live; the EDI side typically takes 1–2 days on certified maps.
Because dropship generates a steady stream of modest documents, pricing shape matters. EDISQ's is flat-footed simple: no fees for setup or mapping — just documents, with 25 free per month and per-document rates that open at $0.50 and slide to $0.10 through the volume tiers, each tier billed marginally, plus a $100/month Production minimum that applies in full to usage once you're live. Connectivity is bundled whichever transport Chewy uses. The arithmetic for your volume is on the pricing page.
FAQ
Is Chewy EDI or API?
Both — core documents ride EDI while some programs use API. EDISQ presents the two as one connector, so your workflow does not change based on the transport.
How often does Chewy expect inventory updates?
Dropship inventory feeds run multiple times daily. Positions that go stale lead to stockouts that suppress your listings.
What must a Chewy ship notice include?
Carrier and tracking number for every shipment — the 856 is what powers the customer notification, so it transmits at carrier handoff with tracking attached.
What does Chewy EDI cost through EDISQ?
Per document only. Each month starts with 25 free documents; beyond that pricing runs from $0.50 per document downward with volume.