Overview
Linnworks is transitioning from the FedEx Web Services integration to a new integration built on the FedEx REST API. This move reflects FedEx's own strategic direction - FedEx Web Services is a legacy platform, and FedEx REST API is their modern, actively developed platform going forward.
The new integration brings improved reliability, access to new FedEx features, and long-term support. However, it does introduce some changes to how certain shipping options are configured. This document answers the most common questions about the migration and highlights the key differences you need to be aware of.
Frequently Asked Questions
1. Why is this change happening?
FedEx Web Services is a legacy platform that FedEx is actively winding down. The FedEx REST API is their current, modern platform and will continue to receive new features and improvements. Migrating to the REST API integration ensures Linnworks customers retain full, uninterrupted access to FedEx shipping services and can take advantage of new FedEx capabilities as they are released.
2. When will the new integration be ready?
We are currently finalising our verification process with the FedEx team. Once this is complete, the new integration will be published and available to all customers. We will communicate the release date as soon as it is confirmed. A link to the full setup documentation can be found here.
3. What action will I need to take?
Once the new integration is available, you will need to complete the following steps:
- Add the new FedEx REST API integration in Linnworks.
- Complete authentication using your FedEx PIN or Invoice details.
- Recreate or move your shipping services from the old integration to the new one.
- Review the significant changes section below, as some options are configured differently in the new integration.
A full step-by-step migration guide can be found here.
4. What will happen to the existing FedEx Web Services integration?
The existing FedEx Web Services integration will continue to function until 30 April 2026. After this date, the integration will stop working. Once all customers have migrated to the new integration, the old integration will be permanently removed from Linnworks.
5. Will my existing services and settings transfer automatically?
No, your services, configurations, and item and order-level shipping properties will need to be set up again in the new integration. This is because the REST API integration is a new connection with a different authentication model. We recommend migrating and testing the new integration alongside the existing one before the deadline, so you can verify everything is working before the cutover.
6. What if I don’t migrate before the deadline?
If you have not migrated by 30 April 2026, your FedEx shipping through Linnworks will stop working as the legacy integration will no longer function. To avoid any disruption to your fulfilment, we strongly recommend migrating well before the deadline.
7. Who should I contact if I need help migrating?
If you encounter any issues during migration, please contact the Linnworks Support team. You can also refer to the migration checklist available here.
Significant Changes to Be Aware Of
The following features work differently in the new integration. Please review each one before completing your migration.
| Feature | How it worked previously | How it works in (New) FedEx |
|---|---|---|
FedEx One Rate® | Available as a tick-box option on individual service configurations. | FedEx One Rate is offered as a separate, dedicated service within the integration, with its own configuration. You will need to add and configure it as a new service rather than enabling a toggle on an existing one. |
| FedEx® Delivery Signature Options | Signature options were applied per-order using Order Extended Properties. | Signature options are configured at the service level in the integration settings. If you require different signature options for different shipment types, you will need to set up separate services for each. |
| Shipping Lithium Batteries (Non-Hazardous) | Not supported | Battery declarations are now specified using item-level properties: BatteryType, BatteryIsContained, and BatteryComplianceSection. These must be configured on each relevant product before shipping. Full setup guide available here. |
| Shipping Alcohol | Item-level properties: Alcohol Order-level properties: AlcoholRecipientType | Alcohol shipments require two item-level properties to be set: ProductGoodsType (set to ALCOHOL) and AlcoholLicenseeType (set to CONSUMER or LICENSEE). A FedEx Alcohol Shipping Agreement must also be active on your FedEx account. Full setup guide available here. |
| Dangerous Goods (DG) Shipments | Item and order-level properties as specified in this article. | FedEx has introduced an updated flow for processing Dangerous Goods shipments in the REST API. This functionality is not yet implemented in the new Linnworks integration. Support for the new DG flow will be added in a future update. If your business regularly ships Dangerous Goods via FedEx, please contact Linnworks Support to discuss your options ahead of the migration deadline. |
Last updated: March 2026 • For support, contact the Linnworks team • Full documentation available here