Most Odoo teams hit the same wall the moment shipping stops being an afterthought: the standard delivery carrier framework ships thin real-world coverage, and each delivery.carrier you configure only rates one account against one provider. If you move parcels through several couriers, add freight (LTL/FTL) on top, or negotiate zone- and account-specific tariffs, native Odoo has no clean way to compare live rates side by side at quote time. Sales reps guess a flat fee, margin leaks on every under-quoted shipment, and warehouse staff re-key tracking numbers into carrier portals by hand. The generic off-the-shelf apps.odoo.com connectors typically bolt on one or two carriers and leave you buying a separate module per provider — none of which talk to each other or to your freight lanes.

We build a single multi-carrier rating and booking layer for your Odoo. At its core is a normalized delivery.carrier extension plus a rate-shopping engine that fans a shipment request out to every connected account — 1500+ parcel and freight carriers reachable through their REST/SOAP APIs or, for the legacy freight world, EDI (X12 210/211/990, EDIFACT IFTMIN/IFTMBF). Each integration is a Python service model that maps your stock.picking, package dimensions, weights, incoterms, and destination into the carrier's request schema, then normalizes the response back into a common quote object: service level, transit days, surcharges, dimensional weight, and a landed rate. Credentials and account numbers are stored per company and per carrier, secured with ir.model.access.csv plus record rules so a subsidiary only sees its own negotiated tariffs. Compute fields (@api.depends on weight, volume, destination zone) recalculate available services live on the sale order, and an OWL widget presents the ranked options so the rep picks by price, speed, or a business rule you define. On confirmation we generate the label (PDF via QWeb or the carrier's own label stream), write the tracking reference back to the picking, and can fire an automated action to email the customer or push an EDI 214 status feed.

Because tariffs, dimensional-weight formulas, and accessorial surcharges change constantly, the engine is built around a versioned rate-map and a caching layer so you are not hammering carrier APIs on every keystroke, with a scheduled ir.cron job to refresh negotiated rate tables. Everything is exposed over Odoo's XML-RPC/JSON-RPC API too, so an external OMS or marketplace bridge can request a rate or book a shipment programmatically. The build targets Odoo 17.0, 18.0, or 19.0; it works on Community and Enterprise, and where Enterprise-only features (like the studio-driven approvals or advanced accounting on freight cost bills) are in play we design around your exact edition rather than assuming it.

Delivery is build-to-order: nothing here is a pre-existing download you install and forget. After a short scoping call we confirm which carriers, service levels, freight lanes, and EDI trading partners are in scope, agree the UAT criteria, and build your version against a copy of your data on a staging instance. Typical delivery is 2 to 4 weeks from confirmed scope, depending on carrier count and EDI complexity, and you receive installable source, documentation, a training session, and a post-go-live support window. Pricing starts from $249 (indicative, single-company base scope); the number of live carrier integrations, EDI trading-partner onboarding, multi-company tariff separation, and localization depth increase the quoted scope.