One Odoo shipping cockpit that rate-shops 25+ carriers, routes by rules, and prints PDF + ZPL labels at fulfillment. One-time license from $499.00 USD for Odoo 17, 18, 19 — includes 12 months of updates and support.

One Odoo shipping cockpit that rate-shops 25+ carriers, routes by rules, and prints PDF + ZPL labels at fulfillment.
No payment now. This sends a quote request to our team — we'll follow up by email with pricing and next steps.
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.
Pluggable carrier framework where each carrier (DHL, FedEx, UPS, GLS, Aramex, SMSA, and more) is a provider class extending Odoo's native delivery.carrier model
Live rate-shopping at fulfillment: parallel calls to every eligible carrier's rating API return a ranked cheapest/fastest quote list on the delivery order
One-click booking that pulls the carrier tracking number back onto stock.picking and generates the label in a single action
Unified label output in QWeb PDF (A4/Letter laser) and raw ZPL (Zebra thermal) so labels print correctly on any warehouse printer
Carrier-rule routing engine evaluating weight band, destination zone/country, order value, incoterm, product category, and warehouse
Computed shipping fields using @api.depends on package weight and destination to auto-suggest or auto-select the routed carrier
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 2–4 weeks 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.
Runs fulfillment across several carriers and regions and is tired of juggling separate connectors and portals. Wants one cockpit where the team rate-shops, books, and prints, and where shipping policy is enforced by rules instead of memory.
Packs and ships hundreds of orders a day and needs labels that print right the first time. Cares about ZPL to the Zebra printers, fast one-click booking, batch manifests, and a dashboard that flags stuck shipments before customers complain.
Owns shipping cost and delivery SLAs. Wants live rate-shopping to cut spend, rule-based routing to protect margins and delivery promises, and native Odoo data so shipping analytics live alongside sales and inventory — no external SaaS silo.
Buy the license on ecosire.com and download the Multi-Carrier Shipping Hub for Odoo (Rate-Shopping Backbone) module ZIP from your account dashboard.
Extract the ZIP into your Odoo custom addons folder on the server (or upload via Apps > Install from file on Odoo.sh / runbot).
Activate Developer Mode, open Apps, click Update Apps List, search for Multi-Carrier Shipping Hub for Odoo (Rate-Shopping Backbone), and press Install.
Open the new menu, paste your ECOSIRE license key, connect any external credentials (Shopify, Amazon, Stripe, etc.), and save.
Run the built-in connection test, sync your first 10 records, and schedule the recurring cron. Contact support if anything fails.
| Criterion | ECOSIRE | Custom Build | Competitor | Odoo Native |
|---|---|---|---|---|
| Coverage across many carriers in one place | One hub; every carrier is a pluggable provider in the same rate/label/track pipeline | Possible, but you design and maintain the whole framework yourself | Usually one connector per carrier — several apps to install and reconcile | |
| Live rate-shopping (cheapest/fastest) at fulfillment | Parallel live rating across all eligible carriers with ranked quotes | Only if you build the multi-carrier rating loop and ranking logic | Rarely cross-carrier — each connector rates its own carrier in isolation | |
| Rule-based routing by weight / zone / value / incoterm / warehouse | Configurable routing engine with computed fields and record rules | Build-your-own; ongoing rule maintenance falls on your team | Limited or per-connector; rarely a unified policy layer | |
| Unified label output (PDF + ZPL to thermal printers) | QWeb PDF and raw ZPL from one screen, matched to your printers | You implement ZPL streaming and label templates from scratch | Varies by connector; ZPL support inconsistent | |
| Consolidated cross-carrier tracking dashboard | One dashboard polling all carriers via scheduled automated actions | Requires building the polling jobs and aggregation views | Per-carrier tracking, no single roll-up view | |
| Fits your exact accounts, contract rates & workflow | Built and configured to your carriers, rates, warehouses and process | Fully bespoke, but you own all analysis, build and QA effort | Generic — you adapt your process to the app | |
| You receive the full module source (no lock-in) | Yes — delivered to your repo, licensed to your organization | Yes, but at full bespoke build cost and timeline | Typically closed/obfuscated, tied to a vendor subscription | |
| Ongoing support & Odoo 17/18/19 upgrade path | Support window plus optional maintenance across 17/18/19 | Your team owns every fix and version migration | Depends on the third-party publisher's roadmap |
No. The Multi-Carrier Shipping Hub is a build-to-order module — it is not an existing apps.odoo.com listing and there is no instant-download link. ECOSIRE builds it around your specific carriers, contract rates, warehouses, and workflow, then installs it on your Odoo instance.
Typical lead time is 2–4 weeks from kickoff. We start with a short scoping call to confirm carriers, rating/label requirements, and routing rules, then build and configure the module, run test shipments against your live carrier accounts during UAT, and go live with training. Timeline moves with the number of carriers and any custom customs/marketplace requirements.
Every build includes a post-go-live support window (typically 30–90 days, depending on scope) covering bug fixes and adjustments for carrier-API changes within the delivered scope. After that, ECOSIRE offers ongoing support and maintenance plans for new carriers, Odoo version upgrades, and enhancements. Because you receive the full module source, you're never locked to us.
We build and support the hub for Odoo 17, 18, and 19, on both Community and Enterprise. The module extends native models (delivery.carrier, stock.picking) and uses standard Odoo mechanisms — ir.model.access.csv, record rules, QWeb reports, and ir.cron automated actions — so it fits cleanly into a standard upgrade path.
Yes. The framework is pluggable by design: each carrier is a provider class extending delivery.carrier. If a carrier exposes a rating/label/tracking API (or usable EDI), we can add it as a provider in the same rate-shop, label, and tracking pipeline. Tell us your carriers during scoping and we'll confirm feasibility.
Yes. The hub exposes rate, book, label, and track actions over Odoo's XML-RPC/JSON-RPC API, so an external storefront, WMS, or marketplace connector can trigger rate-shopping and pull tracking numbers. It also works natively inside Odoo Sales and Inventory, so most shops don't need any external glue.
At fulfillment the engine calls each eligible carrier's live rating API in parallel and returns a ranked quote list (cheapest or fastest). Your carrier-routing rules — weight band, zone/country, order value, incoterm, warehouse — narrow the eligible set first, so the pick respects your shipping policy. A user can override, or a rule can auto-select with no clicks.
One Odoo shipping cockpit that rate-shops 25+ carriers, routes by rules, and prints PDF + ZPL labels at fulfillment.