Manufacturers and distributors that ship a mix of small parcels and palletized freight quickly outrun Odoo's native delivery layer. Out of the box, stock.picking carrier integrations cover a handful of parcel providers (and most are Enterprise-only delivery_* bridges); LTL and full-truckload simply aren't modeled, and there is no rate comparison across carriers. Warehouse teams end up copying addresses into a carrier portal, re-keying weights and dimensions, downloading a PDF label, and pasting a tracking number back into the sale order by hand. Every manual hop is a chance for a mis-ship, a missed cut-off, or a freight bill that nobody reconciled against the quoted rate.

ECOSIRE builds a dedicated Cargoson integration that treats Cargoson as your single freight aggregation layer, giving one Odoo connection to 1,500+ EU and US carriers across parcel, LTL and freight. Technically, we ship a proper Odoo module: a new delivery.carrier provider type (cargoson) plus supporting models such as cargoson.shipment and cargoson.rate (models.Model with typed fields, @api.depends computes for chargeable/volumetric weight, and stored relations back to stock.picking and sale.order). A configured res.config.settings block holds your Cargoson API credentials and default service mappings, and all access is locked down through ir.model.access.csv and record rules so only warehouse and logistics roles can book or void shipments.

The booking flow lives where your team already works. From a delivery order, a Rate Shop action calls the Cargoson API server-side (via a resilient requests client with retries, timeouts and structured error handling) and returns a comparison of available carriers, services, transit times and prices rendered in an OWL/XML view. The user picks a service, confirms the booking, and the connector persists the carrier tracking reference on the picking, pulls the label and any freight documents (CMR/BOL) as ir.attachment records, and generates a QWeb-rendered shipping summary if you need an internal manifest. Tracking status is synced back into Odoo through a scheduled automated action (ir.cron) that polls Cargoson and updates each shipment's state, with optional customer notifications on the picking chatter. Everything is exposed over Odoo's XML-RPC/JSON-RPC API too, so upstream systems can trigger rating or read tracking programmatically. The module is written to be Community-compatible and is validated against Odoo 17.0, 18.0 and 19.0.

Because this is build-to-order, you are not downloading a generic app and hoping it fits. We start with a short scoping call to confirm your carrier mix, service-level rules, weight/dimension sources, label formats and any customs or multi-warehouse constraints. We then build the connector against your Cargoson account, test it end-to-end on a staging copy of your database with your real carriers, and hand over installable source, documentation and a git repository. Typical delivery is one working week from confirmed scope, followed by a post-go-live support window. No fabricated benchmarks, no instant-download claims — just a connector engineered to your freight reality and supported by the team that built it.