Shopify
Package tracking API for Shopify stores
For custom Shopify apps and storefronts that want delivery updates connected to their own orders.
Read the guideUse cases
Package tracking API use cases.
A useful tracking integration connects parcel evidence to the order, buyer or operator who needs it. These guides cover different implementations: a storefront page, a supplier handoff, a TMS event receiver, and a seller import all have different failure modes.
Trace provides tracking and owned shipment records. Your application supplies platform integration, customer authorization and business rules. Each guide includes concrete examples, limits and a rollout checklist, rather than assuming a carrier catalog guarantees every parcel result.
WooCommerce
Package tracking API for WooCommerce orders
For WordPress developers connecting a store’s shipping plugin to a consistent parcel timeline.
Read the guideDropshipping
Tracking API for cross-border dropshipping orders
For stores managing supplier parcels, uncertain scan times and cross-border carrier handoffs.
Read the guideLogistics & 3PL
Shipment tracking API for logistics and 3PL teams
For logistics software teams that need tracking evidence inside their own operating system.
Read the guideMarketplaces
Order tracking API for multi-seller marketplaces
For platforms connecting many sellers’ parcels to one buyer-facing order experience.
Read the guideChoose the first workflow to validate
Start with the customer question and the system that owns the tracking number. A shipping plugin, seller upload and carrier scan are different data sources. Model a separate parcel cycle, then decide whether an immediate lookup or monitored record fits your application.
| Goal | First building block | What to measure |
|---|---|---|
| Answer an order-status question | Order-linked records and an authorized parcel view | Support contacts per shipped order; age of verified data |
| Ingest a warehouse or seller file | Durable imports with per-row reconciliation | Created records and verified histories as separate counts |
| Route delivery problems to support | Carrier-fact alerts and labelled Trace inferences | Unresolved actions and evidence quality |
| Recover a receiver outage | Delivery attempts, durable deduplication and deliberate replay | Recovered business events without duplicate notifications |
Use sandbox scenarios for the UI and developer guides for failure handling. Then qualify representative real shipments for your carriers before customer rollout.