Retirement of FedEx Web Services

This article is intended for uStore customers using FedEx services.

FedEx Web Services are being retired. The SOAP based FedEx Web Services are in development containment and have been replaced with FedEx RESTful APIs. XMPie customers will need to prepare to upgrade to uStore 16.1 or higher, and apply a patch for the FedEx updated APIs. This patch should be available in March 2024.

How do I know if I'm using FedEx in uStore?

  1. Log in to the uStore back office: https://{your server}/ustoreadmin

  2. Click Presets.

  3. Click Delivery Setup.

  4. Click Fedex.

  5. If any accounts are listed, you may be using FedEx for one or more of your uStore storefronts.

  6. Should you need help identifying whether you're using FedEx services, please contact XMPie Support.

What versions of uStore are impacted?

uStore 17.1 requires the FedEx patch.

uStore 17.0 requires the FedEx patch.

uStore 16.1 requires the FedEx patch.

uStore 16.0 and below require uStore upgrade + patch.

If I'm using FedEx services, what steps should I take?

Recommendation: Perform the transition to FedEx projects on your store’s slow hours to avoid new orders from being submitted with old services.

Make sure you read through the entire procedure before performing it.

  1. Create deliveries for all FedEx pending orders.

  2. Install the FedEx patch for uStore in the uStore back office, or contact XMPie Support.

  3. Set up FedEx projects in the FedEx website.

    Retrieve the test keys of each project to be later used in a test account which you will create in uStore.

  4. Set up a FedEx test account in uStore.

    Note that test keys are provided for each FedEx project, together with dedicated test account numbers. Use these test account numbers when creating a test account in uStore.

  5. In uStore back office, go to the store's Setup page > Delivery Services, select the required new delivery services provided by FedEx and disable the old services.

    Supported delivery services:

    • FedEx International Priority Express

    • FedEx International First

    • FedEx International Priority

    • FedEx International Economy

    • FedEx International Ground (for both domestic and international)

    • FedEx Cargo International Premium

    • FedEx First Overnight

    • FedEx Intl Ground Distribution

    • FedEx Ground Home Delivery

    • FedEx Smart Post

    • FedEx Priority Overnight

    • FedEx Standard Overnight

    • FedEx 2 Day

    • FedEx 2 Day AM

    • FedEx Express Saver

    • FedEx Same Day

    • FedEx Same Day City

    To prevent confusion between the old SOAP services and the new REST API services, it is recommended to rename the SOAP services so that they can be distinguished from the new delivery services.

    Important: If you haven't created deliveries for orders pending delivery, as recommended above, and FedEx account has been migrated to use FedEx projects:

    • If the old delivery services have been disabled, a delivery cannot be created for any pending orders set with the old services.

    • If old delivery services are still active, during delivery creation you will have to locate in the receipt the old service selected by the customer and create a new delivery with a corresponding new service.

  6. In Presets > System Setup > Delivery services, you can see in the Description column which of the services are for REST API.

  7. Perform label certification, as required by FedEx.

  8. Set up your FedEx account for production.

    When moving Track and Ship & Rate projects to production, use the same account number for both projects, when prompted to do so.

    This can be done in two ways:

    • Create a new FedEx account in uStore, and then apply it to each store.

      In this way you migrate stores one by one, and do not lose customer selections of delivery services. You can also choose different times of migration for each store. However, this may be a lengthy process.

    • Upgrade the existing FedEx account. This will affect all stores at once.

      All stores are migrated at once, and there is no need to locate which stores use the account. However, if some orders are before the Delivering status, customer selection of delivery service is lost.

      Note: For versions lower than 17.2, if you're upgrading your old accounts to REST API accounts, you'll need to take the stores offline and then place them back online.  

What should I do if I'm using an older version of uStore?

uStore 16.0 and below require uStore upgrade and patch.  Open a support case to request an upgrade to the latest version.

What happens with orders that use the old delivery services?

When trying to create a delivery, the system will check if the requested delivery service is still available in the store. If the delivery service is not available (removed from the store or deactivated in Presets), the delivery cannot be created, and the production flow will fail. If the delivery service is active – the system allows replacing the delivery service to one of the newly activated delivery services. In this case you will not be able to see the customer selections of previous delivery services.

How do I contact XMPie Support?

Contact XMPie support via the support portal: https://www.xmpie.com/support or support@xmpie.com to schedule your uStore upgrade.

 

Created by: Clint Cagle ,updated on May 2024