Tracking & Sync
Two things move between TakeTheme and your carrier:
- Shipment creation — the order goes out to the carrier, and a tracking number comes back.
- Status sync — the carrier tells TakeTheme where the parcel is.
Both are handled by background jobs. Neither is instant, and both are gated by one switch.
The auto-sync switch
Auto-sync orders (per carrier, in its settings) controls everything automatic:
| Auto-sync | Shipment creation | Status sync |
|---|---|---|
| On | Orders are pushed to the carrier automatically | Status is fetched automatically |
| Off | Nothing is sent | Nothing is fetched |
Turning auto-sync off doesn't just pause status polling — it also stops orders being sent to the carrier at all. If orders have stopped appearing in your carrier dashboard, check this first.
Manual actions — selecting orders and clicking create shipment — bypass the switch and always run.
Timing
Jobs are queued about a minute after the triggering event and picked up by a worker that checks for due work every 15 seconds, processing a handful at a time.
So a shipment typically reaches the carrier a minute or two after fulfillment starts, not instantly. If a tracking number hasn't appeared after a few minutes, something failed — check the sync-error notification emails.
How delivery status arrives
Bosta pushes a webhook on every state change, so its delivery status is close to live. Statuses map like this:
| Bosta state | TakeTheme delivery status |
|---|---|
| Pickup requested | New |
| Waiting for route · Route assigned | Pending pickup |
| Picked up from business | Picked up |
| Received at warehouse · In transit between hubs | In transit |
| Out for delivery | Out for delivery |
| Delivered | Delivered |
| Exception (NDR) · Awaiting your action | Exception |
| Returned to business · Returned to stock | Returned |
| Terminated · Canceled | Cancelled |
| Lost · Damaged | Lost |
Unknown or purely administrative states (like Archived) are ignored rather than overwriting a good status.
Mylerz has no webhook. A status sync is scheduled once, shortly after the shipment is created; after that, status is refreshed when a sync runs. For a parcel in flight over several days, use the manual sync action to pull current status on demand.
Turbo's webhook does nothing — the integration isn't live.
Reading the statuses
Exception means the carrier hit a problem — customer unreachable, address unclear, delivery postponed — but the parcel is still moving. It is not terminal, and it's the earliest signal you get that an order is heading for a failed delivery.
Returned means the parcel came back to you. Nothing is restocked automatically; if the goods are back on your shelf, restock them through a return or by cancelling with restock.
Auto-fulfillment on shipment creation
With Auto mark orders as fulfilled enabled, creating a shipment marks the order's items fulfilled and stamps the tracking number onto every item — you skip the packing step entirely. With Send confirmation email to customer also on, the shipping notification goes out at the same moment.
Leave auto-fulfillment off if you want packing to stay an explicit human step.
When sync fails
Failures are recorded on the job and emailed to the addresses in Notify on sync errors. Common causes:
- Credentials rejected — the carrier's key, or the Mylerz password, changed.
- Address the carrier won't accept — the city or governorate doesn't match one the carrier recognises. Use the city / zone list action to see the values it expects.
- Missing phone number — carriers reject shipments without a reachable contact.
Fix the cause and create the shipment manually; the order isn't stuck, it's just not been sent.
Related
- Carriers
- Fulfillment
- Order lifecycle — where delivery status sits among the four statuses