Error: "Source field cannot be empty" on API shipments

Summary: An integration (a system that sends orders to Shipstore automatically) can show this error even though a label and tracking number were already made in the same response. Before you resend, check for the label so you do not create and get billed for duplicates.

Problem

A system sending shipments to Shipstore gets this error:

Source field cannot be empty. Shipment processing stopped.

The confusing part is that the response also includes a tracking number and a label, so the shipment partly went through.

Cause

A Shipstore-side problem returned the "Source field cannot be empty" message even though the shipment processed and a label plus tracking number were created. If the sending system treats any error as a full failure and stops, it does not save the label, but the label still exists and can be billed. This has been corrected on our side.

Fix

If you get "Source field cannot be empty. Shipment processing stopped.", look in the same response for a tracking number and a label. A shipment may already have been created.
Do not simply resend, or you may create duplicate labels that get billed.
Email support@shipstore.com with an example request and response so we can confirm the fix is applied to your account.
For any labels created by mistake, void them. UPS generally does not bill unless the package is delivered; for USPS labels, void through the label service or ask your Shipstore support contact.

What you should see

After the fix, the integration processes shipments without the "Source field cannot be empty" message, and one order creates only one label.

Batch error: "No order data returned" from the integration

Knowledge Base