Logistics Oman Localisation Pack
Ready-to-use Oman master data: sea ports, airports, customs offices, and free zones, wired into the ERP Heritage logistics suite.
Why this module
Logistics Oman Localisation Pack
The actual Oman network, not placeholders
Sohar, Salalah, Sultan Qaboos (Muscat), Duqm and Khasab ports; Muscat, Salalah, Khasab, Duqm and Sohar airports; the Royal Oman Police Customs Department, Oman Tax Authority and per-port customs houses; and the Sohar, Salalah, SEZAD Duqm and Al Mazunah free zones. Codes are filled in: UN/LOCODE, IATA and ICAO.
No data entry before your first job
Install and the registers are populated. Each record carries the codes and flags operators reference (container, bulk and petrochemical terminal markers on ports, cargo-capable flags on airports, bonded markers on zones), so you stop transcribing port lists by hand.
Seeds survive upgrades, writes stay controlled
Records are loaded with noupdate so your edits are preserved across module updates, names and notes are translation-ready, and write, create and delete are limited to the logistics manager group while operators get read access.
Day in the life
Booking a box through Sohar
An operator builds a freight job for a container moving through Sohar. The port is already in the system as OMSOH with its container and bulk terminal flags set, the Sohar Port Customs House is on file under the Royal Oman Police Customs Department, and Sohar Free Zone (SFZ) is there with its bonded flag for the free-zone leg. Nothing to look up or type, the references are picked from the seeded lists and the job moves on.
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.
UN/LOCODE on ports, IATA on airports, and the code fields on customs offices and free zones each carry a database unique constraint, so two records cannot share a code even under concurrent or imported writes.
Customs offices link to a parent authority with a restrict delete rule, so a parent like the Royal Oman Police Customs Department cannot be removed while port or airport customs houses still reference it. The authority flag is computed from office kind, not hand-set.
All country records load with noupdate set, so a later module update will not overwrite edits you made to a seeded port, airport, office or zone.
Every record has an active flag, so a port, airport, customs house or zone that goes out of use can be archived out of pickers without breaking historical freight jobs that still reference it.
Free zones carry a bonded flag so the customs treatment of a free-zone leg (SFZ, Salalah, SEZAD Duqm, Al Mazunah) is explicit in the data rather than inferred.
What is inside
Built to do the job, end to end.
- Sea port register. Five Oman sea ports (Sohar OMSOH, Salalah OMSLL, Sultan Qaboos / Muscat OMMCT, Duqm OMDUQ, Khasab OMKHS) with UN/LOCODE, operator name, and container, bulk and petrochemical terminal flags. Searchable by code or name, list and form views included.
- Airport register. Five airports (Muscat MCT, Salalah SLL, Khasab KHS, Duqm DQM, Sohar) with IATA and ICAO codes and a cargo-capable flag, each with a unique IATA constraint.
- Customs offices. Six records covering the Royal Oman Police Customs Department, the Oman Tax Authority, and the Sohar, Salalah and Duqm port customs houses plus the Muscat airport customs house, organised by office kind and linked to their parent authority, with single-window URL and helpline fields.
- Free zones. Four free zones (Sohar SFZ, Salalah SLFZ, Duqm SEZAD, Al Mazunah MZN) with bonded markers, regulating authority and website, each with a unique code.
- Views, menus and access. List and form views for all four registers under a dedicated Oman menu inside the logistics master-data section, with read access for operators and full write reserved to the logistics manager group.
Honest about the edges
What this does not do, so nothing surprises you.
- This is master data only. It seeds reference registers and adds no shipment, quotation, customs-declaration or tracking workflow of its own. Those live in the operational modules of the logistics suite.
- It requires and extends eh_log_base, which must be installed. It is not a standalone application.
- It does not connect to Bayan, the national single window or any customs or EDI system, and ships no electronic-declaration or message exchange. Single-window URLs on customs offices are reference links only.
- It configures no tax, VAT-on-import or accounting setup. The Oman Tax Authority is present as a customs-office reference record, not as a tax configuration.
- Record names and notes are translation-ready (translate enabled), but the pack ships English values only, no Arabic translations are bundled.
- Coverage is the major national gateways listed, not an exhaustive register of every customs sub-station or minor facility in Oman. Records are editable and extendable.
Odoo 17 Oman logistics, Oman freight forwarding Odoo, Sohar port Odoo, Salalah port master data, Duqm SEZAD free zone, Oman customs offices Odoo, Royal Oman Police Customs, Oman Tax Authority logistics, UN/LOCODE Oman ports, Oman airport IATA codes, Oman free zones bonded, Odoo Community 3PL Oman, Khasab port, GCC freight localisation
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.
Real-time fiscalisation of customer invoices and credit notes with the Mauritius Revenue Authority e-Invoicing (E...
The Canada country pack for the ERP Heritage Employment Hero integration
Imports finalised pay run journals from the Employment Hero payroll platform (KeyPay) into Odoo Community account...
Please log in to comment on this module