| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Discuss (mail)
• Invoicing (account) • Purchase (purchase) • Sales (sale_management) |
| Community Apps Dependencies |
Show
•
Carrier Portal
• Cold Chain • Container Management • Customs Broker • Dangerous Goods • Disputes and Variations • EDI Hub • Freight Forwarding • Last Mile • Logistics Dashboard • Logistics Qatar • Logistics Qatar Customs • Logistics Quotation • Logistics Suite Base • Project Cargo • Road Transport • Ship Agency • Track and Trace • Warehouse 3PL |
| Lines of code | 30865 |
| Technical Name |
eh_log_suite_qa |
| License | LGPL-3 |
| Website | https://www.erpheritage.com.au/ |
| Versions | 16.0 17.0 18.0 19.0 |
Qatar Logistics Suite
One install brings the full ERP Heritage logistics suite onto an Odoo 19 Community database, scoped to the State of Qatar with the Al Nadeeb single window adapter.
See it in action
One suite, one operational paneQuotations, freight, customs, transport, last mile, cold chain, containers, ship agency and project cargo, every engine reporting into one dashboard.
The forwarding boardThe freight desk reads its whole book in one screen, grouped by state with mode, lane and cargo on every card.
Every file wired to the suiteA job file links out to quotations, bills of lading, containers, bookings, customs, cold chain and disputes, one connected operation rather than isolated modules.
Why this module
Qatar Logistics Suite
Tested as a set, not assembled by hand
Every constituent module sits on the same Odoo 19 release line. The bundle manifest anchors the exact nineteen-module combination, so you skip the version-alignment work of stitching a logistics stack together yourself.
Single support contact across the suite
Freight, customs, transport, warehouse, EDI, and the Qatar packs all ship under ERP Heritage. Support, fixes, and upgrades come from one source instead of several, with no cross-vendor compatibility gaps to chase.
Qatar localisation included from the first click
The bundle pulls the seventeen engines plus Qatar master data and the Al Nadeeb customs adapter in a single action. No search-and-click loop across the store, no guessing which country pack pairs with which engine.
Day in the life
Quote to clearance, on one Qatar-scoped database
A forwarder confirms a logistics quotation in Doha. The margin, credit, and KYC guards pass, so the freight job is born from the sale order rather than typed in by hand. Sea legs route through Hamad Port; container free-time and demurrage accrue against gate movements. The customs declaration runs its state machine, validates HS lines, and submits through the Al Nadeeb single window adapter, which surfaces the real accepted or rejected status. Track events stream into an append-only log from carrier webhooks, the public tracking page updates, and the dashboard rolls quotes, freight, customs, and transport into KPI tiles. Every step is company-scoped and audit-logged.
Edge cases
The cases most modules quietly ignore.
In the shipped code today, each one a place where a cheaper module silently does the wrong thing.
Quotation pricing and freight jobs model sea, air, land, and multimodal legs, so a single shipment can be costed and tracked across mode changes rather than forced into one transport type.
Track events are written only through log_track_event() on the source record and cannot be deleted or edited in place. Carrier webhook ingest lands in one normalized event log that stays tamper-evident.
Outbound EDI builds its payload once and stores it. A failure increments retry_count and the same content is re-sent on retry, so the partner sees identical bytes. Past max_retries the row moves to a dead-letter state for an operator to resume or cancel.
Customs HS codes must be all-digit with length 2, 4, 6, 8, or 10, mapped to chapter, heading, subheading, and national levels. Malformed classifications are rejected at the constraint before a declaration can submit.
Each DG class carries an IMDG incompatibility list. The declaration's segregation detector scans its lines and flags incompatible class combinations as a warning before the shipper's declaration is issued.
Container chargeable days compute as max(0, days at destination minus free time days) against gate-in and gate-out movements, so demurrage and detention accrue from the equipment interchange history rather than manual counting.
Declarations move through draft, ready, submitted, queried, assessed, paid, cleared, and closed, with rejected and cancelled as terminal guards. Hard stops (missing HS lines) block the transition, and clearance posts the deferment debit.
Company scoping carries across the operational models suite-wide (present in seventy-six model files), with isolation rules applied so jobs, declarations, and billing stay within their company.
What is inside
Built to do the job, end to end.
- Freight forwarding engine. Sea, air, land, and multimodal jobs with HBL, HAWB, MBL, and MAWB documents, milestone tracking, a document checklist, and per-job cost and revenue ledger lines. Jobs are born from a confirmed quotation.
- Logistics quotation. Charge templates and multi-leg pricing with live margin, credit, and KYC guards that raise typed exceptions on hard failure at confirmation, plus an approval flow before downstream jobs are created.
- Customs broker plus Al Nadeeb. Declaration types, HS classification, deferment accounts and entries, and a full declaration state machine. The Qatar pack adds the Al Nadeeb single window adapter (declaration submit, status, health check) with fixture-backed offline tests and honest status surfacing.
- Road transport and last mile. Trips, drivers, vehicles, and proof of delivery for line-haul transport; wave planning, multi-stop dispatch, delivery attempt logs, and COD handling for B2C and B2B last-mile distribution.
- Container, cold chain, dangerous goods. Container depots, gate movements, leases, work orders, and demurrage and detention; cold chain profiles, runs, readings, and deviation tracking; dangerous goods UN number and class master with a segregation incompatibility detector.
- Ship agency, project cargo, 3PL, EDI, track. Port calls, Statement of Facts events, and Disbursement Accounts; project cargo convoys, route surveys, and permits; bonded 3PL warehouse with append-only movements and periodic billing runs; an EDI hub with retry and dead-letter; and a public track and trace page over a normalized event log.
Honest about the edges
What this does not do, so nothing surprises you.
- This is a meta-bundle. It carries no models or views of its own and ships an empty data list. All functionality comes from the nineteen modules it depends on, which install with it.
- Scoped to the State of Qatar. The country packs cover Qatar master data and the Al Nadeeb single window customs adapter; other countries are not included in this bundle.
- The Al Nadeeb adapter is built to the documented contract and ships with fixture-backed offline tests. Live single-window submission depends on credentials and connectivity to the regulator, which are configured per deployment.
- The Qatar customs pack delivers its logic through an adapter and seed data (declaration types, HS overlays, adapter profile) rather than its own model layer.
- Licensed LGPL-3 and free at this release. Installing the bundle installs all nineteen modules, so plan database scope accordingly.
- Engines are country-neutral by design. Regulator behaviour outside Qatar would require the matching country pack, which is not part of this listing.
Qatar logistics Odoo, Qatar freight forwarding, Al Nadeeb single window, Qatar customs broker Odoo, Hamad Port logistics, freight forwarding Odoo 19, customs declaration HS code, container demurrage detention, dangerous goods IMDG Odoo, 3PL warehouse billing, EDI EDIFACT X12 logistics, track and trace carrier webhook, ship agency disbursement account, Qatar Free Zones logistics, Odoo 19 Community logistics suite
Please log in to comment on this module