FedEx WMS as a Source

July 20, 2026

Summary

FedEx WMS 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, matching FedEx shipment and tracking data back to your fulfillment requests. Getting shipping method mapping right — so FedEx's shipping/carrier codes match a value your sales channel recognizes — is what keeps carrier name and tracking flowing through cleanly.

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 WMS 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 WMS source, start configuring Get Shipments, and when Flxpoint prompts you click + New Connection, enter the values, then Test Connection → Save Connection.

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. 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

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

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 WMS Integrations