Re-exporting Changed Orders

With re-export of changed orders enabled for your organization, an order you already exported does not leave the Orders Export feed for good. If its data changes after a successful export, Zendera hands it to your exporter again so the carrier can be told about the change.

How it works

1. You fetch a shipment with GET /v1/orders/export and acknowledge it with POST /v1/orders/export/status, echoing the shipment’s exportToken.
2. Zendera records which payload the carrier received.
3. If the order, its products, or its stops change afterwards and the resulting shipment payload differs from the one the carrier received, the order appears in the feed again — with isUpdate: true and a new exportToken.
4. You send it to the carrier as an update of the existing shipment and acknowledge it again with the new token.

An order is only reconsidered for 14 days after its last successful export. Changes after that window don’t bring it back.

What your exporter must do

• Honour isUpdate. When it is true, send the shipment to the carrier as an update (for example with the carrier’s update indicator), not as a new shipment — otherwise the carrier creates a duplicate.
• Echo exportToken verbatim in the acknowledgement. It identifies the exact payload you received, so a change that lands between your fetch and your acknowledgement still triggers a re-export.
• Page until the end. While re-export is on, total and totalPages can overcount, because orders whose payload turns out unchanged are dropped after the page is loaded. Keep requesting pages until you reach totalPages.

Good to know

• Orders acknowledged before re-export was enabled stay final. Only exports acknowledged while it is on can come back.
• Every acknowledgement counts toward the five-attempt limit, successful ones included. An order with five export statuses no longer appears in the feed.
• An order whose payload didn’t really change is not re-sent, even if it was touched in Zendera.

Related documentation

• Orders Export — the fetch, acknowledge, and progress loop