← Back to blog

Multi-carrier shipping: how to do it without five logins

Published 4 August 2026 · 3 min read

Multi-carrier shipping can be unified into one interface that creates the shipment, prints the label and tracks its status regardless of carrier. Shipment creation, label printing, pickup booking and tracking can all be unified. Pricing, the claims process and rules on dimensions and weight cannot — those stay carrier-specific. The deciding factor is whether the tool translates shipment states into one shared vocabulary, or merely displays whatever each carrier sent.

Why five portals cost more than they look

The direct cost is time: log in, find the order, retype the address, print. At thirty shipments a day across five carriers that is not minutes but hours a week.

The indirect cost is larger. An address retyped by hand contains typos. A tracking number that never reaches the order means a question from the customer. And a shipment status you can only see by logging into a portal means nobody is watching it — until the customer gets in touch.

What can be unified

  • Creating a shipment from an order — one form regardless of carrier.
  • Label printing, including in bulk for a whole batch.
  • Booking a pickup.
  • Tracking a shipment and its status.
  • Writing the tracking number back into the order in the shop.

What cannot be unified

Pricing and invoicing stay carrier-specific — the tool shows what you shipped, but the invoice comes from the carrier.

Claiming for a damaged shipment follows each carrier’s own rules and usually requires their own form.

Size and weight limits differ for everyone. A good tool knows them and warns you up front; they cannot be unified, because this is physics, not software.

The key question: a shared vocabulary of states

Every carrier reports status in its own codes. One says "at transit depot", another "at hub", a third a numeric code. A tool that merely displays them moves the confusion from five portals into one window.

A tool that translates them into a shared set — created, picked up, in transit, out for delivery, delivered, returned, exception — lets you attach a rule to a state. That is the difference between "I can see it in one place" and "I can do something about it".

For an unknown state the only correct answer is "unknown", with an incident recorded. A tool that quietly files an unknown state under delivered does more damage than one that does not process it at all.

How MitoOps handles it

The Shipping module creates shipments, prints labels in bulk and tracks status for seven connected carriers: Packeta, DHL Express, SPS, GLS, DPD, Express One and InPost. Slovak Post, Czech Post, Balíkovna and DHL Freight are in preparation.

States are translated into one shared set that automations can hook into. The carrier’s original message is retained — if a translation turns out to be inaccurate, it can be corrected retroactively without losing data.

Common questions

Is a unified tool worth it with one carrier?
Usually not. With a single carrier their own portal is normally sufficient. The benefit starts with the second carrier and becomes clear with the third.
What matters more: number of carriers or quality of integration?
Quality. A tool with three carriers connected through official APIs that report status reliably beats one with twenty where half run on unofficial workarounds.
What about cash on delivery?
Cash on delivery is where carriers differ most — specifically in when the amount can still be changed and when it cannot. Ask whether the tool supports changing it and what happens when the change fails.
Do I need my own carrier contracts?
Yes, in most cases. The tool uses your credentials and your rates — it is not a reseller, it is an interface to accounts you already hold.

Dealing with the same thing?

MitoOps brings stock, orders and shipping into one system. Let us walk through your numbers.