Most Odoo shops end up with a drawer full of single-carrier connectors: one app for DHL, another for FedEx, a spreadsheet for Aramex, and a warehouse team that alt-tabs between four label portals just to get an order out the door. The Multi-Carrier Shipping Hub replaces that mess with a single shipping backbone inside Odoo — a real delivery.carrier extension framework where every carrier is a pluggable provider, so rating, label generation, and tracking all live in one cockpit on the delivery order and stock.picking.

This is a BUILD-TO-ORDER module. It is not an existing apps.odoo.com download and there is no instant-download link. ECOSIRE designs, builds, installs, and supports it against your exact carrier accounts, contract rates, warehouses, and fulfillment workflow. Typical lead time is one working week from kickoff to a working install on your Odoo instance, and we support Odoo 17, 18, and 19 on both Community and Enterprise.

At the heart of the hub is a pluggable carrier framework. Each integration — DHL, FedEx, UPS, GLS, Aramex, SMSA, and more — is implemented as a provider class extending Odoo's native delivery.carrier model, so adding or swapping a carrier never means bolting on another disconnected app. When a picking is ready to ship, the rate-shopping engine calls every eligible carrier's live rating API in parallel and returns a ranked quote list. Your team (or an automated rule) picks the cheapest or fastest option, and the hub books the shipment, pulls the tracking number back onto the delivery order, and generates the label in one action.

Labels print in the format each carrier and each printer actually needs. A QWeb-rendered PDF handles A4/Letter laser printers for packing docs, while raw ZPL streams straight to Zebra thermal label printers over the network or via the browser print bridge — no manual PDF-to-label conversion, no cropped labels. Every label, commercial invoice, and customs doc is attached to the picking so the full paper trail stays in Odoo.

Carrier-rule routing turns your shipping policy into configuration instead of tribal knowledge. Rules evaluate weight bands, destination zone/country, order value, incoterm, product category, and warehouse to auto-select or restrict carriers — heavy pallets to a freight partner, GCC deliveries to SMSA or Aramex, high-value parcels to an insured express service — enforced by record rules and computed fields (@api.depends on weight and destination) so the right choice is made before a human ever looks. A consolidated tracking dashboard then rolls every open shipment across every carrier into one screen: status, ETA, exceptions, and last-mile events pulled via scheduled automated actions, with filters by carrier, warehouse, and delay so ops sees problems before customers call.

Because the whole thing is native Odoo, it inherits security via ir.model.access.csv and record rules, exposes shipping actions over XML-RPC/JSON-RPC for your WMS or storefront, and slots cleanly into your existing Inventory and Sales flows. You keep your Odoo. You get one shipping cockpit instead of ten.