FedEx integration for WMS-driven express shipping
FedEx connects to myFulfillment so your warehouse prints express labels straight from the packing station, through the FedEx Developer Portal REST APIs. Orders flow in from your stores and marketplaces, the operator runs the barcode check, and the tracking number returns to the channel. Built for merchants shipping domestic and cross-border parcels from one preparation flow.
Carrier label
FedExFedEx1,2KG
- Boostmyshop product
- myFulfillment
- Category
- Carriers
- Connects
- The FedEx express network, more than 220 countries and territories served (2026)
- Account required
- FedEx account (Developer Portal API credentials)
- Integration cost
- Included in myFulfillment · TMS module
- Sync frequency
- ≈ 5 min
- Data direction
- Two-way (inbound and outbound)
- Developed by
- Boostmyshop (native integration)
- Support by
- Boostmyshop
- Sovereignty
- American (United States)
- Vendor
- FedEx
- Last updated
- 2026-07-18
How FedEx fits with myFulfillment
What is FedEx?
FedEx is a global express carrier: more than 220 countries and territories served, with its own air network. E-commerce integrations run through the FedEx Developer Portal REST APIs: Ship, Track, Rates and Transit Times, and Locations. myFulfillment adds the layer FedEx does not provide: the OMS and WMS that orchestrate orders, guide picking and packing, and hand the parcel to FedEx at the right moment. Not to be confused with FedEx Fulfillment, FedEx's own 3PL service: here your warehouse prepares, myFulfillment runs the operation, FedEx carries the parcel.
Orders, stock, picking and barcode-checked packing.
Applies your carrier rule and prints the FedEx label at packing.
Home or pickup-point delivery, tracking sent back to the sales channel.
FedEx with any sales channel
Orders from any store or marketplace that feeds myFulfillment flow into the OMS; preparation is orchestrated, the FedEx label prints through the Ship API and the tracking number flows back to the channel to trigger the delivery notification. Browse the FedEx combinations by channel below: Shopify, BigCommerce, WooCommerce, PrestaShop and more.
myFulfillment runs the picking, FedEx prints the label
At packing time, myFulfillment generates the FedEx label through the Ship REST API and prints it at the station, thermal (ZPL, EPL2) or laser (PDF, PNG). The operator never opens FedEx Ship Manager.
See the featureThe FedEx tracking number goes back to the store or marketplace as soon as the label prints and triggers the shipping confirmation. The Track API then exposes scan events, estimated delivery and proof of delivery, up to 30 numbers per request.
Outbound: tracking number to the sales channel when the label prints; scan events and proof of delivery through the Track API.
See the featureFedEx runs pickup and drop-off points in France, listed on local.fedex.com. The Locations API searches them by address or coordinates, and shipping to a point is activated through the Ship API's Hold at Location service.
See the featureThe FedEx Ship API covers returns: a return label printed and slipped into the parcel, or emailed to the customer. The myFulfillment returns flow builds on it: reception, checking, stock reintegration.
See the featureThe Rates and Transit Times API returns your FedEx account's negotiated rates, not only list rates, several services in one call. The myFulfillment carrier rule applies your weight, method and customer-group matrix; FedEx Freight quotes are excluded.
See the featureEvery validated, paid order lands from the sales channel in the myFulfillment OMS, address and reserved items included. When the rule picks FedEx, preparation runs through to the Ship API call, from the same screen as picking.
Inbound: validated and paid orders, with address and items, about every 5 minutes.
See the featureAs soon as the FedEx parcel leaves the station, domestic or export, myFulfillment removes the shipped quantities from the available stock and resyncs every connected channel; only availability travels, never the selling price.
Outbound: recalculated availability to the channels, after the parcel leaves.
See the featureIn a tight flow, an already-sold item moves from the receiving dock to the shipping station without put-away: the control scan triggers the Ship call and the FedEx parcel leaves the same day.
See the featureWhat syncs, and when
| Data | When |
|---|---|
| In | |
| Validated and paid order | ≈ every 5 min |
| Address and items (SKU) | when the order is validated |
| Negotiated rates and transit times (Rates API) | on call, during preparation |
| Scan events and proof of delivery (Track API) | on demand, up to 30 numbers per request |
| Out | |
| FedEx label (ZPL, EPL2, PDF or PNG) | at packing, after the barcode check |
| Tracking number | when the label is printed |
When FedEx is enough, and when myFulfillment makes the difference
Our operator's read: FedEx covers global express transport; what makes the difference in the warehouse is the orchestration layer above the label.
- A global express network, for domestic and international shipments
- Documented REST APIs on the Developer Portal: Ship, Track, Rates and Transit Times, Locations
- Your account's negotiated rates returned by the API, several services in one call
- FedEx Ship Manager and per-channel modules stop at the label: no guided preparation, no packing check, no multi-channel tracking write-back
- In a direct integration, the SOAP-to-REST migration stays with the merchant
| Solution | FedEx label printing | Account negotiated rates via the API | Packing check (double scan) | Guided preparation and picking | Multi-channel tracking write-back | Move to the REST APIs (SOAP sunset) | Module or license required |
|---|---|---|---|---|---|---|---|
FedEx via myFulfillmentRecommended | connected channels | Handled by Boostmyshop | myFulfillment TMS module | ||||
FedEx Ship Manager alone | Depends on the account | Not applicable (FedEx tool) | FedEx account | ||||
A per-channel FedEx module | Depends on the module | One channel | Depends on the module vendor | Depends on the vendor |
Comparison based on the official documentation and myFulfillment docs. "Partial" states the limit under the badge; no rating, no sponsored placement.
See the FedEx integration on your operations
How our customers use FedEx day-to-day
Day to day, merchants who connect FedEx to myFulfillment ship from a single screen: the order arrives from the sales channel, the operator runs the barcode check, the carrier rule proposes the FedEx service and the label prints at the packing station.
The parcel for Lyon and the parcel for New York follow the same path: barcode check, label at the station, tracking pushed back. Only the FedEx service changes.
Weight, destination and promised delivery time drive the carrier rule: it proposes the right FedEx service, and the operator confirms during preparation.
A cross-border seller fulfilling from France connects stores and marketplaces to myFulfillment like any other channel; the FedEx label and tracking work the same for every destination.
The return label leaves with the parcel or goes out by email; on reception the return is checked and the stock reintegrated in myFulfillment.
Urgent export orders, a separate carrier portal, addresses re-keyed before every label.
Preparation centralized in myFulfillment, the label printed after the barcode check.
Read the full storyConnect FedEx to your other tools, via myFulfillment
myFulfillment sits in the middle, so FedEx works with any sales channel that feeds it: every order comes in from a channel, leaves with the right FedEx label, and tracking flows back to the customer. A few live pairings below.
Amazon × FedEx
Amazon orders centralised in myFulfillment, the FedEx label printed at packing, valid tracking pushed back to Amazon within its deadline.
Cdiscount × FedEx
Cdiscount orders centralised in myFulfillment, the FedEx label printed at packing, valid tracking pushed back to Cdiscount within its deadline.
Fnac × FedEx
Fnac orders centralised in myFulfillment, the FedEx label printed at packing, valid tracking pushed back to Fnac within its deadline.
Shopify × FedEx
Your Shopify store orders are prepared in myFulfillment, the FedEx label printed at packing, tracking pushed back to the store to notify the customer.
PrestaShop × FedEx
Your PrestaShop store orders are prepared in myFulfillment, the FedEx label printed at packing, tracking pushed back to the store to notify the customer.
WooCommerce × FedEx
Your WooCommerce store orders are prepared in myFulfillment, the FedEx label printed at packing, tracking pushed back to the store to notify the customer.
Connect FedEx to myFulfillment, step by step
- 1Create your API credentials on the FedEx Developer Portal (OAuth) and enter them in myFulfillment.
- 2Map your carrier rules: weight, destination, domestic or international FedEx service.
- 3During preparation, the rule proposes the FedEx service; the operator confirms at the packing station.
- 4myFulfillment prints the label through the Ship API and returns the tracking number to your store.
A FedEx account with API credentials created on the Developer Portal (OAuth) is required. New integrations go through the REST APIs: the SOAP Web Services have been on maintenance-only support since July 1, 2026. myFulfillment drives the preparation, label printing and tracking write-back; FedEx provides the express transport, excluding FedEx Freight.
FedEx: frequently asked questions
Pricing, contract, carriers, Shopify, pickup points, international: answers on the FedEx integration.
Through the myFulfillment TMS module: the Shopify store feeds the OMS, the validated order reaches the preparation station and the FedEx label prints after the barcode check. The same connector covers BigCommerce, PrestaShop, WooCommerce and Magento; the combinations by channel are listed further down the page.
myFulfillment is the OMS and WMS layer: orders land in the OMS, picking and packing are guided in the warehouse, and the FedEx Ship API is called at the packing station. The label prints where the parcel is packed, and the tracking number goes back to the channel.
Yes. FedEx publishes REST APIs on its Developer Portal: Ship for labels, Track for tracking, Rates and Transit Times for pricing and delivery times, Locations for drop-off points. Access requires OAuth credentials created on the portal. myFulfillment consumes these APIs for you, so there is no in-house development to maintain.
Yes. The Rates and Transit Times API returns your FedEx account's negotiated rates, not only list rates, and compares several services in one call. One limit: FedEx Freight quotes are not included.
Yes. A cross-border seller fulfilling from France or elsewhere in Europe connects stores and marketplaces to myFulfillment like any other channel; the FedEx label and tracking work the same for domestic and export parcels. A FedEx account with Developer Portal API credentials is required.
Since July 1, 2026, FedEx Web Services are on maintenance-only support: new integrations go through the Developer Portal REST APIs. With myFulfillment the migration is not your problem: the connector runs on the REST APIs and Boostmyshop maintains it.
The Ship API generates FedEx labels in thermal (ZPL, EPL2) and laser (PDF, PNG) formats. At the packing station, myFulfillment sends the right format to the configured printer, with no file handling by the operator.
The Ship API covers returns two ways: a return label printed and slipped into the parcel, or emailed to the customer. On the warehouse side, the myFulfillment returns flow takes over: reception, checking, stock reintegration.
Yes. As soon as the label prints, the store or marketplace receives the tracking number and the customer gets the shipping confirmation, with no operator action. For customer service, scan events and proof of delivery stay available through the FedEx Track API.
Explore other integrations
FedEx covers shipping. Connect your sales channels and tools too.
FedEx integration for WMS-driven express shipping
See it on your own stack