A build-to-order Odoo freight and transport management module that unifies shipment planning, multi-mode freight rating, dispatch, and carrier tracking in one workflow. ECOSIRE scopes, builds, installs, and supports it for your Odoo 17/18/19 environment. Built to order by ECOSIRE for Odoo 17, 18, 19 — indicative price from $299.00 USD; request a quote for a scoped proposal.

A build-to-order Odoo freight and transport management module that unifies shipment planning, multi-mode freight rating, dispatch, and carrier tracking in one workflow. ECOSIRE scopes, builds, installs, and supports it for your Odoo 17/18/19 environment.
Aucun paiement maintenant. Ceci envoie une demande de devis à notre équipe — nous vous recontacterons par e-mail avec les tarifs et les prochaines étapes.
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.
First-class `freight.shipment` model with its own `ir.sequence`, state machine (draft, booked, in transit, delivered, closed), and QWeb documents, linked to sale orders, purchase orders, and one-to-many `stock.picking` records
Multi-mode support (road, air, ocean, rail, courier) with mode-specific fields, so a single shipment carries the right data set for its transport type
Consolidation and de-consolidation: group multiple orders into one shipment or split one order across carriers, with package-level `freight.package` lines
Chargeable-weight and volumetric rating via `compute`/`@api.depends` methods on dimensions and weight — sell price and cost recompute automatically when packages change
`freight.rate` and `freight.charge.line` structure for base freight, fuel surcharge, and accessorial charges, separating carrier cost from customer sell price and exposing freight margin
Carrier assignment with booking references, house/master document numbers, and per-carrier default charge templates
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 2-4 weeks from confirmed scope, depending on how many carriers, document formats, and localizations are in play. Pricing starts from $299 (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.
Runs shipments for many clients across modes and carriers and needs consolidation, house/master documents, and per-shipment freight margin — none of which native delivery orders provide.
Ships finished goods to customers on Odoo and wants freight cost and sell price attached to each shipment, rating automated, and dispatch visible on one board instead of email and spreadsheets.
Needs a clean, upgrade-safe freight addon with proper models, security, and API surface they can maintain and extend, rather than brittle Studio fields bolted onto `stock.picking`.
Coordinates daily pickups and deliveries and needs milestone tracking, exception alerts, and POD capture tied to each load, with an at-a-glance kanban of what is booked, in transit, and delivered.
Achetez la licence sur ecosire.com et téléchargez le module ZIP All in One Freight Management depuis le tableau de bord de votre compte.
Extrayez le ZIP dans votre dossier de modules complémentaires personnalisés Odoo sur le serveur (ou téléchargez-le via Applications > Installer à partir du fichier sur Odoo.sh / runbot).
Activez le mode développeur, ouvrez les applications, cliquez sur Mettre à jour la liste des applications, recherchez All in One Freight Management et appuyez sur Installer.
Ouvrez le nouveau menu, collez votre clé de licence ECOSIRE, connectez toutes les informations d'identification externes (Shopify, Amazon, Stripe, etc.) et enregistrez.
Exécutez le test de connexion intégré, synchronisez vos 10 premiers enregistrements et planifiez le cron récurrent. Contactez le support si quelque chose échoue.
| Critère | ÉCOSIRE | Construction personnalisée | Concurrent | Odoo natif |
|---|---|---|---|---|
| Freight shipment object | First-class `freight.shipment` model with states, sequence, and documents | Possible, but you design and maintain the whole model yourself | Often a lighter shipment record with fixed assumptions | |
| Multi-mode & consolidation | Road/air/ocean/rail with consolidation across orders and carriers | Whatever you build; scope creep is common | Usually one or two modes, limited consolidation | |
| Freight rating & margin | Chargeable-weight/volumetric compute, cost vs sell, margin exposed | Build your own rating engine from scratch | Basic rate tables, margin often not modeled | |
| Fit to your workflow | Built to your confirmed scope, carriers, and documents | Fully bespoke — highest effort and cost | You adapt your process to the app's assumptions | |
| Security & multi-company | Dedicated access rules + record rules scoped by company/team | You implement and test the security matrix | Varies; multi-company support inconsistent | |
| Support & source handover | Full source, git repo, docs, training, support window | Depends entirely on your developer's handover | Vendor support tiers; source often closed | |
| Odoo version fit | Version-pinned build for 17.0/18.0/19.0, Community or Enterprise | You maintain compatibility yourself | Depends on vendor's release cadence | |
| Delivery model | Build-to-order, 2-4 weeks, fixed quote after scoping | Weeks to months, open-ended budget | Instant download, take-it-as-is |
This is a build-to-order module, so it is built for you after we agree the scope. Typical delivery is 2-4 weeks from confirmed scope. The exact timeline depends on the number of transport modes, carriers, document formats, integrations, and any data migration in play — all of which we pin down on the scoping call.
No. It is not an off-the-shelf apps.odoo.com download. ECOSIRE designs, builds, installs, and supports it for your specific Odoo environment and requirements. You receive installable source code and a git repository once your version is built and tested.
Pricing starts from $299 as an indicative single-company base-scope figure. On a short scoping call we confirm modes, rating rules, carriers, documents, integrations, and migration needs, then give you a fixed quote — no surprise invoicing. Drivers like multi-company operation, extra carrier/EDI integrations, deeper document localization, and historical data migration increase the quoted scope.
Every engagement includes a post-go-live support window for defect fixes and configuration questions. Because you receive the full source and git repository, you or your partner can maintain it, and we offer ongoing support or Odoo-version upgrade work (for example moving 17.0 to 18.0 or 19.0) as a separate arrangement.
We build and version-pin the module for Odoo 17.0, 18.0, or 19.0, on Community or Enterprise. If any capability depends on an Enterprise-only feature (advanced accounting, for example), we flag it during scoping so there are no surprises at install.
Native delivery carriers price a single parcel against a `stock.picking` and stop there — there is no shipment object, no consolidation, no freight margin, and no multi-mode rating. This module adds a real `freight.shipment` domain layer on top of Inventory and Sales, so a transport operation becomes a first-class record rather than a spreadsheet workaround.
Yes. The new models are exposed over Odoo's XML-RPC/JSON-RPC API, so carrier portals, EDI feeds, and customer tracking pages can create and update shipments programmatically. Specific carrier or EDI integrations are scoped and quoted based on the endpoints and data formats involved.

A build-to-order Business Central AL extension that maps your 3PL warehouses into native sales and purchase flows — sending fulfillment orders, ingesting ASN and shipment confirmations, and reconciling on-hand quantities against each 3PL's stock balances.

A build-to-order ERPNext app that lets 3PL operators bill each client for storage, handling, and value-added services with strict multi-owner inventory segregation and automated periodic invoicing. ECOSIRE builds, installs, and supports it for your warehouse.

A custom-built, two-way integration between your Shopify store and your 3PL or WMS. ECOSIRE builds, installs, and supports it — pushing orders, syncing inventory, writing back tracking, and routing by warehouse automatically.
A build-to-order Odoo freight and transport management module that unifies shipment planning, multi-mode freight rating, dispatch, and carrier tracking in one workflow. ECOSIRE scopes, builds, installs, and supports it for your Odoo 17/18/19 environment.