Distributor EDI inverts the usual retail priorities. With a chain retailer, the ship notice is the document under the microscope; with UNFI, the relationship runs on visibility — scheduled 846 inventory positions that keep your items orderable, and high-frequency 850 replenishment that expects same-day processing. Setting up UNFI is mostly about wiring those two rhythms so they run without you. The build takes 1–2 days; here's the order of operations.
Groundwork: items and destinations
Get your UNFI vendor relationship and item setup squared away first, and map your items against UNFI's identifiers in a cross-reference table. UNFI orders and inventory positions are organized around its DC network, so your location table needs UNFI's DCs in it from the start. If Whole Foods is part of your world, note the topology while you're here: many categories flow through UNFI, others trade direct with Whole Foods — EDISQ supports either path or both simultaneously, but knowing which you're on shapes what you test.
Connect the ERP — the source of both rhythms
Attach your business system (NetSuite, Fishbowl, Unleashed, or another of the 30+ supported platforms). It matters more here than in most setups because both key documents originate from live ERP data: the 846 reads your inventory positions, and same-day 850 turnaround only works if orders land as ready-to-fulfill sales orders without re-keying.
Schedule the 846 like the obligation it is
The 846 inventory advice goes out on a schedule, reporting positions per DC-serving warehouse. Treat the schedule as a commitment: distributors sell what they can see, and stale positions degrade UNFI's picture of your availability. Configure the feed to pull from current on-hand data at each transmission — not from a snapshot that ages between runs — and decide the granularity deliberately so lead-time expectations stay honest.
Automate the order loop for same-day turnaround
UNFI replenishment arrives at high frequency, and same-day processing is the operating assumption. The intake path should be entirely mechanical: 850 arrives, validates against your item and location tables, becomes a sales order, and the acknowledgment cycle proceeds from real availability. Any step that waits for a person becomes the bottleneck the whole relationship queues behind. Invoicing closes the loop — the 810 generated from shipment data so it reconciles cleanly on UNFI's side.
Test the tempo, then go live
A good UNFI sandbox session simulates a normal week compressed into an hour: several 846 cycles (verify positions refresh rather than repeat), a burst of orders (verify same-day flow with zero touches), and the invoice pass. At go-live, monitor two things — 997 acknowledgments on everything, and 846 feed freshness, because a silently stalled inventory feed is invisible until order volume sags. Food-and-beverage suppliers scaling across distributors will find the same machinery reusable; see the food & beverage solutions page for the broader pattern.
A day-one readiness checklist
Before declaring the setup done, confirm five things in writing: the DC cross-reference covers every UNFI location in your program; the 846 schedule matches what UNFI expects and pulls live positions; order intake runs to sales order with zero manual steps; the missed-feed alert has actually been tested by breaking something on purpose; and someone owns the exception queue. Five yeses means the relationship can scale on its own; any no is tomorrow's incident, scheduled in advance.
What it costs
The commercial model matches the document rhythm: the first 25 documents each month are free, then pricing runs from $0.50 per document down to $0.10 at the top tier, billed marginally as volume crosses each threshold. Scheduled 846s, orders, invoices — each is simply one document on the meter, with connectivity, maps, and testing included, no mapping or setup fees, and a $100/month Production minimum applied entirely to usage. Details at pricing.
FAQ
Which documents drive a UNFI setup?
The 846 inventory advice and the 850 purchase order. Scheduled inventory positions per DC keep items orderable, and high-frequency replenishment orders expect same-day processing.
How long does UNFI EDI take to stand up?
About 1–2 days on the EDI side with certified maps. The scheduled 846 feed is the piece that needs real automation behind it.
Why does a distributor need my inventory data?
Distributors sell what they can see. If your 846 positions go stale, UNFI's view of your availability degrades — and so does your order flow.
Does UNFI matter for Whole Foods suppliers?
Often, yes — many categories reach Whole Foods through UNFI, while others trade direct. EDISQ supports either path, or both at once.