How Tracking Works
- Your order is successfully placed with the retailer
- The retailer ships the item and sends a shipping notification
- We automatically extract tracking numbers from the notification
- Tracking information appears in the order response
Tracking numbers are added to orders automatically. There is no separate endpoint to create or manage tracking numbers.
Tracking in Order Response
Tracking information is returned as part of the order response when you retrieve an order:Tracking Number Fields
Tracking Status
Thestatus field is the carrier-derived state of the shipment and is always present on each tracking number:
Estimated Delivery Date
estimated_delivery_date is the carrier’s current delivery estimate for the shipment, as a calendar date in the destination’s local time zone (e.g. "2026-01-18"). It is refreshed on every carrier poll, so the value can shift as the carrier revises its estimate. It is null when the carrier hasn’t reported an estimate — typically until the first in-transit scan — so always handle the null case.
Checkpoint Timeline
checkpoints is the per-scan history of a tracking number, most recent first. Each checkpoint is a single carrier-reported scan event:
The checkpoint timeline is embedded automatically on the single-order read (
GET /orders/{order_id}). On the List Orders endpoint it is omitted by default to keep payloads small — request it with include=tracking_events.Supported Carriers
The following carriers are automatically detected:Multiple Tracking Numbers
An order may have multiple tracking numbers if:- Items ship separately from the retailer
- Multiple products in the order ship from different fulfillment centers
Tracking Links
You can construct tracking URLs for each carrier:When Tracking Is Available
Tracking numbers appear after the order status changes toorder_placed and the retailer has shipped the item. The timing depends on:
- Retailer processing time
- Shipping method selected
- Product availability

