TracePharma
Integrations / Wholesalers / Cardinal Health — SFTP

Integrations · Drug wholesaler EPCIS

TracePharma + Cardinal Health — SFTP

TracePharma ships an inbound connection preset for Cardinal Health — SFTP. Receive EPCIS, match 3T data, and surface exceptions before inventory—using the transport channel your wholesaler supports.

Preset: cardinal_sftp SFTP

Most dispensers and distributors receive serialized product from cardinal via SFTP. TracePharma onboarding wizard applies this preset. Operators focus on receiving workflows—not connector configuration from scratch.

Inbound interoperability

  • SFTP inbound preset (cardinal_sftp) with partner adapter epcis_12_xml.
  • EPCIS shipment files parsed into scan-first receiving and 3T matching.
  • Exceptions surfaced when serials or transaction data are missing from the file.

Outbound & compliance

  • Not applicable for typical pharmacy receive-only workflows.
  • Distributors may ship downstream EPCIS from the same TracePharma tenant.
  • VRS verification and FDA 3911 from received serial inventory.

Typical cutover steps

  1. 1 Request Cardinal SFTP credentials and confirm EPCIS XML drop schedule.
  2. 2 Share your SFTP host and tenant inbound path from Integrations.
  3. 3 Upload a sample Cardinal shipment file on Receiving before go-live.

Best for

Connection details (tenant provisioning)

Placeholder values are replaced with your tenant ID and connection ID after onboarding.

Cardinal Health — SFTP interoperability FAQ

Do I need a separate wholesaler portal if I use TracePharma?
TracePharma ingests EPCIS and matches transaction data—the accountability record for DSCSA. Many teams keep the wholesaler portal during transition, then rely on TracePharma for serial-level receiving and verification audit trails.

Connect Cardinal Health — SFTP in your tenant

We'll walk through inbound preset setup, test receiving, and ACK monitoring on a profile-tuned demo workspace.

Request a demo