Shipping integrations: carriers, labels and tracking pages
How orders become labelled parcels with tracking the customer can follow, what to connect, and where shipping integrations fail.
The short answer
Between an order being paid and a parcel arriving sits the shipping integration: it takes the order, applies rules to choose a carrier and service, buys and prints the label, hands tracking to the customer and updates the order as the parcel moves. Doing this well is mostly configuration on modern platforms, using native shipping or a multi-carrier service rather than integrating each carrier by hand, because carriers change their interfaces constantly. The feature that reduces support contact most after checkout is a branded tracking page on your own domain that says clearly where the parcel is and when it will arrive. And the rules that pick the service, by weight, destination, value and speed, must be tested with real orders to real destinations before peak season, not during it.
What the integration does
| Step | What happens | What must be right |
|---|---|---|
| Rate at checkout | The customer sees shipping options and costs | Product weights and dimensions; zones; rules; delivery estimates |
| Service selection | Rules choose carrier and service per order | Rules match what carriers actually offer per destination |
| Label purchase | A label is bought from the carrier and printed | Address validated; no duplicate purchase on retry; customs data for cross-border |
| Fulfilment | The order is marked shipped; tracking attached | Status mapped correctly; partial shipments handled |
| Customer tracking | Email and a tracking page with stages and dates | Branded page; proactive updates on delay |
| Delivery and exceptions | Delivered, attempted, returned to sender | Events mapped to status; exceptions routed to support |
| Returns | Return labels generated from the returns portal | Same rules; reason codes captured |
Setting it up
- Complete product data: weights and dimensions on every product, or rates and labels will be wrong.
- Choose native shipping or a multi-carrier service; avoid direct carrier integrations unless volume demands them.
- Write the rules: by destination zone, weight, value and speed, and check each rule maps to a service the carrier offers there.
- Set up the branded tracking page on your domain with clear stages, expected dates and a contact route.
- Configure notifications: shipped, out for delivery, delivered, delayed.
- Test real orders to each zone, including cross-border with customs data, and read the labels.
- Monitor failed label purchases, stale tracking and delivery exceptions, and route them to a person.
The tracking page
A carrier’s tracking page is generic, sometimes in another language, often uninformative. A branded page on your own domain shows the parcel’s stage in plain words, the expected delivery date, what to do if it is late and how to reach you, with the store’s look. It is where customers go instead of emailing, and it is a page many stores never build because the carrier link was already in the email. Build it; the support inbox will show the difference.
What this means for you
Complete the product data, use native or multi-carrier shipping rather than hand-built carrier integrations, write rules that match real services per zone, build a branded tracking page, set proactive notifications, test every zone with real orders before peak, and monitor the failures. Shipping done this way is invisible to the customer and quiet in the support inbox, which is exactly what it should be.
Frequently asked questions
Should we integrate directly with our carrier?
Rarely. Carriers change their interfaces, rates and services frequently, and a direct integration becomes a maintenance burden. The platform's native shipping and multi-carrier services maintain those connections for you, offer negotiated rates, and let you switch or add carriers by configuration. Direct integration makes sense only at volumes and with contracts that justify it.
Why do customers still ask where their order is?
Because the tracking email pointed at a carrier page that said nothing useful, or the parcel status stopped updating. A branded tracking page on your own domain that shows clear stages, the expected date and what to do if it is late answers the question before it is asked. Proactive updates on delay do the rest.
What breaks in shipping integrations?
Address formats a carrier rejects, weights and dimensions missing on products so rates are wrong, rules that pick an unavailable service for a destination, labels bought twice after a retry, and tracking events not mapped to order status. Each is caught by testing real orders to each destination and by monitoring failed label purchases and stale tracking.
Sources
- Shopify Help Center: Shopify Shipping (accessed 2026-09-12)