End-to-end air/ocean/land freight forwarding in Odoo — shipments, containers, customs and multi-party billing. Built to order by ECOSIRE. One-time license from $799.00 USD for Odoo 17, 18, 19 — includes 12 months of updates and support.

End-to-end air/ocean/land freight forwarding in Odoo — shipments, containers, customs and multi-party billing. Built to order by ECOSIRE.
现在无需付款。此操作会向我们的团队发送报价请求——我们会通过邮件跟进价格和后续步骤。
Freight Forwarding Management is a build-to-order Odoo module that ECOSIRE designs, builds, installs and supports for your forwarding operation — it is not an off-the-shelf apps.odoo.com download you install yourself. After purchase, our Odoo engineers scope your process, then deliver a fully working forwarding app on your Odoo 17, 18 or 19 database within a typical 2–4 week lead time.
Direct, House (HBL) and Master (MBL) shipment structures with parent/child consolidation so multiple house shipments roll up under one master co-load
Air, ocean (FCL and LCL) and land mode handling on a single shipment model, with mode-aware fields and validation for each transport type
Container and carton capture recording gross/net weight, length/width/height dimensions, package counts and seal numbers per unit
Computed chargeable weight, volumetric weight, total CBM and TEU counts via @api.depends fields that recalculate as cargo is entered
Dated tracking event timeline (booking, gate-in, loaded, departed, arrived, customs cleared, delivered) recorded per shipment
Branded, tokenized customer tracking page where consignees self-serve live status without a login or an email to your desk
At its core is a dedicated shipment model built on Odoo's ORM (models.Model) that mirrors how forwarders actually work: Direct, House and Master (HBL/MBL) shipment structures with parent/child links so you can consolidate multiple house shipments under one master and see the full co-load at a glance. Each shipment carries mode-aware fields for air, ocean (FCL/LCL) and land, with computed fields driven by @api.depends — chargeable and volumetric weight, total volume, teu counts and margin roll up automatically as you capture containers and cartons with their weights and dimensions.
Operational visibility is first-class. Dated tracking events (booking confirmed, gate-in, loaded on board, departed, arrived, customs cleared, delivered) are recorded on a timeline and surfaced on a branded customer tracking page so your clients self-serve status instead of emailing your desk. Customs and compliance data — HS codes, incoterms, declaration references, ports of loading and discharge — live on the shipment and flow into QWeb PDF documents such as the house bill of lading, cargo manifest and arrival notice.
Billing is where forwarders lose money, so the module models it correctly: one customer invoice plus multiple vendor bills per shipment. Charge lines (ocean freight, THC, documentation, customs clearance, haulage, insurance) capture buy rate and sell rate per line, compute margin, and post to Odoo Accounting with the right analytic account — giving you true per-shipment profitability instead of a monthly guess.
Access is locked down with ir.model.access.csv and record rules so operations, accounts and management each see only what they should, and multi-branch record rules keep separate offices isolated. Automated actions handle the repetitive work — nudging when an ETA passes without a gate-in event, or flagging shipments missing a customs reference. Everything is exposed over Odoo's XML-RPC / JSON-RPC API so your website, carrier portals or a customer app can read shipment status and push tracking events. The module works on Odoo Community and Enterprise; where a feature benefits from Enterprise (studio-style approvals, advanced accounting analytics), we tell you up front rather than assume your edition.
Because ECOSIRE builds it, you get code written to Odoo standards — a clean __manifest__.py with pinned dependencies, upgrade-safe migrations, and views in XML/OWL that feel native — plus documentation, admin and user training, and a post-go-live support window. You own the source. No lock-in, no per-shipment SaaS fee.
Runs the ops desk moving air, ocean and land shipments and wants Direct/House/Master consolidation, a live tracking timeline and exception alerts inside Odoo instead of across spreadsheets and email threads.
Consolidates cargo under master bills and needs accurate container, TEU and chargeable-weight rollups plus a self-serve tracking page for downstream agents and shippers.
Manages HS codes, incoterms, declaration references and port data per shipment, and needs QWeb manifests, arrival notices and clean audit trails tied to the same record the ops and accounts teams use.
Owns billing and margin, and needs the one-customer-invoice, many-vendor-bills model with buy/sell charge lines posting to Odoo Accounting so per-shipment profitability is real, not a monthly reconciliation.
在 ecosire.com 上购买许可证并从您的帐户仪表板下载 Freight Forwarding Management for Odoo 模块 ZIP。
将 ZIP 解压到服务器上的 Odoo 自定义插件文件夹中(或通过“应用程序”>“从 Odoo.sh / runbot 上的文件安装”上传)。
激活开发者模式,打开应用程序,单击更新应用程序列表,搜索 Freight Forwarding Management for Odoo,然后按安装。
打开新菜单,粘贴您的 ECOSIRE 许可证密钥,连接任何外部凭据(Shopify、Amazon、Stripe 等),然后保存。
运行内置连接测试,同步前 10 条记录,并安排定期 cron。如果出现任何问题,请联系支持人员。
| 标准 | 伊科西尔 | 定制建造 | 竞争对手 | 奥杜本机 |
|---|---|---|---|---|
| Direct/House/Master shipment structures with consolidation | Possible but you design the data model from scratch | Varies by app; consolidation often partial or absent | ||
| Air / ocean (FCL & LCL) / land mode handling in one model | Depends on how you scope it | Often mode-specific or ocean-only | ||
| Container/carton capture with weight & dimensions and computed CBM/TEU | You build the @api.depends compute logic yourself | Sometimes, quality varies | ||
| One customer invoice + multiple vendor bills per shipment with buy/sell margin | Buildable but billing edge cases are hard to get right | Rarely modelled this precisely | ||
| Dated tracking events + branded self-serve customer tracking page | Extra build effort for the public page | Some apps include tracking, few a public page | ||
| Fits your exact process (fields, charges, branches, roles) | ||||
| Built, installed and supported for you with training | Only if you hire a developer separately | |||
| You own the source code, no per-shipment SaaS fee | Depends on vendor licence |
This is a build-to-order module, not an instant apps.odoo.com download. After purchase we run a short scoping session, then build, install and test it on your Odoo 17, 18 or 19 database. Typical lead time is 2–4 weeks depending on how much customs, billing and integration detail your workflow needs. You get progress checkpoints along the way, and nothing is claimed as 'done' until it runs on your environment.
Every build includes a defined post-go-live support and bug-fix window for issues, questions and minor adjustments. Because you receive the full source code and own it, there are no per-shipment SaaS fees. We keep the module upgrade-safe across Odoo 17/18/19, and when you plan a version upgrade or want new capabilities, we quote that as a scoped follow-on rather than locking you into a subscription.
The core forwarding features — shipment structures, containers, tracking events, customs fields, QWeb documents and the multi-party billing model — run on both Odoo Community and Enterprise. A few conveniences lean on Enterprise (for example advanced accounting analytics or studio-style approvals). During scoping we tell you exactly which edition each feature needs so there are no surprises, and we build around whatever edition you run.
Each shipment carries charge lines with a buy rate and a sell rate. Sell lines aggregate into a single customer invoice; buy lines become vendor bills against the relevant carriers and subcontractors — so a shipment can have several vendor bills but one customer invoice. Margin computes per line and per shipment via @api.depends fields, and everything posts to Odoo Accounting with analytic accounts, giving you true per-shipment profitability.
Yes. The module exposes shipment and tracking data over Odoo's standard XML-RPC / JSON-RPC API, and ships a branded, tokenized customer tracking page. Your web team, a carrier portal or a mobile app can read status and push new tracking events programmatically. We hand over sample API calls and integration notes as part of the deliverables.
Where the data is available in spreadsheets or a legacy system, we import your charge catalogue, ports, incoterms and open shipments as part of setup. We scope migration during the kickoff — the cleaner the source data, the more we can bring across. Historical closed shipments can usually be loaded as reference records so your reporting has continuity from day one.
End-to-end air/ocean/land freight forwarding in Odoo — shipments, containers, customs and multi-party billing. Built to order by ECOSIRE.