Logistics teams running Odoo hit a wall fast: the core Inventory and Sales apps handle stock moves and delivery orders, but they have no real concept of a freight shipment. There is no first-class object that carries the load's mode (road, air, ocean, rail), consolidated packages, chargeable vs actual weight, carrier assignment, freight cost, and margin in one place. So planners fall back on spreadsheets for rating and consolidation, re-key carrier bookings by hand, and lose the link between what was quoted, what was dispatched, and what the carrier actually charged. Native stock.picking and delivery carriers get you a shipping label price for a single parcel — they do not get you a transport operation.

All in One Freight Management closes that gap with a purpose-built domain layer on top of Odoo. We add a freight.shipment model (with its own sequence, states, and QWeb documents) that links to sale orders, purchase orders, and one or many stock.picking records, so a shipment can consolidate multiple orders or split one order across carriers. A freight.rate / freight.charge.line structure drives rating: chargeable-weight and volumetric calculations run through compute methods with @api.depends on package dimensions and weight, so freight cost, fuel and accessorial surcharges, and customer sell price recompute automatically. Carrier assignment, booking references, and milestone tracking (booked, in transit, at destination, delivered, POD) live on the shipment, with automated actions and scheduled actions to flag exceptions and stale bookings. Everything respects Odoo's access model — ir.model.access.csv for the new models plus record rules to scope shipments by company and transport team.

Technically, the module is a clean, upgrade-safe addon: its own __manifest__.py, versioned for the Odoo release you run, models under models/, backend views and OWL components under views/, security rules, QWeb PDF reports (freight manifest, house/master documents, load sheet), and demo data for UAT. Costs post to accounting through standard journal entries and vendor bills so freight margin lands in your P&L rather than a side spreadsheet. Because it is Odoo-native, the shipment, rating, and tracking data are all reachable over the XML-RPC/JSON-RPC API, so carrier portals, EDI, or a customer tracking page can read and write shipments programmatically. We build against Community or Enterprise as your edition dictates and note any Enterprise-only dependencies (studio-style fields, advanced accounting) up front so nothing surprises you at install.

This is a made-to-order engagement, not an instant download. After a short scoping call we confirm the exact modes, rating rules, carrier set, and integrations you need, then build, test on a staging copy of your database, and hand over installable source. Typical delivery is one working week from confirmed scope, depending on how many carriers, document formats, and localizations are in play. Pricing starts from $999 (indicative, single-company base scope); multi-company operation, additional carrier/EDI integrations, deeper localization of freight documents, and migration of historical shipment data increase the quoted scope. You receive a fixed quote after the scoping call, never a surprise invoice.