Retailer requirements · October 9, 2026

McLane EDI Requirements: How to Become Compliant

McLane EDI for suppliers — weekly DC order cycles, UIN cross-references, 882 DSD settlement summaries, VAN connectivity, and invoice matching.

McLane is not a retailer — it's the distribution engine behind tens of thousands of convenience stores, moving product on fixed weekly rhythms that its suppliers either match or miss. Trading with McLane means adopting that rhythm: cyclical orders, disciplined item data, and a settlement flow that most retail suppliers have never seen.

The cycle is the deadline

Per McLane's 850 program, c-store replenishment orders run on fixed weekly cycles per DC — miss the cycle, miss the truck. There is no partial credit: an order processed a day late waits for next week's truck, and a week of empty c-store shelf space is how supplier relationships erode.

The operating requirement is same-cycle processing, automated: 850s land, validate, and flow to fulfillment the day they arrive. Item lines carry the McLane UIN alongside the UPC, cross-referenced both ways, and new items clear McLane item setup before the first order — the launch checklist runs data before commerce.

The 882: where the money reconciles

McLane's distinctive document is the 882 direct store delivery summary. Per the 882 flow, these are route-level DSD summaries that reconcile deliveries to settlement — and the guidance is blunt: map them into AR, don't file them. The 882 is how delivered quantities square against what you'll be paid; a supplier who archives them unparsed is reconciling settlement blind, and discovering variances months later when they've hardened into disputes.

Wired into your receivables process, the 882 turns settlement from a mystery into a checkable ledger line.

Invoices at DC level

The 810 reconciles against the 850 at DC level, and price variances age into deductions. The standard prevention applies with extra force in distribution economics, where margins are thin on both sides: invoices built from order-and-shipment lineage, prices traceable to the governing agreement, and variances caught by validation before McLane's reconciliation finds them.

Connectivity: the VAN is included

McLane trades through VAN interconnect — historically a second contract, kilocharacter billing, and a vendor relationship of its own. With EDISQ the VAN hop is folded into the per-document price: no separate VAN contract, no kilocharacter arithmetic, no additional bill. You see documents; the routing is plumbing.

Early mistakes new McLane suppliers make

  • Treating the cycle as a guideline. The weekly cadence per DC is a hard gate — an order processed after the cycle closes waits a full week, and c-store shelves record the gap.
  • One-way item mapping. The UIN and UPC must translate in both directions; a cross-reference that only reads inbound orders produces invoices McLane cannot reconcile.
  • Filing the 882 instead of processing it. Settlement summaries left unparsed mean variances surface months later, hardened into disputes rather than caught as fresh questions.
  • Launching before item setup completes. McLane orders only what its item file knows; the first order follows the data, never precedes it.

The pattern behind all four is rhythm. Distribution rewards suppliers whose automation moves when the cycle moves, and the relationship compounds quietly from there.

Setup and steady-state cost

1 Sign up free no card needed 2 Add McLane from the catalog 3 Test in the sandbox a full order, no risk 4 Certify with McLane 5 Go live documents flow

Onboarding follows the distribution pattern: McLane vendor and item setup, system connection (SAP Business One, NetSuite, or another of 30+ integrations), UIN/UPC and DC cross-reference load, then sandbox validation of the order, invoice, and 882 flows. The EDI side typically takes 2–4 days on certified McLane maps.

Steady-state, the cost model matches the weekly rhythm: per-document pricing where each month's first 25 documents are free, subsequent documents start at $0.50, and the rate slides to $0.10 through the volume tiers — billed marginally, VAN routing included, with no setup or mapping fees anywhere and a $100/month Production minimum applied entirely to usage. The pricing page shows how weekly-cycle volume prices out.

FAQ

Does McLane require a VAN?

McLane trades through VAN interconnect. The VAN hop is included in EDISQ's per-document price — no kilocharacter bills, no separate VAN contract.

What happens if I miss a McLane order cycle?

C-store replenishment runs on fixed weekly cycles per DC — miss the cycle, miss the truck. Same-cycle processing is the operating requirement.

What is the 882 from McLane?

A route-level DSD summary that reconciles deliveries to settlement. Map it into your AR process rather than filing it — it is how the money squares.

What does McLane EDI cost on EDISQ?

Per document with VAN routing included: first 25 monthly free, then from $0.50 per document, decreasing with volume.