One despatch process across several carriers — labels, rates and tracking without a separate portal for each.
A multi-carrier integration connects your ERP or WMS to several carriers through their APIs, so rates, labels, manifests and tracking are handled inside your own despatch process. Instead of staff logging into DHL, FedEx and UPS portals separately and re-keying addresses, the despatch transaction produces the label and writes the tracking number back.
Carrier portals are where despatch time disappears. Each one needs its own login, its own address entry and its own tracking reference copied back by hand. At any volume this is both slow and a reliable source of address errors. The integration removes the re-keying and, as a by-product, makes carrier cost comparable because every shipment is rated through the same process.
Carrier APIs can validate and standardise the delivery address before a label is produced, which is where most failed deliveries originate.
Dimensions, weight, service level and destination are sent to each configured carrier for a quote.
The chosen carrier returns a label in printable form, with the tracking number, booked against your account.
End-of-day manifesting tells the carrier what is being collected, which is required by most of them.
The tracking number is stored against the despatch and the sales order, and pushed to the customer or storefront.
A dispatch team picks the lowest quoted rate for every parcel. On paper this minimises freight cost. In practice the invoice does not match the quotes, and nobody can say why.
Three gaps explain it. Dimensional weight: a light, bulky carton is billed on volume, so a rate quoted on actual weight understates the charge. Surcharges: fuel, remote-area delivery, residential delivery and address correction are added after the fact and vary by carrier. And service failure: the cheapest carrier to a difficult pincode may have poor serviceability there, so a proportion of those parcels are delayed or returned, and a return costs the outbound freight twice plus handling.
Rate shopping that uses dimensional weight, includes known surcharges, and weights carriers by measured performance to each destination zone produces a different and better answer than raw rate comparison. The saving usually comes less from choosing cheaper carriers than from not choosing an unsuitable one — failed deliveries are far more expensive than the rate difference that caused them.
| Term | What it means |
|---|---|
| Carrier service | A specific product from a carrier — express, economy, same-day — each with its own rate and transit. |
| Manifest | The end-of-day summary handed to the carrier listing everything tendered. |
| AWB | Air waybill, the carrier's tracking document number for a consignment. |
| Dimensional weight | Billable weight derived from size rather than mass, which is what makes light bulky parcels expensive. |
| Serviceability | Whether a carrier delivers to a given pincode at all, which varies considerably in India. |
Rating and surcharges depend on them. Missing data produces wrong rates and later billing adjustments.
If one API is down, despatch must continue. Build a fallback rather than stopping the dock.
Residential, remote-area and fuel surcharges can invert the apparent cheapest option.
A label produced without the despatch being recorded creates a shipment the system does not know about.
| Metric | What it tells you | What distorts it |
|---|---|---|
| Cost per shipment by zone | Where freight spend actually concentrates, which is rarely where it is assumed. | |
| Quoted vs invoiced freight | The gap caused by dimensional weight and surcharges. Persistent gaps mean the rate card is incomplete. | |
| On-time delivery by carrier and zone | Carrier performance varies enormously by destination; a single national figure hides it. | |
| Failed delivery rate | The most expensive outcome, and the one rate comparison ignores entirely. |
We build and support the systems this page describes. Start with a free working proof of concept — no cost, no commitment.