Shippo provides a tracking-status API and shipping-label workflows. Its official reference exposes tracking history and links tracking to transactions when a label was purchased through Shippo. Trace offers tracking data and owned shipment records without label purchasing.
Compare the complete application workflow. A store may benefit from retaining its shipping provider while building its own tracking view, but adding a second integration is useful only when the actual carrier results and operating model fit.
Keep shipping transactions and parcel records distinct
A shipping transaction, an order and a carrier tracking number are different resources. Keep them separately in your application. When using Trace, create a shipment record for the particular parcel cycle and save the returned ID against your own order or shipping transaction reference.
Trace’s order_id and reference connect parcel records to your business context. Your application still determines buyer authorization, partial-delivery summaries and messaging. Trace does not create Shippo transactions, purchase labels, negotiate rates or replace the carrier’s delivery-dispute process.
| Decision | Trace API | Shippo |
|---|---|---|
| Label purchasing | Not provided | Official API reference includes shipping-label transactions. |
| Tracking status | Normalized observed events, freshness and source errors | Official tracking reference includes status and tracking_history. |
| Parcel grouping | Owned records with order_id and reference | Your application links its order model to the appropriate resources. |
| Delivery evidence | Qualified source events; UTC or explicit unknown-timezone metadata | Inspect the provider’s actual event and timestamp contract. |
| Update integration | Signed webhooks, delivery attempts and explicit replay | The official API includes tracking-status webhook resources. |
| Total cost | Successful lookup budget plus your implementation work | Check current terms for tracking, labels and account features. |
Evaluate three practical store workflows
A small store already buying labels through Shippo may prefer to keep the associated tracking workflow and avoid another provider. First identify what is missing from its current buyer experience; changing the data provider will not automatically solve a confusing page layout or order authorization bug.
A WooCommerce developer may want a custom timeline that combines numbers from several shipping plugins. Trace can be evaluated as a separate data layer while the plugins continue creating labels. The integration must read each plugin’s supported tracking fields rather than assume a universal metadata key.
A marketplace may need per-parcel order records and durable uploads from sellers. Compare Trace’s record/import workflow with the existing data model, preserving shipping transaction references. Successful import should be measured separately from successful carrier acquisition.
Move the tracking contract while retaining your shipping history
Save the existing transaction reference, carrier identifier, number and local order ID. Map the known carrier into Trace’s catalog and create a record with an idempotency key tied to the parcel cycle. Do not use a purchased-label transaction ID as the tracking_number input.
Trace returns six normalized statuses and observed scan descriptions. When a provider’s status or substatus is more detailed, preserve that original information in your migration audit rather than silently discarding it. Check estimates, null timestamps, locations and ordering before the customer interface assumes identical fields.
- Pilot authorized parcels that include split deliveries, replacement cycles and missing scans.
- Separate created records from verified histories in your migration report.
- Implement the Trace raw-body signature verifier instead of reusing another provider’s authentication logic.
- Deduplicate buyer-facing actions and retain a reconciliation read path.
- Set explicit rollback criteria for unsupported sources, bad carrier mappings and stale observations.
Explain stale or unavailable results in the storefront
A successful API call does not establish that the latest carrier scan is recent. Trace includes last_checked_at and data_freshness so your application can distinguish live, cached and opt-in stale snapshots. A stale response retains its original verification time and does not generate new shipment notifications.
When no configured source supplies usable data, the default response is a retryable error rather than an invented pending result. Present an update-unavailable state and keep the customer’s purchase status intact. If a scan lacks a timezone, display its source-local time with a clear label instead of calculating a precise UTC delivery age.
For example, a WooCommerce page can continue showing ‘In transit — last verified yesterday’ while its backend investigates an upstream failure. That is a better explanation than showing ‘Label created’ simply because the newest lookup returned no usable timeline.
Compare the same parcel workload before deciding
Trace’s unit is a successful lookup, including cache hits and successful background refreshes. A shipping provider’s tracking and label units may differ. Estimate active parcel lifetime, refresh count, direct support lookups and implementation work instead of comparing a headline price with a different unit.
The Trace free plan provides 200 monthly lookups, and paid checkout is currently disabled. Verify current Shippo commercial terms through its official account and pricing materials. This guide does not claim a universal cost advantage, guaranteed carrier coverage or matching shipping functionality.
Evaluate Trace when you want a custom, order-linked tracking layer with explicit evidence and failure semantics. Retain Shippo when its integrated shipping and tracking workflow meets your needs. A limited dual-read pilot can establish which option fits without changing live customer notifications prematurely.
Common questions
Does Trace replace Shippo shipping labels?
No. Trace provides tracking and shipment records. Keep a shipping provider for labels and rates.
Can I preserve a Shippo transaction reference?
Yes, keep that reference in your own migration mapping or appropriate record metadata. It remains separate from the carrier tracking number and Trace shipment ID.
Should I move every parcel as soon as one test succeeds?
No. Test several actual shipments for the relevant carriers and destinations, including exceptions and unavailable timelines, before expanding the rollout.
References & next steps
Implementation details were checked against Trace’s current API. External product details may change; verify the linked documentation before deciding.