Wayfair EDI Requirements: How to Become Compliant

There is no distribution center at the end of a Wayfair order. Every purchase order is a consumer order, every ship-to is somebody's home, and the whole machine runs on data you feed it. That inversion — retailer as storefront, supplier as fulfiller — is what makes Wayfair EDI different from every DC-based program, and it reorders which documents matter most.

The 846 is the storefront

In dropship, Wayfair sells what your 846 inventory advice says you have. Two rules follow from Wayfair's 846 requirements:

• Keep the cadence. Feeds run on a fixed schedule, and stale positions have a price: listings get suppressed when Wayfair loses confidence in your data, and oversells caused by inflated positions are charged to you.
• Report by warehouse. Lead-time promises to the customer depend on which building the unit ships from, so warehouse-level granularity keeps those promises accurate.

The practical implication: the 846 must be generated from live warehouse data on schedule, untouched by hands. This is the document where automation stops being a convenience and becomes the product.

Orders addressed to living rooms

The 850 arrives carrying a consumer's name and home address — the ship-to comes from the order itself, never from a DC cross-reference table. Your fulfillment system needs to consume that address dynamically, print it correctly, and ship parcel or LTL as the product demands.

Turnaround expectations are consumer-grade too: a delivery estimate started ticking the moment the customer checked out, so acknowledge quickly and pick immediately. In dropship, your warehouse is the retailer's fulfillment promise.

The ASN is a tracking event

Wayfair's 856 exists to feed the customer's tracking page. It transmits at carrier handoff — not at any appointment, because there isn't one — and carries the carrier and tracking number for each shipment. From the shopper's perspective, your ASN is the "your order has shipped" email; late or trackingless ASNs translate directly into support tickets and performance-standard trouble.

Wayfair manages all of this through its supplier performance standards — dropship SLAs covering the feed, the turnaround, and the ship notice. Meeting them is the same job three times: connect the document to the operational event it describes and let it fire automatically.

Big-and-bulky adds a fork

Much of what sells on Wayfair ships LTL rather than parcel, and the fork matters operationally. Parcel shipments produce a tracking number at label print; LTL shipments produce a PRO number at carrier pickup, often hours later. Your ASN trigger has to handle both paths — fire at the event that yields real tracking data for that mode, and never send a placeholder to satisfy the clock. Suppliers with mixed catalogs should test both branches in the sandbox, because the parcel path working is no evidence the freight path does.

Failure modes worth engineering away

Dropship problems cluster in three places: an 846 that keeps its schedule but reports a stale snapshot, an order whose customer address gets truncated or reformatted by an intermediate system, and a ship notice that fires before real tracking data exists. Design against all three explicitly — verify feed freshness rather than feed success, pass addresses through untouched, and gate ASN transmission on carrier data being present.

Wiring it up

Commerce-native systems fit this program well. Connect Shopify, ShipStation, NetSuite, or any of 30+ platforms; map SKUs and warehouses; schedule the 846; wire order intake and ship-confirm events; then run Wayfair's scenarios in the sandbox. EDISQ's certified Wayfair maps handle both the EDI documents and the API-side programs under one connector, and the EDI setup typically takes 1–2 days.

Dropship produces lots of small documents, which is exactly the shape EDISQ's model favors: after each month's 25 free documents, per-document rates start at $0.50 and compress toward $0.10 as volume accumulates, billed tier by tier. No mapping or setup fees, connectivity included, and a $100/month Production minimum that counts wholly toward documents — the pricing page shows how high-frequency, low-touch volume stays cheap.

FAQ