McKesson as a Source
Summary
McKesson is a leading medical and healthcare products distributor. The Flxpoint integration uses two connection types: an XML API connection (B2B Key, Identity, Shared Secret, Account Number, Ship To Number) for Get Inventory (Primary and Secondary) via McKesson's XML ItemFeed, and a separate FTP/FTPS EDI connection for Send Fulfillment Requests (EDI 850), Get Shipments (EDI 856), and Get Invoices (EDI 810). Each McKesson Unit of Measure becomes its own variant in Flxpoint, and McKesson typically selects the shipping carrier on your behalf.
McKesson supports two connection types used for different operations — an XML API connection for Get Inventory (Primary and Secondary), and a separate FTP/FTPS EDI connection for Send Fulfillment Requests, Get PO Acknowledgements, Get Shipments, and Get Invoices. Add a McKesson source, start configuring an operation, and when Flxpoint prompts you click + New Connection, enter the values for that operation's connection type, then Test Connection → Save Connection.
support@flxpoint.com for setup help.Five XML credentials required — all must match McKesson's B2B/EDI records exactly
The XML API connection requires: B2B Key, Identity, Shared Secret, Account Number, and Ship To Number — all provided by McKesson's B2B/EDI team. If Test Connection fails, re-enter each value carefully (watch for whitespace), and verify both Account Number and Ship To Number match McKesson's records. Also confirm your account has the correct EDI docs enabled: 846 (Inventory), 850 (PO), 856 (ASN), and optionally 810 (Invoice).
Each McKesson UOM (Unit of Measure) becomes a separate variant — SKU = itemId + units
A single McKesson item can have multiple Units of Measure (EA, PK, CS, BX, etc.). Each UOM imports as a distinct variant in Flxpoint. The recommended variant SKU format is {itemId}-{units} (e.g., 123456-EA). GIS matches inventory against this constructed SKU. Order submission via Send FR requires mapping a valid Unit Measurement Code that McKesson supports for each line item.
McKesson selects the shipping carrier — do not map shipping method unless specifically enabled
In most McKesson EDI setups, you do not send a shipping method or carrier code with orders. McKesson selects "Best Way" based on your account and item rules. Leaving shipping method fields unmapped will not cause order failures. Only map carrier/service codes if McKesson has explicitly enabled and documented this for your account. If unsure, leave shipping method unmapped.
Multiple tracking numbers in EDI 856 are split into separate Flxpoint shipment records
As of October 16, 2025, when an EDI 856 shipment contains comma-separated tracking numbers, Flxpoint automatically splits them into separate shipment records — one tracking number per shipment. This is especially important for Amazon channel orders, which only accept one tracking number per shipment. After a multi-tracking shipment imports, re-sync the order to ensure each tracking number publishes correctly to the channel.
| Field | Maps To — Notes |
|---|---|
| itemId + unit | → Product / Variant → SKU. Required. Constructed as {itemId}-{units} per McKesson UOM — each UOM becomes its own variant. |
| description / itemDescription | → Product → Title. McKesson's item description. |
| itemFeatures | → Product → Description. Extended item features/description text. |
| manufacturerName / itemBrand | → Product → Brand. |
| majorCategory / minorCategory | → Product → Category 1 / Category 2. |
| itemImage + additional images | → Product / Variant → Images. Primary image plus any Image Reference Number attributes; the base image URL depends on your Image Quality Preference setting (High Res / Item Detail / Thumbnail). |
| price | → Pricing → Cost. Per-UOM dealer price. |
| quantityAvailable | → Inventory → Quantity. Per-UOM available quantity. |
| unit (UOM) | → Product / Variant → Option (UOM). Each McKesson Unit of Measure (EA, PK, CS, BX, etc.) becomes a distinct variant option. |
| itemAttributes | → Product → Attributes. Name/value attribute pairs returned by McKesson. |
| Field | Maps To — Notes |
|---|---|
| itemSku ({itemId}-{units}) | → Inventory Variant → SKU. Required. Must match the SKU created by Get Inventory Primary. |
| price | → Pricing → Cost. |
| quantityAvailable | → Inventory → Quantity. |
| Full catalog fields | Not included in Secondary — titles, images, categories and attributes come from Get Inventory Primary. Run Primary daily for the full catalog and Secondary more frequently to keep Cost and Quantity current. |
| Source Field | Maps To (McKesson EDI 850) — Notes |
|---|---|
| Fulfillment Request # | → Patient Account Number. Required. Must be unique per order — reusing a PO number causes a Duplicate PO rejection from McKesson. |
| Fulfillment Request line → SKU | → Buyer's Item Number (IN). Required. Sent per line item. |
| Fulfillment Request line → Quantity | → Quantity. Required. |
| Fulfillment Request line → UOM | → Unit Measurement Code. Required. Must be a UOM McKesson supports for that item (EA, PK, CS, etc.). |
| ShipTo Number | → ShipTo Number. Optional — only if McKesson assigned you a coded ship-to location. Mapping this suppresses sending a full shipping address. |
| Cost | → Cost. Optional line cost. |
| Shipping method | Not typically mapped — McKesson selects the carrier (“Best Way”) based on your account and item rules. Only map if McKesson has explicitly enabled carrier selection for your account. |
| Field | Maps To — Notes |
|---|---|
| TrackingNumber | → Shipment → Tracking Number. Required. Comma-separated tracking numbers on a single 856 are split into separate shipment records (as of Oct 16, 2025). |
| Buyer's Item Number (IN) | → Shipment Item → SKU. Required. |
| quantity | → Shipment Item → Quantity. Required. Units shipped for the line. |
| unitMeasurementCode | → Shipment Item → UOM. Informational — not required for matching. |
| PRF01 (Purchase Order) | → Shipment → Purchase Order reference. Required. |
| Carrier / ship method | McKesson's 856 typically returns tracking number only — carrier and ship method fields are often blank and do not need to be mapped. |
| Field | Maps To — Notes |
|---|---|
| Buyer's Item Number (IN) | → Invoice Item → SKU. Required. Matches the invoice line back to your catalog/FR. |
| quantity | → Invoice Item → Quantity (invoiced). Required. |
| cost | → Invoice Item → Per Unit Cost. Required. |
| unitMeasurementCode | → Invoice Item → UOM. Informational. |
| Summary total (SAC/TDS, cents) | → Invoice → Total Cost. Converted from cents to dollars. |
| Line item charges (SAC) | → Invoice → Additional Invoice Items. Freight/tax/other charge lines added as separate invoice items (title = charge description, cost = charge amount). |
YYYYMMDD-####). Set up a mapping template rule to always output a unique value per order submission. Do not retry a failed FR using the same FR number as the original failed submission.