KeHE's EDI program is small in document count and strict about rhythm. Two flows carry the relationship — a scheduled 846 that keeps your items visible and orderable, and 850s keyed to a DC network where lead times differ by location. There's no sprawling document matrix to certify; the challenge is building two feeds that never miss a beat. The KeHE build runs 1–2 days, sequenced like this.
Start with the DC cross-reference
Everything at KeHE is organized by distribution center. Orders arrive per DC, and lead times vary across the network, so the first table you build maps KeHE's DCs to your locations and carries the lead time each one operates on. This table quietly powers both flows: it tells the 846 what to report where, and it tells order intake what delivery promises are realistic for each receiving point.
Connect the system that holds your inventory truth
The 846 inventory advice is only as good as the data behind it, so the ERP connection is the load-bearing step. Hook up NetSuite, Katana, Cin7, or whichever of the 30+ supported systems tracks your stock, and confirm the connector reads live positions rather than a nightly export. The difference sounds academic until the feed runs at noon against midnight's numbers.
Put the 846 on rails
KeHE expects inventory advice on a fixed schedule, and the penalty for staleness is concrete: stale data suspends items. Configure the feed's cadence to match what KeHE has asked for, source it from current positions at each run, and — the step most setups skip — alert when a scheduled transmission fails to happen. A distributor's ordering system treats silence as absence; your monitoring should treat silence as an emergency. This is the piece of the setup that most repays doing properly, because it fails invisibly when done casually.
Automate order intake end to end
Replenishment 850s should travel from arrival to sales order without human touches: validated against the item cross-reference, routed with DC-specific lead-time awareness, acknowledged from real availability. During setup, resist the temptation to leave a manual review step in the path "just for the first month" — the habit calcifies, and distributor order cadence eventually outruns it.
Rehearse a normal week, then switch on
The sandbox session for KeHE is short but should be honest: several 846 cycles proving the positions change as inventory changes, an order burst proving zero-touch intake, and a deliberate failure — kill the inventory source and confirm the missed-feed alert fires. Then go live with 997 acknowledgment tracking on both flows. If natural and specialty channels beyond KeHE are on your roadmap, the same 846-first machinery extends across the food & beverage landscape.
Lead times are data, not folklore
A recurring KeHE-specific mistake deserves its own warning: treating lead times as a single number for the whole relationship. Because they vary by DC, the promise your order acknowledgment makes should be computed from the receiving DC's entry in your cross-reference — not from a company-wide default someone set during onboarding. Review the per-DC values with your KeHE contact when you load the table, and revisit them whenever your own logistics change. Distributor relationships run on kept promises at the DC level, and the table is where those promises are either encoded or invented.
The meter
KeHE traffic bills like all EDISQ traffic — per document, first 25 each month free, then from $0.50 with the rate stepping down to $0.10 at the highest tier under marginal billing. A scheduled 846 is one document per transmission; there's no charge for the schedule itself and no mapping or setup fees, connectivity is included, and the Production plan's $100/month minimum applies in full to usage. Tier-by-tier detail lives at pricing.
FAQ
What is the core of a KeHE EDI setup?
Two flows: the 846 inventory advice on a fixed schedule, and 850 purchase orders keyed to KeHE's DC network. Stale 846 data suspends items, so the feed is the priority.
How fast can KeHE EDI go live?
The technical side runs about 1–2 days with certified maps. Most of that is wiring the 846 to live inventory data and loading the DC cross-reference.
Why do KeHE lead times vary?
Lead times differ by DC across KeHE's network. Your cross-reference should carry them per location so promises made to orders reflect the receiving DC.
What happens if my 846 goes stale?
KeHE expects inventory advice on a fixed schedule; stale data suspends items from ordering. Automating the feed from live positions removes the risk.