FedEx Freight (LTL, meaning less-than-truckload freight) stops returning rates while other carriers still rate. This is a FedEx response-format change that Shipstore fixes with a carrier-engine update. Report it to support; it rates again after the update.

Problem

FedEx Freight does not return a rate in the rate shop while other carriers rate normally. The log shows:

Could not deserialize the response body stream as FX.V2.RatchResponseVO_LTL. Status 200 Response

Right after a carrier update is applied you may also briefly see:

Plugin loader: No suitable carrier plugin could be found for engine code FX after all checks

Cause

FedEx changed the format of the freight rate reply, and Shipstore's FedEx engine needs an update to read the new format. This is not a customer setting problem. The "No suitable carrier plugin ... engine code FX" message is a separate, short-lived symptom that can appear right after a carrier update is deployed, until the site re-syncs.

Fix

  1. Confirm the pattern: only FedEx Freight fails while other carriers rate, and the log shows the FX.V2.RatchResponseVO_LTL deserialize message.
  2. Email support@shipstore.com to report it. Include the error text and a sample shipment. The fix is a FedEx carrier-engine update made on the Shipstore side.
  3. After support confirms the update, process the shipment again and check that FedEx Freight returns in the rate shop.
  4. If you see "No suitable carrier plugin ... engine code FX" right after a carrier update, process the shipment again. If it keeps happening, email support to ask for a site re-sync.

What you should see

FedEx Freight returns a rate in the rate shop with no deserialize message after the update is applied.

Related articles

  • Shipping stops at random times across carriers, then works after a restart
  • FedEx: We are unable to process this request. Please try again later