FedEx as a Source

July 20, 2026

Summary

FedEx connects as a shipment-tracking source using a Client API Key, Client Secret Key and an Environment selection (Sandbox or Production). Its only supported operation is Get Shipments, which matches FedEx shipment and tracking data back to your fulfillment requests. Two things decide whether it works: putting your Flxpoint Fulfillment Request # in the FedEx Purchase Orders or Customer Reference field on the shipment, and mapping your shipping methods to FedEx shipping codes your sales channel recognizes.

What this integration does

Get Shipments

Pulls FedEx shipment and tracking data back into Flxpoint for existing fulfillment requests.

How to connect: credentials you need

FedEx connects using a Client API Key and Client Secret Key from your FedEx developer project, plus an Environment selection (Sandbox or Production). Add a FedEx source, start configuring Get Shipments, and when Flxpoint prompts you click + New Connection, enter the values, then Test Connection → Save Connection.

Field	What to enter
EnvironmentRequired	Set to Sandbox or Production. A mismatch will fail authentication.
Client API KeyRequired	From your FedEx developer project.
Client Secret KeyRequired	Shown at project creation; regenerate it from the Project Overview page in FedEx if lost.

Get Shipments is the only supported operation for this connection: it does not import inventory or send fulfillment requests. In step 2 of the configuration, pick which FedEx reference field (Purchase Orders or Customer Reference) carries your Flxpoint Fulfillment Request #. Also make sure your shipping methods are mapped to FedEx's shipping/carrier codes so carrier name and tracking sync correctly to your sales channel.

Important: read before configuring

Put the Fulfillment Request # on the FedEx shipment

Shipments are matched back to Flxpoint through a FedEx reference field. When you create the shipment in FedEx, enter your Flxpoint Fulfillment Request # in the FedEx Purchase Orders or Customer Reference field, then select that same field in step 2 of the Flxpoint configuration. Without it Flxpoint has nothing to match the shipment against and the tracking never lands on the order.

Match the Environment

Set the connection to the correct Environment (Sandbox or Production). A mismatch will fail authentication.

Client API Key and Secret come from FedEx

Both the Client API Key and Client Secret Key come from your FedEx developer project. The secret is shown at creation and can be regenerated on the Project Overview page.

Shipping code mapping matters

FedEx fulfillment and tracking depend on shipping method mapping matching FedEx's shipping codes. Mismatches cause blank carrier or wrong-service issues on the sales channel.

Operations: fields to know

Get Shipments

Pulls FedEx shipment and tracking data back into Flxpoint for existing fulfillment requests.

Field mapping for this operation is configured with Flxpoint Support.

Common issues

Carrier name is blank in the Edit Tracking screen and the channel rejects the sync

The tracking number pushes but the carrier field stays empty, so channels that require it error out. Ensure the shipping method is mapped to a carrier value the channel recognizes.

Orders ship under the wrong service (for example UPS instead of FedEx Ground)

The shipping method is mapped to the wrong FedEx shipping code. Update the mapping to the correct FedEx service using FedEx's shipping code list.

FAQs

Why is the carrier name blank or set to "Other" on my sales channel even though tracking is present?

The FedEx carrier or service code is not mapped to a value the channel recognizes. Map it under Shipping Management so tracking syncs with a recognized carrier name.

Back to Carriers & Shipping Services