Industry guides · October 6, 2026

Dropship EDI Operations: Running the 846/856 Loop at Scale

How dropship EDI really runs — 846 inventory cadence, consumer ship-tos on the 850, tracking numbers in the 856, and an 810 for every order.

Retail EDI grew up around truckloads: one purchase order, hundreds of cartons, a single DC appointment. Dropship inverts all of it. The retailer merchandises your catalog, the consumer buys, and you ship one parcel to one doorstep — so the same documents now run thousands of small cycles instead of a few big ones. Partners like Wayfair and Chewy built their supplier programs around this loop, and its operating rules are worth learning before the first order lands.

Inventory is the front door

In a dropship program, the 846 inventory advice is what earns you orders. The retailer only sells what your last feed said was available, which makes the 846 your de facto storefront. Wayfair runs inventory feeds on a fixed schedule, and stale positions carry a double penalty there: listings get suppressed, and oversells are charged back to you. Chewy expects dropship inventory updates multiple times daily for the same reason — a stockout your feed missed leaves a listing live that shouldn't be, or suppressed when it shouldn't be.

Two practices follow. Generate the 846 directly from live inventory rather than a nightly export, and where the partner supports it, report positions by warehouse — Wayfair uses warehouse-level granularity to keep its lead-time promises accurate.

Every 850 is a consumer order

A dropship 850 purchase order does not route to a distribution center. The ship-to is a customer's home address carried inside the document — at Wayfair it always comes from the 850 itself, never from a location cross-reference table. That changes the mapping problem: instead of resolving a store number against a table, your system has to pass a one-time address through to the warehouse and onto the parcel label untouched.

Turnaround matters more than in wholesale, too. The consumer saw a delivery estimate at checkout, and that estimate is already counting down when the order arrives; Wayfair expects fast acknowledgment for exactly this reason. Letting orders sit for an afternoon batch job is how dropship service levels get missed.

The 856 feeds the tracking page

A dropship 856 is less about pallet hierarchy and more about the parcel: one shipment per order, with carrier and tracking number attached. Both Wayfair and Chewy pipe that tracking data into the customer's order-status page, so an ASN missing its tracking number is a customer-visible failure rather than a back-office one. Timing follows the parcel, not an appointment — at Wayfair, the ASN transmits when the package is handed to the carrier.

Behind it comes the 810 invoice, one per order, matched to its PO. A wholesale supplier might cut thirty invoices a month; a dropship supplier cuts one per consumer sale. Each document is tiny, but a single order typically produces four of them: an 850 in, then an 855, 856, and 810 out.

Running the loop without adding headcount

Both partners formalize the expectations — Wayfair through its supplier performance standards for dropship SLAs, Chewy through its dropship SLA program — and both mix EDI with API endpoints on some programs, which EDISQ presents as a single connector so your side of the flow stays uniform. The playbook that keeps scorecards clean is automation end to end: the 846 on cadence from live stock, orders landing in your system and acknowledged on arrival, ship confirmation triggering the 856 with tracking attached, and the 810 generated automatically behind it. Our retail solutions page shows how this fits a multi-channel operation, and the Wayfair EDI requirements post goes deeper on that specific program.

High document counts are also why pricing structure matters in dropship. EDISQ meters this loop the way it meters everything else: the first 25 documents each month cost nothing, after which documents start at $0.50 and step down to $0.10 at the highest volume tier, billed marginally — with no mapping or setup invoices to spread across thousands of small orders, and a flat $100/month Production minimum that applies in full to document usage. AS2, SFTP, and VAN connectivity are part of the service. The full ladder is on the pricing page.

FAQ

How often should I send the 846 in a dropship program?

On the partner's clock. Wayfair runs inventory feeds on a fixed schedule and Chewy expects updates multiple times daily. Feeding the 846 from live inventory is the only way to keep listings up and avoid oversell charges.

What makes a dropship 856 different from a retail ASN?

It covers one consumer order, carries the carrier and tracking number, and transmits at carrier handoff rather than before a DC appointment. The tracking data drives the retailer's customer-facing tracking page.

Do I invoice every dropship order separately?

Yes — the convention is one 810 per order, matched against its PO. Automation absorbs the volume, and per-document pricing keeps the cost of all those small invoices predictable.