You shipped an order from your own system (a warehouse tool, ERP or custom integration), but it is still Pending in Zentail. Zentail marks an order Shipped only when it has recorded a package with a tracking number for it. This article covers the three ways a shipment fails to reach Zentail, and how to fix each.
First, check where the Shipped status came from
A Shipped status on the sales channel (Amazon, eBay, Walmart and so on) does not tell Zentail anything. Zentail keeps the channel's status separately and does not copy the tracking number from it. If the channel says Shipped and Zentail says Pending, Zentail never received a package. The order may also show Status Mismatch. See Order Status Overview.
1. Your system posted the shipment and Zentail rejected it
If your integration sends shipments through the Zentail Open API (POST /salesOrder/shipments), look at the response your system received. Zentail returns the reason in the response, and nothing is shown in the Zentail app. Common reasons:
A 400 error naming a missing field. If you send
shippedToorshippedFrom, the address needsname,addressLine1,cityandpostalCode. LeaveshippedToout to use the order's own address."Sales Order with orderNumber: N not found." The
orderNumbermust be the Zentail order number, not the channel's order id. This appears in the response'serrorslist, and the rest of your batch still goes through."Warehouse with ID" or "Warehouse with Unique ID" not found. The warehouse must exist in Zentail. The order should be routed to that warehouse.
"…is being fulfilled by a warehouse it is not routed to." The order is routed to a different warehouse. Send the warehouse the order is routed to.
A 422 error about the fulfillment package id. Every package needs a unique
fulfillmentPackageId.A 409 error that the package was already recorded by another warehouse.
Fix the request and post the shipment again.
2. A tracking import row matched no order
The Tracking Data import finishes as Complete even when some rows did nothing. A row is skipped without an error when:
the Zentail Order Number in column A matches no order in your account (check you did not use the channel order id);
the order is already finished (for example Shipped or Cancelled).
Rows with a warehouse name that does not exist, no warehouse selected, or a zero quantity for a SKU with nothing left to ship are reported in the import's error file. Open the import's error file to check them. Correct the rows and import them again.
3. Nothing was ever sent
If your system has no record of a post or an import, the shipment never left it. A package sent without a tracking number is also ignored, unless your account allows shipping without tracking. Check your integration's logs for the order, and have it send the shipment again with a carrier and tracking number.
Fix the order now
You do not need to wait for your integration. Open the order in Zentail and add the tracking number by hand. See How to Manually Ship an Order on Zentail, or use the Tracking Data import. Once the package is recorded, the order moves to Shipped and Zentail sends the tracking to the channel. Then fix the cause in your integration, or the next order will stick the same way.
