Discovery & Supplier Profile
We confirm your supplier type (manufacturer, NLC replenishment, or CSOS), current ERP/WMS, order volume, and which optional transactions (852, 844, 849, 812) are in scope.
Cardinal Health moves pharmaceuticals, medical devices, and lab supplies through one of the largest healthcare distribution networks in the country — and it enforces DSCSA-compliant EDI on every purchase order. SBSA Technology automates your 850, 855, 856, and 810 transactions so every shipment clears without a $10-per-line ASN penalty.
Cardinal Health onboards manufacturers, NLC-replenishment suppliers, and controlled-substance vendors under different rules. SBSA configures your integration to the path that actually applies to you.
Cardinal Health transmits POs via AS2, SFTP, or VAN in real time. Manual POs still route by fax or the FAX401 system for non-EDI backup.
Confirm receipt and flag any quantity, pricing, or availability exceptions before you pick and pack.
The ASN must carry lot, expiration, and transaction data required under the Drug Supply Chain Security Act, sent before the shipment is received.
Pallet and case identifiers must follow HDMA bar code guidelines and match the ASN exactly — required for serialized receiving.
Every inbound EDI transmission from Cardinal Health must be acknowledged with a 997 inside 24 hours, and their return 997s must be monitored.
NLC replenishment orders carry distinct routing and scorecard tracking separate from direct-ship manufacturer orders.
Cardinal Health grades NLC suppliers on a service scorecard where ASN timeliness and accuracy are a direct scoring criterion.
A complete, on-time ASN reduces dock turnaround time and feeds serialized receiving at the NLC.
Backordered, allocated, and short-dated item status is communicated back through activity data for demand planning.
High-volume NLC replenishment requires full automation — SBSA bridges Cardinal Health's NLC EDI directly into your fulfillment system.
Controlled Substance Ordering System orders are placed via Axway / Cyclone AS2, enabling direct EDI 850 ordering of Schedule II products.
Non-exempt controlled items require full lot number and expiration data in the 856 — no omissions permitted.
Mixed shipments require the correct YNQ02 indicator per line so exempt and non-exempt items are processed correctly.
Cases and pallets of narcotics and controlled drugs are not required to carry unique GS1 identifiers in the ASN.
Every CSOS-linked ASN is checked against DSCSA field requirements before it leaves your facility.
A fixed, six-stage engagement — from first questionnaire to live monitoring — built specifically around Cardinal Health's DSCSA and ASN requirements, not a generic EDI rollout.
We confirm your supplier type (manufacturer, NLC replenishment, or CSOS), current ERP/WMS, order volume, and which optional transactions (852, 844, 849, 812) are in scope.
SBSA provisions your AS2, SFTP, or VAN connection to Cardinal Health's EDI environment, including Axway/Cyclone AS2 for CSOS-linked Schedule II ordering where applicable.
850, 855, 856, and 810 are mapped to your ERP's data model. The 856 is built against Cardinal Health's required DSCSA field list — lot, expiration, NDC, and quantity — line by line.
GS1-128 / HDMA carton and pallet label generation is wired to your ASN data, and your ERP is connected for automated sales orders, invoices, and inventory sync.
Every transaction is run against Cardinal Health's test POs and validated — 850 intake, 855 acknowledgment, DSCSA-complete 856, and 810 matching — before anything goes live.
Once certified, we cut over to production with continuous monitoring for 997 turnaround, ASN completeness, and any exception that could trigger a $10-per-line penalty.
Cardinal Health accepts AS2, SFTP, and VAN transmission. SBSA Technology configures, certifies, and monitors whichever protocol matches your volume and infrastructure.
Direct Point-to-Point
Encrypted, real-time transmission straight to Cardinal Health, including Axway/Cyclone AS2 for CSOS-linked Schedule II ordering. Preferred for medium-to-high volume suppliers.
Secure File Transfer
Secure FTP-based exchange for suppliers with existing SFTP infrastructure. SBSA manages server configuration, file monitoring, and DSCSA field validation.
Value-Added Network
EDI transmission through a third-party VAN. Minimal technical footprint on your end — SBSA provides your EDI ID and manages all routing to Cardinal Health.
SBSA Technology supports core and supplemental Cardinal Health Integration EDI documents. Critical transactions are highlighted because they carry the highest compliance risk when transmitted incorrectly or late.
Cardinal Health's PO initiating the order cycle — collected in real time via EDI, or manually by fax when EDI isn't in place.
InboundConfirms your ability to fulfill and flags quantity, pricing, or availability exceptions at the line level.
OutboundMust carry DSCSA transaction data and transmit before the shipment is received. Missing or incomplete ASNs trigger a $10-per-line charge.
Outbound $10/line penalty riskConveys detailed invoice data matched to the PO and ASN. SBSA auto-generates the 810 from confirmed shipment data.
OutboundMust be returned within 24 hours of any inbound transmission. SBSA monitors 997s in both directions in real time.
Outbound 24-hour SLASales and inventory activity shared for demand planning, including backordered, allocated, and short-dated items.
OutboundConveys credit and debit adjustment detail tied to pricing, chargebacks, or returns.
InboundTransmits debit, credit, or credit-request detail relating to preauthorized product transfers.
InboundResponds to an 844, in detail or summary, for parties requesting an accounting adjustment.
OutboundSBSA Technology provides pre-built ERP integrations that simplify EDI implementation, automate document exchange, and reduce onboarding time.
Full SuiteScript integration — POs, fulfillments, and DSCSA-ready ASNs synced in real time.
EDI-to-SAP IDOC mapping for enterprise manufacturers and large-volume distributors.
Dynamics 365 and NAV/BC connectors for full Cardinal Health order lifecycle management.
POs arrive as draft sales orders, invoices auto-generate on shipment, and remittance reconciles automatically.
Synchronize orders, inventory, invoices, and lot/expiration data required for DSCSA-compliant ASNs.
If your ERP or WMS isn't listed, SBSA builds a custom integration — flat-file imports, AS/400 mainframes, proprietary pharma ERPs, and everything in between.
Cardinal Health's ASN penalty is assessed automatically, monthly, with no manual review. SBSA automates every EDI and DSCSA touchpoint so your line-level compliance stays clean.
855 PO Acknowledgment auto-generated on receipt, with exceptions flagged before your team ever opens the order
GS1-128 / HDMA carton and pallet labels generated and checked against ASN data before goods leave your dock
810 invoice auto-generated per PO, matched to ASN quantities to eliminate short-payment disputes
852 Product Activity Data synced for backorder, allocation, and short-dated item visibility
856 ASN validated against Cardinal Health's required DSCSA fields before transmission — lot, expiration, NDC, and quantity
Exempt vs. non-exempt line logic (YNQ02) applied automatically on mixed shipments
997 Functional Acknowledgment returned within Cardinal Health's 24-hour requirement, in both directions
24/7 document monitoring — transmission failures and rejections surfaced before they become penalty line items
Common questions from suppliers beginning Cardinal Health EDI compliance
Yes. Cardinal Health requires an EDI 856 Advance Ship Notice to transmit DSCSA transaction data on every purchase order. In cases where an ASN isn't possible, the required information must instead be provided through a web portal or email — but standard EDI 856 transmission is the expected path for all EDI-enabled suppliers.
Cardinal Health charges $10 per line for any purchase order shipped without an ASN, or where the ASN is missing required fields. Penalties are calculated based on the prior month's EDI compliance and billed via a separate invoice once your quarterly total reaches $750 or more. SBSA validates every ASN's required fields before transmission to prevent this exposure.
Suppliers are required to return a 997 Functional Acknowledgment within 24 hours of receiving any EDI transmission from Cardinal Health, and are also expected to monitor the 997s Cardinal Health sends back for your own transmissions. SBSA automates both directions and flags any transmission that doesn't get acknowledged in time.
Cardinal Health expects new suppliers to be fully engaged and EDI compliant within 90 days of becoming a supplier, or immediately upon notification of noncompliance for existing suppliers. SBSA's implementation timeline is designed to certify you well inside that window.
The ASN must carry the transaction information required to satisfy the Drug Supply Chain Security Act, including lot number, expiration date, and product identifiers, along with the standard shipment, carton, and carrier detail Cardinal Health requires in the 856. Exempt items follow simplified rules — a UPC may substitute for an NDC, and lot/expiration data can be omitted where the item lacks those properties.
Yes. Cardinal Health enables direct EDI 850 ordering of Schedule II products through the Controlled Substance Ordering System (CSOS) via Axway/Cyclone AS2. Suppliers fulfilling CSOS orders still transmit DSCSA-compliant ASNs, though narcotics and controlled drugs are exempt from unit-level GS1 labeling requirements.
Unique pallet and case identifiers must conform to the GS1-128 standard and HDMA (Healthcare Distribution Management Association) bar code guidelines, and must be included in the ASN exactly as shipped. This data supports serialized receiving and helps Cardinal Health meet pedigree regulations across multiple states — except for narcotics and controlled drugs, which are exempt from unit-level identifiers.
Yes — SBSA integrates Cardinal Health EDI with both QuickBooks Online, via the QBO API for sales orders, invoicing, and payment reconciliation, and QuickBooks Enterprise, via IIF file or SDK-based integration to push POs as sales orders and trigger DSCSA-ready ASN generation from fulfillment data.
Most Cardinal Health EDI implementations with SBSA take 2 to 4 weeks from questionnaire completion to go-live, covering connection setup (AS2, SFTP, or VAN), document mapping, DSCSA field configuration, GS1-128/HDMA labeling, and validation in Cardinal Health's test environment before any live PO is transmitted.
Tell us your supplier type — manufacturer, NLC replenishment, or CSOS controlled substances — and we'll build a complete integration plan with DSCSA penalty protection from day one.