Flxpoint Help Center
All DocsContact support

AmerisourceBergen EDI as a Source

July 17, 2026

Summary

AmerisourceBergen — now rebranded to Cencora — is a pharmaceutical distributor connected via direct EDI over SFTP. 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 Cencora 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.

Get Inventory (Primary)
Imports Cencora's pharmaceutical catalog and pricing via EDI 832.
Send Fulfillment Requests
Sends purchase orders to Cencora via EDI 850.
Get Acknowledgements
Reads Cencora's EDI 855 acceptance, backorder, or substitution status.
Get Invoices
Imports Cencora invoices via EDI 810 for reconciliation.
Get Shipments
Pulls Cencora tracking and ship data via EDI 856.

AmerisourceBergen (now Cencora) requires a coordinated EDI trading-partner setup before any files can be exchanged. Contact your Flxpoint account manager to begin — Flxpoint will work with Cencora to provision the connection and complete a UAT testing phase. Once Cencora confirms your account is live in production, add an AmerisourceBergen source, enter the SFTP and trading-partner details Cencora provided, then Test ConnectionSave Connection.

SFTP Connection — provisioned by Cencora
HostRequired
The Cencora SFTP server hostname. Provided by Cencora once your trading partner account is provisioned — do not configure this until you receive Cencora's go-live confirmation.
PortRequired
The SFTP port Cencora provides for the connection.
UserRequired
Your Cencora SFTP username, issued during trading partner setup.
PasswordRequired
Your Cencora SFTP password (or key-based credential), issued during trading partner setup.
Inbound Remote FolderOptional
The remote folder Cencora delivers 832/855/810/856 files to. Confirm the path with Cencora's EDI team during setup.
Outbound Remote FolderOptional
The remote folder Flxpoint writes outbound 850 purchase orders to. Confirm the path with Cencora's EDI team during setup.
EDI Trading Partner Settings (ISA/GS identifiers)
Our QualifierRequired
Flxpoint's ISA/GS qualifier used in the EDI envelope with Cencora.
Our IDRequired
Flxpoint's ISA/GS ID with Cencora — formatted as FLX[accountID]. Provide this to Cencora when initiating trading partner setup.
Their QualifierRequired
Cencora's ISA/GS qualifier, confirmed in Cencora's go-live email.
Their IDRequired
Cencora's ISA/GS trading-partner ID (their EDI account identifier), confirmed in Cencora's go-live email.
Buyer IDRequired
Your buyer identifier sent on outbound 850 purchase orders, as assigned by Cencora during setup.
Cencora requires a formal UAT/testing phase before any new trading partner goes live — do not submit live purchase orders until you receive Cencora's go-live confirmation (account number, ISA/GS ID, and enabled transaction sets). For EDI setup, go-live, and file-transmission issues, your Flxpoint account manager can put you in touch with Cencora's EDI support team (including their 24/7 afterhours line) and their Pharmacy Data Services (pricing/catalog) team. For extended operation setup and field mapping beyond connection, contact support@flxpoint.com.

AmerisourceBergen is now Cencora — EDI support contacts have changed

AmerisourceBergen rebranded to Cencora. For EDI setup and go-live support, contact Cencora's EDI support team. For afterhours EDI issues, Cencora offers a 24/7 EDI support line. For pricing files and catalog questions, contact Cencora's Pharmacy Data Services (PDS) team. Your Flxpoint account manager has these contact details on file. Provide Flxpoint's ISA/GS identifier (FLX[accountID]) when initiating the trading partner setup with Cencora's team.

EDI files are exchanged over SFTP — not Flxpoint's FTP

Unlike some other EDI integrations, AmerisourceBergen uses SFTP as the file exchange method. Cencora's EDI team configures the SFTP connection on their end when they provision your trading partner account. Your Flxpoint account manager will coordinate the SFTP credentials and connection path during setup. Do not attempt to configure this manually before Cencora has completed provisioning on their side.

A formal UAT process with Cencora is required before going live

Cencora requires a testing phase before activating any new EDI trading partner. They will open a tracked testing ticket on their end and confirm when your account is live in their production environment. You will receive a go-live confirmation email from Cencora's EDI team with your account number, ISA/GS ID, and the transaction sets enabled. Do not submit live purchase orders until you receive this confirmation.

Inventory quantities must be set manually — the 832 file does not include real-time stock levels

The 832 EDI file from AmerisourceBergen contains price and catalog data only — not real-time warehouse quantities. After products are imported via Get Inventory Primary, you must apply a Pricing and Quantity Rule in Flxpoint to assign a fixed quantity to Cencora SKUs (a common configuration is a fixed quantity of 50 per SKU). Contact support@flxpoint.com if you need help setting this up in bulk across your AmerisourceBergen source inventory.


FieldMaps To — Notes
Vendor Item NumberProduct / Variant → SKU. Required. Primary identifier parsed from the 832 catalog file.
Drug / Product NameProduct → Title.
Long DescriptionProduct → Description. Free-form descriptive text from the catalog file.
ManufacturerProduct → Manufacturer / Brand.
Dosage Form / Strength / Package SizeProduct / Variant → Attributes. Pharmaceutical-specific attributes (dosage form, strength, pack size).
Vendor Item Number / Manufacturer Part Number / Vendor Catalog Number / UPC / HIBC BarcodeVariant → Identifiers. Additional item identifiers Cencora returns alongside the NDC.
Cost PricePricing → Cost. Cencora's contract/purchase cost. AWP, List, MSRP, Retail and Wholesale reference prices are also available to map.
QuantityNot included in the 832 file. Set a fixed-quantity Pricing and Quantity Rule scoped to this source (see Important Notes) — do not leave unmapped.
Source FieldMaps To (Cencora EDI 850) — Notes
Fulfillment Request #PO Number. Required. Must be unique per submission.
Fulfillment Request line → SKUVendor's Item Number. Required. Sent per line item.
Fulfillment Request line → QuantityQuantity. Required.
Unit of MeasureUnit Measurement Code. Must be a UOM Cencora supports for that NDC.
Buyer IDBuyer ID. Identifies your account to Cencora — typically a fixed value set during trading-partner setup, not mapped per order.
FieldMaps To (Cencora EDI 855) — Notes
Acceptance CodeAcknowledgement Status. Accepted, Backordered, Not Available, Rejected, On Hold, or Accepted with Substitution.
Acknowledged QuantityAcknowledgement Item → Quantity.
Substitute SKU (sent when Cencora accepts with substitution)Fulfillment Request Item attribute. Saved automatically so Get Shipments and Get Invoices match the substituted item instead of the original NDC.
FieldMaps To — Notes
NDC Number (or substitute SKU, if applicable)Invoice Item → SKU. Required.
Quantity InvoicedInvoice Item → Quantity. Required.
Unit PriceInvoice Item → Per Unit Cost. Required.
Product DescriptionInvoice Item → Title. Optional.
Invoice TotalInvoice → Total Cost. Converted from cents to dollars.
Line Item Charges (freight, allowances)Invoice → Additional Invoice Items. Added as separate lines; allowances are recorded as negative amounts.
FieldMaps To — Notes
NDC Number (or substitute SKU, if applicable)Shipment Item → SKU. Required.
Quantity ShippedShipment Item → Quantity. Required.
Tracking NumberShipment → Tracking Number. Required. Falls back to Cencora's shipment ID if no tracking number is present.
Purchase Order NumberShipment → Purchase Order reference. Required.
Lot Number / Lot Expiration DateShipment Item → Lot info. Optional — useful for pharmaceutical lot tracking/recalls.
CarrierShipment → Carrier. Optional carrier code returned by Cencora.

Get Inventory Primary not importing products — 832 file not processing
First confirm the go-live email was received from Cencora's EDI team and that your account is active in their production environment — catalog files will not be delivered until the trading partner is fully provisioned. If you have received the go-live confirmation but files are still not processing, contact Cencora's Pharmacy Data Services team (your Flxpoint account manager has this contact) to confirm the 832 file is being transmitted on schedule. Also raise a ticket with support@flxpoint.com including your Cencora account number and ISA/GS ID so the SFTP path and schedule can be verified.
Products imported but showing zero or no quantity available
This is expected behavior — the 832 file contains price and catalog data but no real-time stock quantities. Products import with zero or null quantity until a quantity rule is applied in Flxpoint. Set up a Pricing and Quantity Rule scoped to the AmerisourceBergen source to assign a fixed quantity (for example, 50) to all SKUs. This rule needs to be configured once after initial catalog import and will apply to all future 832 updates. Contact support@flxpoint.com for help configuring this in bulk.
Send Fulfillment Requests failing — orders not reaching Cencora
Confirm the integration is pointing to Cencora's production environment — this should only happen after their team has issued the go-live confirmation. If orders are failing in production, check the Send Fulfillment Requests job logs for the specific EDI error. For EDI transmission issues, contact Cencora's EDI support team (or their 24/7 afterhours line for issues outside business hours — your Flxpoint account manager has these contacts). Provide them with your ISA/GS identifier and the transaction date — they can look up the EDI transmission log on their end to identify where the 850 is failing.
No 855 acknowledgment received after submitting a purchase order
If a 850 purchase order was sent but the 855 acknowledgment has not been received after a reasonable window (typically a few hours for production), first confirm the 850 was successfully transmitted by checking Send Fulfillment Requests logs in Flxpoint. If the transmission was successful, contact Cencora's EDI support team with your ISA/GS ID and order reference — they can confirm whether the 850 was received and why an 855 was not generated. Missing acknowledgments can also indicate an SFTP path misconfiguration on Cencora's side during initial setup.

What EDI transaction sets does the AmerisourceBergen integration support?
The integration supports five EDI transaction sets: 832 (Price/Sales Catalog — drives Get Inventory Primary to import product and pricing data from Cencora), 850 (Purchase Order — Send Fulfillment Requests submits orders to Cencora), 855 (Purchase Order Acknowledgment — Get Acknowledgements confirms orders were received), 810 (Invoice — Get Invoices retrieves billing data), and 856 (Ship Notice/Manifest — Get Shipments retrieves tracking and shipment data). All five are exchanged over SFTP.
How do I start the setup process for AmerisourceBergen EDI?
Contact your Flxpoint account manager to start the process. Flxpoint will coordinate with Cencora's EDI team to establish the trading partner relationship using Flxpoint's ISA/GS identifier (FLX[accountID]) and your Cencora account number. Cencora will open a testing ticket on their side and configure the SFTP connection. Once their team confirms the trading partner is live in production — which includes a go-live email listing your account number, ISA/GS ID, and enabled transaction sets — Flxpoint will complete the source configuration in your account.
How do I set inventory quantities for AmerisourceBergen products in bulk?
Since the 832 catalog file does not include real-time stock quantities, you need to apply a fixed quantity rule in Flxpoint scoped to the AmerisourceBergen source. This is typically configured as a Pricing and Quantity Rule that sets a constant quantity (for example, 50) on all SKUs from this source. Contact support@flxpoint.com to configure this in bulk if you have a large catalog — do not attempt to update quantities manually SKU by SKU. The same rule pattern applies to Kinray EDI if you also use that integration.
What is the difference between AmerisourceBergen EDI and Kinray EDI in Flxpoint?
Both integrations support the same five EDI transaction sets (832, 850, 855, 810, 856) and require a distributor-side trading partner setup before going live. The key technical difference is the file exchange method: AmerisourceBergen uses SFTP, while Kinray uses Flxpoint's own hosted FTP server. Both require manual quantity rules since neither 832 file carries real-time stock levels. If you are a pharmacy operator using both distributors, each requires its own separate source configuration in Flxpoint.
© 2026 Flxpoint. All rights reserved.