Webhook retries & replay
Shipment tracking webhook retries, deduplication and replay
A practical receiver design for teams that cannot afford lost or duplicated order updates.
Read the guideDeveloper guides
The difficult parts of a tracking integration tend to appear after the first successful request: a receiver goes down, an import has rejected rows, a source omits its timezone, or a carrier lookup fails during an outage.
These guides explain those cases using Trace’s actual contracts. Each separates observed evidence from application policy and includes concrete implementation examples. Use the API reference for endpoint schemas and current limits.
Webhook retries & replay
A practical receiver design for teams that cannot afford lost or duplicated order updates.
Read the guideCSV shipment imports
For warehouse exports, seller uploads and backfills that need recoverable processing instead of a long synchronous request.
Read the guideTracking event timezones
For developers building parcel timelines, no-scan alerts and merchant analytics from incomplete source timestamps.
Read the guideStale tracking data
For teams that need a useful tracking experience when carrier sources temporarily stop returning usable events.
Read the guide