Logistics Qatar Localisation Pack
Seeded Qatar ports, airports, customs offices and free zones for the logistics suite, ready the moment you install.
Why this module
Logistics Qatar Localisation Pack
Seeded on install
Four sea ports, two airports, four customs offices and three free zones load as data records the moment the module installs. No setup, no CSV import, no hunting for UN/LOCODE values before the first shipment file.
Codes that stay clean
UN/LOCODE on ports, IATA on airports and a code on every customs office and free zone are each database-unique. Records show as [CODE] Name and search by code or name, so the right port or office is one keystroke away.
Master data, not theatre
This pack is reference tables, views, menus and a two-tier access rule. It does not claim a customs EDI adapter, HS-code engine or billing workflow it does not contain. What installs is exactly what the screenshots show.
Day in the life
An operator opens a new Qatar import file.
Booking an ocean import into Doha, the operator picks the discharge port from the seeded list, Hamad Port shows as [QAHMD] Hamad Port with QTerminals as operator and its container and bulk terminal flags already set. The clearing customs house is chosen from the customs-office master, where Hamad Port Customs House sits under the General Authority of Customs (Al Nadeeb) as its parent authority, so the chain of responsibility is explicit. If the consignee delivers into Um Al Houl, its free-zone record carries the bonded flag and the QFZA regulator name, signalling the customs treatment without anyone retyping it. Every value the file references is a curated record, not free text, so two operators spell Mesaieed and Ras Laffan the same way every time.
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.
Each port carries its UN/LOCODE (QAHMD, QADOH, QAUMS, QARLF) under a database-unique constraint, so a duplicate location code is rejected at write time rather than quietly creating a second Hamad Port that splits your shipment history.
Customs offices form a self-referencing tree: port and airport customs houses point to a parent authority via an ondelete-restrict link, so you cannot delete the General Authority of Customs while a Hamad Port house still hangs off it. A computed is-authority flag and an ordering that floats authorities to the top keep the list readable.
Both Doha airports are seeded but distinguished honestly: Hamad International (DOH / OTHH) is cargo-capable, while the legacy Doha International (DIA / OTBD) ships with cargo-capable set false, so an air-freight booking surfaces the operational field and not the retired one.
Free zones carry an explicit bonded flag and their regulating authority. Ras Bufontas and Um Al Houl are flagged bonded under the Qatar Free Zones Authority, while Qatar Science and Technology Park (under Qatar Foundation) is not, so the customs treatment is data, not tribal knowledge.
IATA codes on airports and codes on customs offices and free zones each sit behind their own unique constraint, so an import or a hand-typed duplicate fails loudly instead of producing two records that point at the same real-world place.
What is inside
Built to do the job, end to end.
- Qatar sea ports. Seeded with Hamad Port (QAHMD, QTerminals), Doha Port (QADOH, Mwani Qatar), Mesaieed (QAUMS) and Ras Laffan (QARLF), each with UN/LOCODE, operator name and container, bulk and petrochemical terminal flags.
- Qatar airports. Hamad International (DOH / OTHH, cargo-capable) and the legacy Doha International (DIA / OTBD), each with IATA and ICAO codes and a cargo-capable flag, listed and searchable by IATA or name.
- Customs office hierarchy. General Authority of Customs (Al Nadeeb) and General Tax Authority as authorities, plus Hamad Port and Hamad International Airport customs houses linked to their parent authority, classified by office kind.
- Qatar free zones. Ras Bufontas, Um Al Houl (both bonded, under QFZA) and Qatar Science and Technology Park (under Qatar Foundation), each with code, bonded flag, regulating authority and website.
- Views, menus and access. List and form views for all four masters, grouped under a Qatar menu in the logistics master-data area, with a two-tier rule: operations users read the data, managers create and edit it.
Honest about the edges
What this does not do, so nothing surprises you.
- This is master reference data only. It does not create shipments, quotations, customs declarations, tracking events or invoices, those live in other modules of the suite.
- It requires and depends on eh_log_base; it will not install on its own and reuses that module's user and manager groups and master-data menu.
- There is no customs EDI, single-window or Al Nadeeb electronic-filing integration here. Al Nadeeb appears only as the name of a seeded customs-authority record.
- No HS-code or tariff catalogue, no VAT or duty calculation, no currency or public-holiday data is included in this pack.
- The seeded lists are a practical starting set of the main Qatar gateways, not an exhaustive registry of every facility, sub-office or zone.
- Records are global reference data with an active flag; the models carry no company_id, so they are shared across companies rather than per-company scoped.
- Content is English only, consistent with Apps Store listing rules; there are no bilingual document templates in this module.
Odoo 19 Qatar logistics, Qatar freight forwarding Odoo, Hamad Port UN/LOCODE, Qatar customs offices Odoo, Al Nadeeb customs Qatar, Qatar free zones QFZA, Ras Bufontas Um Al Houl, Hamad International Airport DOH, Qatar ports master data, Odoo Community logistics localisation, IATA ICAO airport master Odoo, GCC freight customs reference data
Languages
Available in 19 languages
The interface ships translated out of the box. Switch language in Odoo and the fields, menus, and messages follow.
Modules teams pair with this one.
Premium ERP Heritage modules that extend the same stack, each built to the same engineering bar.
Connect Odoo partner records to the Saudi SPL National Address service and the Wathq commercial registry
One click install of the full Employment Hero integration for Odoo Community, covering the connector, two way syn...
The Malaysia country pack for the ERP Heritage Employment Hero integration
A dependency free asynchronous job queue that runs long running and fan out work out of band of the request that...
Post Irish payslips to the general ledger on the Irish chart of accounts
Please log in to comment on this module