FedEx 3PL as a Source

July 20, 2026

Summary

FedEx 3PL is a plug-and-play source integration that connects a FedEx-operated fulfillment location to Flxpoint. It supports pulling inventory, sending fulfillment requests, and importing shipments with tracking back to your sales channels. Getting shipping method mapping right — matching FedEx 3PL's own shipping codes — is essential for fulfillment requests and tracking to flow through cleanly.

What this integration does

Get Inventory (Primary)

Imports FedEx 3PL's product catalog, quantities, and item attributes from your fulfillment location.

Send Fulfillment Requests

Sends orders (Fulfillment Requests) to FedEx 3PL for pick, pack, and ship.

Get Shipments

Pulls FedEx 3PL shipment confirmations — ship date, SKU, and quantity shipped — back into Flxpoint.

How to connect - credentials you need

FedEx 3PL connects using a Client ID and Client Secret from your FedEx 3PL project, plus an Environment selection (Sandbox or Production). Add a FedEx 3PL source, start configuring an operation, and when Flxpoint prompts you click + New Connection, enter the values, then Test Connection → Save Connection. After saving, you can generate a new refresh token from the connection if one is needed.

Org NameRequired

Your FedEx 3PL organization name, required to connect.

EnvironmentRequired

Set to Sandbox or Production to match your FedEx 3PL project.

Client IDRequired

Found on the Project Overview page inside FedEx 3PL.

Client SecretRequired

Shown when the FedEx 3PL project is created. Regenerate it from the Project Overview page if lost.

After saving the connection, you can generate a new refresh token from the connection screen if one is needed. Make sure the shipping methods you use are mapped to FedEx 3PL's own shipping codes — see Important Notes below — or fulfillment requests and tracking will not flow through cleanly.

Important - read before configuring

Shipping mapping must use FedEx 3PL codes

Send Fulfillment Requests only works when your shipping method mapping matches FedEx 3PL's shipping codes. Mismatched or missing codes are the most common cause of orders failing to go through or shipping under the wrong service.

Client ID and Client Secret come from FedEx

The Client ID is on the Project Overview page inside FedEx. The Client Secret is shown when the project is created; if lost, regenerate it on the same Project Overview page.

Match the environment

The connection must be set to the correct Environment (Sandbox or Production). After saving the connection you can generate a new refresh token if one is needed.

Not every operation is supported

Get Inventory [Primary], Send Fulfillment Requests, and Get Shipments are supported. Get Inventory [Secondary] and Get Source Invoices are not supported.

Operations - fields to know

Get Inventory (Primary)Send Fulfillment RequestsGet Shipments

Field	Maps To — Notes
Item ID	No mapping is available.
Variants (attribute key/value)	→ Product → Attributes. Per-variant attribute pairs added to the product record.
Battery Type / Battery	→ Product Attributes ("Battery Type", "Battery"). Battery handling flags, when FedEx 3PL returns them.
Fragile / Hazard Material / Liquid / Perishable	→ Product Attributes. Handling flags added as named attributes when present on the item.
Shelf Life / Model	→ Product Attributes ("ShelfLife", "Model"). Additional descriptive attributes when present.

Source Field	Maps To (FedEx 3PL) — Notes
Fulfillment Request line → SKU	→ Order Item SKU. Required. Sent to FedEx 3PL per line item.
Fulfillment Request line → Quantity	→ Order Item Ordered Quantity. Required. Units requested.
Order Item ID	No mapping is available.
Shipping address	→ Destination Address. Required. End-customer shipping address sent with the order.
Source Shipping Method	→ FedEx 3PL Shipping Code. Required. Must match a valid FedEx 3PL shipping code — see Important Notes.

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 tracking sync

The tracking number pushes but the carrier field stays empty, so downstream channels that require it (for example Lowe's) error out. Confirm the shipping method is mapped to a carrier value the channel recognizes; an unmapped or non-standard code leaves the carrier field blank.

Orders ship under the wrong service (for example UPS instead of FedEx Ground) or will not go through at all

The shipping method is mapped to the wrong FedEx 3PL shipping code, so fulfillment requests either route to the wrong service or fail. Update the shipping method mapping to the correct FedEx code (for example FedEx Ground) using FedEx's shipping code reference.

Shipment shipped by the source but tracking has not been picked up in Flxpoint

The source confirms a shipment but the tracking does not appear in Flxpoint for a period, leaving the order Open. Confirm Get Shipments is enabled and running on the source; tracking imports on the Get Shipments sync cycle rather than instantly at ship time.

FAQs

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

This happens when the shipping or carrier code coming from the source is not mapped to a value the channel recognizes, so the channel shows a blank carrier or "Other". Map the incoming shipping method to the correct carrier text under Shipping Management so the tracking syncs with a recognized carrier name.

Where do I find the FedEx 3PL shipping codes to map against?▸

FedEx 3PL publishes its shipping codes in FedEx's developer documentation. Your shipping method mapping in Flxpoint needs to line up with those codes — contact your FedEx representative or support@flxpoint.com if you need help locating the current list.

Does FedEx 3PL send back inventory and invoices?▸

Inventory is supported through Get Inventory [Primary]. Get Inventory [Secondary] and Get Source Invoices are not supported, so source invoice data will not import from FedEx 3PL.

Back to 3PL & Fulfillment Centers