Logistics Kuwait Localisation Pack
Kuwait sea ports, airports, customs offices, and free zones as clean, coded reference data your logistics suite can point at from day one.
Why this module
Logistics Kuwait Localisation Pack
Loaded on install
Four ports, two airports, four customs offices, and two free zones seed themselves when the module installs. No spreadsheet imports, no hand-keying UN/LOCODE or IATA codes before your first quote or booking.
Codes that stay unique
UN/LOCODE on ports, IATA on airports, and office and zone codes are each enforced unique in the database, and every record searches and shows as [CODE] Name, so the right authority is one keystroke away.
Yours to keep
LGPL-3 source on disk. The seed data is editable, archivable, and extendable. Add a private terminal, retire a closed office, or rename in Arabic with translatable fields, all without forking the engine.
Day in the life
A Kuwait forwarder sets up a new sea-import lane.
On the day the logistics engine goes live, the operations lead opens the Kuwait master-data menus and finds Shuwaikh, Shuaiba, Doha Port, and Mubarak Al-Kabeer on Bubiyan already loaded, each carrying its UN/LOCODE and terminal-type flags. The customs team sees the General Administration of Customs sitting as the parent authority, with the Shuwaikh, Shuaiba, and Kuwait Airport customs houses parented underneath it, so the chain of responsibility is unambiguous. Kuwait International Airport is there for air freight with its IATA and ICAO codes, and the Kuwait Free Trade Zone and KSEZA are flagged as bonded with their regulating authorities named. Nobody had to research a port code or hand-build a customs hierarchy. The reference layer was simply present, ready for the operational modules to point at.
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 Kuwait port carries its UN/LOCODE (KWSWK, KWSAA, KWKWI, KWBUB) under a unique-code database constraint, so two records can never claim the same locode. Container, bulk, and petrochemical terminal capabilities are flagged per port rather than assumed.
Customs offices model a real authority tree. The General Administration of Customs is marked as the authority, and the port and airport customs houses reference it as their parent. That parent link is set to restrict on delete, so you cannot orphan a customs house by removing the authority above it.
Airports separate IATA from ICAO and carry an explicit cargo-capable flag, so a general-aviation field is not mistaken for a freight gateway. Kuwait International is flagged cargo-capable, the general-aviation airport is not.
Free zones carry an explicit bonded flag and a named regulating authority rather than a free-text guess, so the Kuwait Free Trade Zone at Shuwaikh and KSEZA are each tied to the body that governs them.
All seed records ship with noupdate set, so your local edits, archived offices, and added terminals survive module upgrades instead of being silently overwritten. An active flag lets you retire a record without deleting history.
Names and notes on every model are translatable, so an English working name and an Arabic display name can coexist on the same record without duplicate entries.
What is inside
Built to do the job, end to end.
- Sea ports. Model eh.log.l10n.kw.port, seeded with Shuwaikh (KWSWK), Shuaiba (KWSAA), Doha Port (KWKWI), and Mubarak Al-Kabeer on Bubiyan (KWBUB), each with operator, UN/LOCODE, and container, bulk, and petrochemical terminal flags.
- Airports. Model eh.log.l10n.kw.airport, seeded with Kuwait International (KWI / OKBK) and the Sheikh Saad Al-Abdullah general-aviation field, separating IATA and ICAO codes with a cargo-capable flag.
- Customs offices. Model eh.log.l10n.kw.customs.office, seeded with the General Administration of Customs as the authority plus Shuwaikh, Shuaiba, and Kuwait Airport customs houses parented beneath it, with office-kind, single-window URL, and helpline fields.
- Free zones. Model eh.log.l10n.kw.free.zone, seeded with the Kuwait Free Trade Zone at Shuwaikh and the Kuwait South Special Economic Zone Authority (KSEZA), each with a bonded flag and named regulating authority.
- Access control. Reuses the logistics base groups. Logistics users get read-only visibility of all Kuwait master data, while logistics managers get full create, edit, and archive rights. Menus live under the master-data section.
- Search and display. Every model resolves by code or by name and renders as [CODE] Name through a computed display name, so ports, offices, and zones are fast to find and unambiguous to read in any list or dropdown.
Honest about the edges
What this does not do, so nothing surprises you.
- This is a Kuwait reference-data and configuration pack, not an operational module. It does not create shipments, bookings, quotations, customs declarations, or tracking events by itself. Those belong to the operational logistics modules.
- It depends on the logistics base engine (eh_log_base) and does nothing useful installed on its own. The base engine must be present.
- The seed set covers Kuwait's principal commercial ports, airports, customs houses, and free zones. It is a practical working baseline, not an exhaustive registry of every facility or sub-office in the country.
- There is no EDI, no single-window API integration, and no live customs filing in this module. The single-window URL and helpline are reference attributes only.
- Codes reflect public UN/LOCODE, IATA, and ICAO references at time of release. You are free to correct or extend records locally, and your edits are preserved across upgrades.
Kuwait logistics master data, Kuwait ports Odoo, UN/LOCODE Kuwait, Shuwaikh port, Shuaiba port, Bubiyan Mubarak Al-Kabeer port, Kuwait International Airport KWI, Kuwait customs General Administration of Customs, Kuwait Free Trade Zone, KSEZA free zone, freight forwarding localisation Odoo 17, customs broker reference data, Odoo 17 Community logistics Kuwait, Kuwait IATA ICAO airport data, bonded free zone Kuwait
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.
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
Interactive drag and drop Gantt planner for Odoo 17 Community project tasks with a deterministic server side sche...
Employment Hero Connector is the integration core of the ERP Heritage Employment Hero suite, providing per compan...
The United Kingdom country pack for the ERP Heritage Employment Hero integration
Sync Employment Hero employees, departments and payroll bank details into standard Odoo Community HR over the pla...
Please log in to comment on this module