Summary: FedEx changed how it accepts return labels, and an older carrier engine on your site no longer matches. Until it is updated, process the shipment with the station set to Not Linked to get a return label as a PDF you can save and send.
Problem
You create a FedEx email return label, also called a Call Tag, and it fails with this message:
Invalid field value in the enum returnType
The return type shows as PENDING and the return label is never emailed.
Cause
FedEx changed the way it accepts return labels. The FedEx carrier engine installed on your site (the part of Shipstore that talks to FedEx) is an older build and sends a value FedEx no longer accepts, so FedEx turns the request down. The lasting fix is to update that carrier engine, which is work Shipstore does on your site.
Fix
Get a usable label now:
- On the ship page, under Station, choose Not Linked.
- Process the shipment. A new browser tab opens with the label as a PDF. You may have to process it once or twice for the tab to open.
- Save the PDF and email it to the person sending the package back.
Get the emailed return label working again:
- Email support@shipstore.com and ask for the FedEx carrier engine update. Quote the message Invalid field value in the enum returnType so support knows which change is needed. Shipstore schedules and tests the update on your site.
- After the update, create an email return label again and check that it sends.
What you should see
After the update, the email return label is created with no message about returnType. Until then, the Not Linked step gives you a PDF return label you can save and send.
Related articles
- How To: Create a Return Label
- How To: Make a Call Tag
- Reprint goes to the Zebra printer instead of a PDF