Region by region — that's how Whole Foods buys. Orders are cut per region and per DC, and what a region may order is gated by regional item authorization, which makes geography a first-class concept in Whole Foods EDI. A supplier ranged in three regions is effectively running three overlapping trading relationships on one connection.
Authorization before orders
The 850s from Whole Foods respect two gates. First, item setup must complete before the first order — UPC-led item identity means your products exist in Whole Foods' systems before they can appear on a PO. Second, regional authorization controls what each region's orders may contain; being ranged nationally is not a thing, being ranged region by region is.
The practical consequence: when an expected order doesn't arrive, or arrives without an expected item, the first place to look is authorization status by region — not the EDI pipe. Keep your own record of which regions carry which SKUs, and reconcile new-item launches against it.
The 846 keeps you orderable
Whole Foods consumes 846 inventory advice on a schedule, and per the 846 program, scheduled availability positions keep items orderable — stale data suppresses replenishment. That is a quietly severe consequence: an 846 feed that stops updating doesn't produce error messages, it produces missing orders, and missing orders read like soft demand until someone traces the cause.
Generate the feed from live warehouse balances on the agreed cadence, automatically, and alarm on failed runs. Availability data is the oxygen of the relationship.
ASNs on a perishable clock
The 856 follows grocery convention — transmitted before DC delivery — with one category-specific note: perishables run tighter windows than shelf-stable grocery. Cold chain compresses every buffer, including the documentation buffer, so ship-confirm-triggered ASN generation matters most exactly where the product spoils fastest. Structure the document from the physical load and let the warehouse event send it.
Deduction exposure at Whole Foods follows the ordinary grocery pattern — receipt mismatches and invoice variances resolve as deductions through reconciliation — and the ordinary defenses apply: validated documents, event-driven timing, synchronized item data.
Treat regions as first-class in your own data
The regional model works best for suppliers who mirror it internally. Track authorization, item setup status, and order history per region rather than nationally, and route those distinctions into your planning: a region that just authorized a SKU will order in ramp-up quantities, while an established region orders in replenishment rhythm, and your 846 availability should anticipate both. When something goes quiet — one region's orders stop while others continue — region-level records turn a vague mystery into a specific question for a specific buyer. National-level bookkeeping can't see any of this until it becomes a revenue problem.
Direct, through UNFI, or both
Many categories reach Whole Foods shelves through UNFI rather than direct trade. Which path (or both) applies to you is a commercial decision made with your category team, and it changes who your EDI counterparty is: direct suppliers trade with Whole Foods; distributor-routed suppliers trade with UNFI. EDISQ supports either or both simultaneously, with the same item data feeding both relationships.
Setup and the meter
Getting live runs the grocery-standard path: complete Whole Foods item setup and regional authorization, connect your system — Katana for food manufacturers, NetSuite, or another of 30+ platforms — load item and region cross-references, schedule the 846, and certify the order-to-invoice flow in the sandbox. The EDI portion typically takes 1–3 days on certified maps.
The running cost is document-metered with nothing lurking: 25 free per month, then from $0.50 per document tapering to $0.10 through the volume tiers, billed marginally against a $100/month Production minimum that applies entirely to usage. Connectivity is included, and setup and mapping fees don't exist here — the pricing page tells the whole story.
FAQ
Do I trade with Whole Foods directly or through UNFI?
Both paths exist. Direct suppliers trade EDI with Whole Foods; many categories flow through UNFI. EDISQ supports either — or both at once.
Why do my items not appear on Whole Foods purchase orders?
Regional item authorization gates what may appear on a PO, and item setup must complete before the first order. Check authorization by region before assuming an EDI problem.
What is the 846 for at Whole Foods?
Scheduled availability positions that keep items orderable. Stale 846 data suppresses replenishment, so the feed should generate automatically on cadence.
What does Whole Foods EDI cost on EDISQ?
Per document: 25 free each month, then from $0.50 per document, decreasing with volume. No mapping or setup fees; going live runs on a $100/month Production minimum applied in full to usage, Whole Foods included as your first live partner.