Kinray EDI as a Source

July 17, 2026

Summary

Kinray (a Cardinal Health pharmaceutical distribution subsidiary) connects via direct EDI over Flxpoint's hosted FTP infrastructure. The integration covers the full distribution workflow: Get Inventory Primary (EDI 832 catalog/pricing), Send Fulfillment Requests (EDI 850 purchase orders), Get Acknowledgements (EDI 855), Get Invoices (EDI 810), and Get Shipments (EDI 856). Setup requires Cardinal Health to provision a trading-partner relationship and complete a UAT testing phase before any files can be exchanged, and inventory quantities must be set with a fixed Pricing and Quantity Rule since the 832 file carries no real-time stock levels.

What this integration does

Get Inventory (Primary)

Imports Kinray's pharmaceutical catalog and pricing via EDI 832.

Send Fulfillment Requests

Sends purchase orders to Kinray via EDI 850.

Get Acknowledgements

Reads Kinray's EDI 855 acceptance, backorder, or substitution status.

Get Invoices

Imports Kinray invoices via EDI 810 for reconciliation.

Get Shipments

Pulls Kinray tracking and ship data via EDI 856.

How to connect: credentials you need

Kinray runs through Cardinal Health's EDI infrastructure and requires a coordinated trading-partner setup before any files can be exchanged. Contact your Flxpoint account manager to begin: Flxpoint will configure your dedicated FTP connection and work with Cardinal Health to complete a UAT testing phase, including a test 832 catalog load. Once Cardinal Health confirms your account is live in production, Flxpoint Support finalizes the Kinray source configuration in your account.

Flxpoint FTP Connection: configured by Flxpoint Support

Field	What to enter
Pre-Configured FTP ConnectionAutomatic	Flxpoint hosts the FTP endpoint that exchanges EDI files with Cardinal Health on your behalf, with a dedicated account-specific username. Flxpoint Support configures this connection during setup: you do not enter a host, port, username, or password yourself.

EDI Trading Partner Settings (ISA/GS identifiers)

Field	What to enter
Our QualifierRequired	Flxpoint's ISA/GS qualifier used in the EDI envelope with Cardinal Health.
Our IDRequired	Flxpoint's ISA/GS ID with Cardinal Health, confirmed during trading partner setup.
Their QualifierRequired	Cardinal Health's ISA/GS qualifier, confirmed in Cardinal Health's go-live communication.
Their IDRequired	Cardinal Health's ISA/GS trading-partner ID (their EDI account identifier), confirmed in Cardinal Health's go-live communication.
Cardinal Account NumberRequired	Your Cardinal Health SAP account/store number, sent on outbound purchase orders to identify your account to Cardinal Health.
Inbound Remote FolderOptional	The remote folder Cardinal Health delivers 832/855/810/856 files to. Confirm the path with Cardinal Health's EDI team during setup.
Outbound Remote FolderOptional	The remote folder Flxpoint writes outbound 850 purchase orders to. Confirm the path with Cardinal Health's EDI team during setup.

Cardinal Health requires a formal UAT/testing phase before any new trading partner goes live: remember to cancel test Purchase Orders by phone once acknowledged (see Important Notes). For EDI setup, go-live, and file-transmission issues, your Flxpoint account manager can put you in touch with Cardinal Health's EDI support team. For extended operation setup and field mapping beyond connection, contact support@flxpoint.com.

Important: read before configuring

Setup requires coordination with Cardinal Health EDI support before connecting

Kinray EDI runs through Cardinal Health's EDI infrastructure. Before Flxpoint can exchange files, Cardinal Health must configure the EDI trading partner relationship on their end. Contact Cardinal Health EDI support to initiate setup: they will load a test 832 catalog file to your account for UAT. Flxpoint support will configure the Kinray EDI source in your account once the trading partner relationship is active.

EDI files are exchanged over Flxpoint's FTP, not Kinray's FTP

Unlike many source integrations, Kinray EDI uses Flxpoint's own FTP infrastructure as the exchange point, with a dedicated account-specific username Flxpoint assigns during setup. Cardinal Health pushes EDI files to this Flxpoint-hosted location, and Flxpoint reads them on your scheduled integration runs. Do not attempt to configure a direct connection to Kinray's or Cardinal Health's FTP servers.

Test POs must be cancelled by phone after acknowledgment is received

During UAT, Cardinal Health loads a test catalog for a limited time. When you send a test Purchase Order (EDI 850) and receive the acknowledgment (EDI 855), you must call Cardinal Health Customer Service at 800-334-5529 to cancel the test PO: they do not cancel automatically. Failing to cancel test POs can result in unwanted orders being processed against your account.

Inventory quantities must be set manually: Kinray does not send real-time stock levels

The 832 EDI file from Kinray contains price and catalog data but not real-time warehouse inventory quantities. After products are imported via Get Inventory Primary, you will need to set quantity rules manually in Flxpoint (for example, a fixed quantity of 50 per SKU, similar to AmerisourceBergen configurations). Consult your Flxpoint account manager about the recommended quantity setup approach for your pharmacy workflow.

Operations: fields to know

Get Inventory (Primary)Send Fulfillment RequestsGet AcknowledgementsGet InvoicesGet Shipments

Imports Kinray's pharmaceutical catalog and pricing via EDI 832.

Field	Maps To: Notes
Vendor Catalog Number	→ Product / Variant → SKU. Required. Primary identifier parsed from the 832 catalog file.
Drug / Product Name	→ Product → Title.
Long Description	→ Product → Description. Concatenated free-form descriptive text from the catalog file.
Manufacturer	→ Product → Manufacturer / Brand.
Category (OTC / RX) & Product Type	→ Product → Attributes. Drug category and distribution/product type codes returned by Kinray.
UPC Number / Vendor Catalog Number	→ Variant → Identifiers. Additional item identifiers Kinray returns alongside the NDC.
Pack Quantity / Units Per Pack / Unit of Measure	→ Variant → Packaging. Case pack and unit-of-measure details from the catalog file.
Cost Price	→ Pricing → Cost. Kinray's contract/purchase cost. MSRP is also available to map.
Quantity	Not included in the 832 file. Set a fixed-quantity Pricing and Quantity Rule scoped to this source (see Important Notes): do not leave unmapped.

Sends purchase orders to Kinray via EDI 850.

Source Field	Maps To (Kinray EDI 850): Notes
Fulfillment Request #	→ PO Number. Required. Sent in the BEG segment; must be unique per submission.
Fulfillment Request line → SKU (Vendor Catalog Number preferred, falls back to NDC)	→ Item Identifier. Required. Sent per line item: Kinray's writer prefers Vendor Catalog Number when both are mapped.
Fulfillment Request line → Quantity	→ Quantity. Required. Sent per line item.
Cardinal Account Number	→ Ship-To identifier. Configured once in connection settings (not per-order): identifies your account to Cardinal Health.

Reads Kinray's EDI 855 acceptance, backorder, or substitution status.

Field	Maps To (Kinray EDI 855): Notes
Acceptance Code	→ Acknowledgement Status. Accepted, Accepted with Substitution, Quantity Changed, Rejected, or Forwarded to Alternate Supplier.
Acknowledged Quantity	→ Acknowledgement Item → Quantity.
Substitute Item Identifier (sent when Kinray accepts with substitution)	→ Fulfillment Request Item attribute. Saved automatically so Get Shipments and Get Invoices match the substituted item instead of the original NDC.

Imports Kinray invoices via EDI 810 for reconciliation.

Field	Maps To: Notes
UPC Number (or substitute item, if applicable)	→ Invoice Item → SKU. Required. Kinray's primary invoice identifier.
Quantity Invoiced	→ Invoice Item → Quantity. Required.
Unit Price	→ Invoice Item → Per Unit Cost. Required.
Product Description	→ Invoice Item → Title. Optional.
Invoice Total	→ Invoice → Total Cost. Converted from cents to dollars.
Line Item Charges (freight, allowances)	→ Invoice → Additional Invoice Items. Added as separate lines at summary level; allowances are recorded as negative amounts.

Pulls Kinray tracking and ship data via EDI 856.

Field	Maps To: Notes
UPC Number (or substitute item, if applicable)	→ Shipment Item → SKU. Required. Kinray's primary shipment identifier.
Quantity Shipped	→ Shipment Item → Quantity. Required.
Shipment ID	→ Shipment → Tracking Number. Required. Kinray does not return a separate carrier tracking number: the shipment/delivery ID is used.
Purchase Order Number	→ Shipment → Purchase Order reference. Required.
Lot Number / Lot Expiration Date	→ Shipment Item → Lot info. Optional: useful for pharmaceutical lot tracking/recalls.
Ship-To Name / Ship-To Code	→ Shipment → Ship-To details. Optional facility identifiers returned by Kinray.

Common issues

832 file not syncing: Get Inventory Primary not importing products

This was a known integration bug that has been resolved. If Get Inventory Primary is not picking up the 832 file from Kinray, first confirm the file is present on Flxpoint's FTP under your dedicated account username: Cardinal Health must have successfully delivered it. If the file is present but not processing, raise a support ticket with Flxpoint including your account ID and the date the 832 file was delivered. Also confirm with Cardinal Health EDI support that your trading partner setup is active and that the file was transmitted to the correct FTP path.

997 acknowledgment error: "Not Found CBR Rules" during EDI testing

A 997 functional acknowledgment error with a "Not Found CBR Rules" message indicates Cardinal Health's EDI system could not match the transaction to a configured business rule on their end: typically meaning the trading partner relationship or ISA/GS identifiers are not correctly configured in their system. Contact Cardinal Health EDI support with the specific INC number from the error (format: INC[number]) and provide the full 997 file details. This is a Cardinal Health-side configuration issue, not a Flxpoint issue, and must be resolved by their EDI support team.

Test PO was not cancelled after UAT: order was processed against account

During UAT, test Purchase Orders must be manually cancelled by calling Cardinal Health Customer Service at 800-334-5529 once the 855 acknowledgment has been received. If a test PO was processed against your account, contact Cardinal Health Customer Service directly to request cancellation or reversal of the order. Flxpoint cannot cancel orders once they have been transmitted and acknowledged by Cardinal Health's EDI systems.

Products imported from 832 file but showing zero or no quantity available

This is expected behavior: the 832 file contains price and catalog data but not real-time stock quantities. Products will import with zero or null quantity until a quantity rule is applied. Set up a Pricing and Quantity Rule in Flxpoint scoped to the Kinray source to assign a fixed quantity to all imported SKUs. The value depends on your pharmacy's ordering workflow: a common approach is to set a fixed quantity (e.g., 50) so that products appear as available for routing. Contact Flxpoint support for help configuring this rule in bulk across your Kinray inventory.

Inventory zeroed out after PO cancellation or partial acknowledgment

If a purchase order line is canceled or only partially acknowledged in the EDI 855, Flxpoint can automatically set that item's source quantity to zero to prevent further routing. This status persists through subsequent syncs until you manually reset the quantity. To enable this behavior or configure the associated email notifications for out-of-stock SKUs, contact Flxpoint support to activate the required configuration flag.

Cross Dock PO status not updating to Acknowledged?

This issue typically occurs when the EDI 855 parser fails to extract the SKU due to missing support for specific qualifiers (such as N4 or VN) or incorrect segment parsing. If you see a Failed to save acknowledgement error in your logs, ensure your integration is updated to include ACK07 and ACK08 in identifier parsing. For detailed segment-level mechanics and EDI troubleshooting, please refer to the Flxpoint EDI help center.

Duplicate acknowledgement errors?

If a duplicate 855 acknowledgement is submitted for a Purchase Order that has already been processed, the system will return a save error. This is expected behavior to prevent redundant status updates; verify the current status of the PO in Flxpoint before re-transmitting files.

FAQs

What EDI transaction sets does the Kinray integration support?

The integration supports five EDI transaction sets: 832 (Price/Sales Catalog (used by Get Inventory Primary to import product and pricing data), 850 (Purchase Order) used by Send Fulfillment Requests to submit orders to Kinray), 855 (Purchase Order Acknowledgment (used by Get Acknowledgements to confirm order receipt), 810 (Invoice) used by Get Invoices), and 856 (Ship Notice/Manifest: used by Get Shipments to retrieve tracking). All five are exchanged over Flxpoint's FTP infrastructure.

How do I start the setup process for Kinray EDI?

Contact your Flxpoint account manager to initiate the integration. Flxpoint will configure the Kinray EDI source in your account, including your dedicated FTP credentials on Flxpoint's hosted infrastructure. In parallel, contact Cardinal Health EDI support to set up the trading partner relationship on their end: they will need to configure your account to send and receive EDI files via Flxpoint's FTP. Once the trading partner setup is complete, Cardinal Health will upload a test 832 catalog file and you can begin UAT.

How do I set inventory quantities for Kinray products in bulk?

Since the 832 file does not contain real-time stock quantities, you will need to apply a fixed quantity rule across your Kinray source inventory in Flxpoint. This is typically done using a Pricing and Quantity Rule scoped to the Kinray source: set a fixed quantity value (e.g., 50) that applies to all SKUs. If you are already using AmerisourceBergen, the same rule pattern applies. Contact Flxpoint support to configure this for your account if you need assistance setting it up in bulk.

Is Kinray EDI similar to the AmerisourceBergen integration?

Yes: Kinray EDI and AmerisourceBergen both use direct EDI over Flxpoint's FTP infrastructure, support the same EDI transaction sets (832, 850, 855, 810, 856), and require the same manual quantity setup approach since neither provides real-time stock levels in their catalog files. The key difference is that Kinray is a Cardinal Health subsidiary serving independent pharmacies, while AmerisourceBergen serves a broader healthcare distribution network. Configuration patterns and quantity rules you have already set up for AmerisourceBergen can serve as a direct reference for Kinray.

Back to General Supplier Integrations