Retailer requirements · October 14, 2026

McKesson EDI Requirements: How to Become Compliant

McKesson EDI — line-level 855 status codes, NDC-keyed 832 catalogs with contract tiers, national DC routing, and setup for pharma suppliers.

Pharmaceutical distribution measures response time in hours. McKesson replenishes a national network of pharmaceutical DCs on cycles that leave no room for a slow answer, and its EDI program is built around one document most retail suppliers treat as an afterthought: the purchase order acknowledgment. At McKesson, the 855 is the working heartbeat of the relationship.

The 855, line by line

McKesson's 855 requirements ask for precision on three axes:

  1. Every line gets a status — IA (accept), IB (backorder), or IR (reject). Header-level blanket answers don't carry the information McKesson's replenishment engine needs.
  2. Backorders carry a revised availability date. An open-ended hold reads as a cancel — if a line is coming later, the acknowledgment says when.
  3. Same-day response. Pharmaceutical replenishment cycles are measured in hours, not days; the acknowledgment generates at order arrival, from live availability, without a queue.

The 855 done well is what keeps product flowing to pharmacies; done badly, it's how a supplier quietly falls out of the replenishment loop.

A catalog with three prices per item

The 832 price/sales catalog at McKesson is NDC-native and contract-aware. Per the 832 spec:

  • Catalog rows pair the NDC and McKesson item number with contract-tier pricing in CTP loops.
  • List, contract, and GPO pricing ride separate price classes — keep the tiers distinct. Pharmaceutical pricing is layered by design, and collapsing the layers corrupts downstream validation.
  • After the initial load, send deltas, not full refreshes. Changed rows only; the full-catalog republish is a one-time event.

Because orders and invoices validate against this data, catalog discipline is the upstream investment that keeps every later document matching.

Orders across a national network

850s route across McKesson's pharmaceutical DC network, which puts the N1*ST location cross-reference under permanent maintenance: keep it current as the network evolves, and treat unrecognized locations as stop-the-line events. Item lines carry both the NDC and the McKesson item number, and the cross-reference must translate in both directions on every document — a one-way map is half a map.

The classic errors, and what they cost

  • Header-level acknowledgments. A blanket accept tells McKesson's replenishment engine nothing about individual lines; per-line IA/IB/IR status is the requirement, not a refinement.
  • Backorders without dates. An IB status carrying no revised availability reads as a cancel, and the demand quietly re-sources elsewhere.
  • Price classes collapsed. List, contract, and GPO tiers merged into a single price corrupt validation on every downstream order and invoice — the CTP loops stay distinct for a reason.
  • Full catalog refreshes. After the initial load, changes travel as deltas; republishing the whole catalog creates churn where a changed-rows file would land clean.
  • A one-way NDC map. Orders arrive keyed by NDC and McKesson item number, and documents return the same way; the cross-reference has to survive the round trip.

In a relationship measured in hours, these are the differences between a supplier who keeps the loop moving and one the loop learns to route around.

Setup for pharmaceutical suppliers

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

The onboarding sequence: McKesson supplier setup, ERP connection — SAP S/4HANA, NetSuite, or another of 30+ platforms — NDC/item cross-reference and catalog load with price classes verified, then sandbox certification with backorder and rejection scenarios included, because at McKesson the acknowledgment paths are the ones that matter. The EDI side typically takes 2–4 days on certified maps.

Spend is metered in documents and nothing else: after the 25 free each month, rates start at $0.50 per document and step down to $0.10 across the volume tiers, billed marginally. There is no setup or mapping invoice — going live is a $100/month Production minimum applied in full to usage, McKesson included as your first live partner — and connectivity, whatever the transport, is included. Every tier is published on the pricing page.

FAQ

Does McKesson require EDI from its suppliers?

Yes — replenishment into its pharmaceutical distribution centers runs on EDI, and the 855 with line-level status codes is the working heartbeat of the relationship.

Which documents matter most in a McKesson setup?

The 855 and the 832. Line-level acknowledgments keep orders moving, and the price/sales catalog keeps NDC-level contract pricing aligned on both sides.

How should backorders be acknowledged to McKesson?

With a revised availability date on the backordered line. An open-ended hold reads as a cancel, so every IB status needs a date attached.

What is the EDISQ cost for McKesson EDI?

Per document: 25 free monthly, then from $0.50 per document with volume discounts. Connectivity, setup, and mapping carry no separate charge.