Setup guides · October 16, 2026

How to Set Up EDI with Cardinal Health (Step by Step)

Cardinal Health EDI setup: NDC cross-references, an 832 catalog with clean units and price classes, line-level 855 automation, and testing.

Pharmaceutical distribution EDI puts the acknowledgment at the center of the world. Where a retail program obsesses over the ship notice, Cardinal Health runs on the 855: every order line gets an answer — accepted, substituted, or backordered — and blanket header-level acknowledgments bounce. Setting up Cardinal Health means building a system that can answer at that granularity automatically. Budget 2–4 days of technical work, in this order.

Get the item file right in both directions

Item identity here is the NDC first and the Cardinal item number second, and both appear on order and catalog lines — so the cross-reference must hold in both directions, resolving either identifier to your SKU and back. This table is the foundation for everything that follows: acknowledgment lines, catalog rows, and substitution citations all key off it. Build it from authoritative data and give it an owner, because pharmaceutical item files change and a stale entry produces confidently wrong documents.

Construct the 832 catalog with unit and price discipline

The Cardinal Health 832 is NDC-keyed on its LIN segments, and two details separate clean catalogs from rejected ones. First, unit-of-measure casing: EA versus CS mismatches are the classic rejection, so lock unit codes down in the map rather than trusting upstream data entry. Second, price classes: contract pricing rides CTP loops per customer agreement, and tier changes must sync before they take effect — a price that changes on an invoice before it changed in the catalog is a dispute in the making. Configure the catalog flow to publish from your item master with both rules enforced at validation time.

Automate the line-level 855

This is the heart of the build. Each inbound order line needs a real answer sourced from your inventory and allocation logic: accept it, backorder it, or substitute it. Two rules from Cardinal Health's program shape the automation. Header-level blanket acknowledgments bounce — the 855 must speak per line. And substitutions must cite the replacement NDC explicitly on the line, not describe it in free text. Wire the acknowledgment generator to live availability, teach it your substitution rules, and let the exceptions queue catch the lines that genuinely need a human decision.

Test like a distributor, then certify

Sandbox scenarios worth running before certification: an order with mixed outcomes (some lines accepted, one backordered, one substituted — verify each line status and the replacement NDC citation); a catalog publication with a contract-tier change (verify the CTP loops carry the right class); and a deliberately mis-cased unit of measure (verify validation blocks it). These three cover the failure modes that actually occur. Certification afterward is routine with certified maps.

Go live with the acknowledgment lane instrumented

Production monitoring centers on turnaround and completeness: 997s tracked on every exchange, 855 latency watched, and a daily check that no order line went unanswered. In a relationship where the acknowledgment is the operational heartbeat, an unanswered line is the equivalent of a missed shipment. The 832 catalog gets its own freshness check so price-class changes never lag their effective dates.

Bring the right people to the kickoff

Two roles shorten this project measurably. Whoever manages your contract pricing needs to be in the room when the CTP price classes are configured, since tier structures per customer agreement are commercial knowledge no integrator can infer. And whoever runs inventory allocation should review the substitution rules the 855 automation will apply — those rules make commitments to a distributor on your behalf, and they should be policy, not defaults.

Pricing for the volume you actually trade

EDISQ meters Cardinal Health traffic per document: 25 documents monthly at no charge, then from $0.50 per document tapering to $0.10 at the highest tier, computed marginally. Catalog publications and acknowledgments count like any document; maps, connectivity, and the sandbox are included; and nothing about pharmaceutical distribution carries a surcharge — no mapping or setup fees, just the $100/month Production minimum applied entirely to usage. The ladder is at pricing.

FAQ

What makes Cardinal Health EDI different from retail EDI?

It is acknowledgment-driven. The 855, with per-line accept, substitute, or backorder status, carries more operational weight than the ASN does in most retail programs.

How should substitutions appear on a Cardinal Health 855?

A substituted line must cite the replacement NDC — a free-text note does not count. Build substitution logic into the acknowledgment flow, not into emails.

What breaks Cardinal Health 832 catalogs most often?

Unit-of-measure casing: EA versus CS mismatches are the classic rejection. The catalog is NDC-keyed on LIN, with contract price classes riding CTP loops.

How long does a Cardinal Health setup run?

Plan for 2–4 days on the EDI side. The item file and price-class configuration are the long poles, not the connectivity.