Updated November 2026
API errors: why an order did not import
Fulfillment clientsAn API error means an order came in from your store with something the system cannot use, so it cannot ship until it is fixed. Errors show in a box at the top of the Orders tab; check it daily until your set-up is settled.
The four causes
- Unmapped shipping method. Your store sent a shipping option that is not mapped to a carrier service. Map it once under Orders, then Integrations, then ShipMethod Translator, and the order releases. Map "*" to a default service so new options never fail.
- Missing or unmapped SKU or bundle. The store sent a SKU that does not exist in the portal, or a product with a blank SKU. Create the SKU (or the set) with the exact same code, or correct it in your store.
- Missing ship-to information. Usually a manual order in your store without a full address. Add the address and the order moves to Pending.
- Duplicate order number. A second order with the same number does not import at all. Give each store a suffix so numbers never collide.
Products we do not ship
Digital goods, consultations, or items you ship yourself should be set as virtual SKUs. The system drops them from the order and ships the rest instead of erroring.
Fixing an error
Open the error, correct the field, and save; the order moves to Pending. Or open a support request and we clear it for you.
Prevention
Create SKUs and sets before you list products, map every shipping option, and train staff to complete addresses on manual orders.
Was this article helpful?