Carrier integration is the technical connection between your commerce stack and a shipping carrier, so your systems can buy labels, fetch rates, book pickups, and receive tracking events without anyone re-typing order data into a carrier portal. Done well, it is invisible. Done badly, it is why your ops team spends Fridays copying tracking numbers into spreadsheets.
This guide explains how carrier integrations actually work, the three ways they get built, and what to check before you add your next carrier.
What a carrier integration actually does
A full integration covers four flows, in both directions:
- Rates: ask the carrier what shipping this parcel costs, live, so checkout and rate shopping use real numbers.
- Labels and booking: create the shipment, get the label and tracking number, book the pickup.
- Tracking events: receive every scan and status change, from handover to delivered. Carriers return anywhere from 10 to 115 different statuses, which is why normalizing them into clean milestones matters more than the raw feed.
- Reverse logistics: return labels, drop-off points, and customs documents on cross-border returns.
Miss any of the four and a human fills the gap by hand.
The three ways integrations get built
Carrier APIs. Modern carriers expose REST APIs for rates, labels, and tracking. Quality varies enormously: some are excellent, some are poorly documented, and some Nordic and regional carriers barely have one. Where APIs are weak, Pango can scrape carrier data in real time, built to fit that carrier.
EDI. The older standard, still common with large and freight carriers (LTL included): structured files exchanged on schedules rather than live calls. Reliable, rigid, slow to change.
Prebuilt connectors. A platform maintains the integrations so you do not. Pango connects to more than 100 carriers through prebuilt connectors, including the Nordic networks like PostNord and Instabee that US-centric platforms skip. Connecting a carrier becomes configuration, not an engineering project.
Integration vs orchestration: the difference that costs money
A connection to one carrier is an integration. Deciding which carrier gets this parcel is orchestration, and it is where the savings live. Orchestration means routing each order against your real rates, delivery promises, and carrier performance, then failing over when a carrier has problems.
That requires the integrations AND the layer above them: multi-carrier shipping with rules, rate shopping, and delivery promises at checkout built from real carrier data. In Pango, the same record also drives the warehouse pick and pack and the branded tracking page, so a delay scan can trigger a customer message automatically instead of a support ticket.
What to check before adding a carrier
- Coverage of all four flows. Many "integrations" are label-only. Ask about tracking webhooks and returns.
- Status quality. How many raw statuses does the carrier emit, and who normalizes them?
- Cross-border support. Customs docs, duties handling, and DDP vs DDU treatment.
- Failover. When the carrier's API goes down on Black Friday, what happens to your labels?
- Time to live. A prebuilt connector should be days, not a quarter. Pango connects carriers through configuration, with new connectors built to fit when a brand needs one.
The bottom line
Carrier integration is plumbing, and plumbing decides what you can build: real delivery promises, honest tracking, automated returns, and routing that saves money on every parcel. Pango ships with 100+ carriers prebuilt and runs the orchestration on top. See the post-purchase operations platform and book a demo.
