Employment Hero Country Base
The shared country profile registry every Employment Hero country pack registers itself against.
Store price is USD 107 all-in: installing this also pulls the 2 paid ERP Heritage modules it depends on.
Why this module
Employment Hero Country Base
Every country pack needs the same anchor
Localisation modules each need somewhere stable to declare which country they cover and to hang country specific behaviour. Without a shared registry, each pack reinvents that anchor and they drift apart.
One thin registry, one record per country
This module defines eh.country.profile and nothing more. One record per country, a stable code, an order, an archive flag and an operator note. A database constraint guarantees a country is never registered twice.
Country packs stay consistent
Because every pack registers against the same profile model and the same security groups, behaviour is uniform across countries and a deployment sees its active localisations in one list.
Day in the life
What this looks like in practice
You install a country pack for a region you operate in. On install it creates its eh.country.profile record here, visible under the Employment Hero configuration menu in a single Country Profiles list. You can reorder the entries, archive a country you no longer run without deleting its history, and read the chatter to see who changed a profile and when. The country pack itself contributes the national identifier fields and any country tagged mappings, this base just holds the registry they register against.
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.
A database unique constraint on country_id blocks a second profile for the same country, so two packs or a careless import can never register the same country twice.
The active flag lets you retire a country pack from the working list while keeping its profile record and its chatter history intact, and the list view shows archived rows so nothing silently disappears.
The profile inherits mail.thread, so changes to the country, code, order and archive state are tracked in the chatter with the author and timestamp for a clean audit trail.
Standard Employment Hero users get read only visibility of the registry, while only the Employment Hero manager group can create, edit or remove profiles, so the registry is not edited by accident.
The sync engine mapping model carries an optional country_id, so a country pack can ship a mapping variant tuned to its country and a deployment can point a job at that variant while the generic mapping serves the rest. This base module enables that seam, the variants themselves ship with the packs.
A sequence field with a handle widget lets operators order the country list deterministically rather than relying on creation order.
What is inside
Built to do the job, end to end.
- eh.country.profile model. A single thin model with country_id, code, active, sequence and note. One record per country, ordered by sequence then code, inheriting mail.thread and mail.activity.mixin for tracking and activities.
- One per country constraint. A SQL unique constraint on country_id rejects any attempt to register the same country twice, keeping the registry the single source of truth for which localisations are installed.
- Configuration views and menu. A list view with inline handle reordering and an archive toggle, a form view with an operator notes section and chatter, and a Country Profiles menu under the Employment Hero configuration area.
- Two tier security. Access rules grant the Employment Hero user group read access and reserve create, write and unlink to the Employment Hero manager group.
- Built on the suite sync foundation. Depends on the Employment Hero sync module, whose mapping model exposes an optional country_id, which is the seam country packs use to ship country specific mapping variants.
Honest about the edges
What this does not do, so nothing surprises you.
- This is a foundation module. On its own it adds no national identifier fields, no validation and no mappings. Those arrive with the individual country packs that depend on it.
- It does not perform sync, webhook handling, queuing or retries. Those capabilities live in the connector, sync engine, queue and webhook modules of the suite, not in this module.
- It does not extend hr.employee. Country specific employee fields are added by each country pack through its own model inherit.
- It ships no country profile records itself. Each country pack creates its own profile on install.
- Targets Odoo 17 Community. Enterprise is not required and not used by this module.
Employment Hero Odoo integration, Odoo 17 country localisation, Employment Hero country pack, Odoo HR country profile, Employment Hero connector suite, Odoo Community HR localisation, national identifier fields Odoo, Employment Hero sync mapping, Odoo 17 Employment Hero, ERP Heritage Employment Hero
Need this fitted to the way you work?
ERP Heritage delivers end to end Odoo work: Odoo Implementation, Customization and Development, Integration, Migration, Consultation, Support and Training. We help teams put this module into production, shape it to their process, and keep it running.
We work with businesses across Australia (Melbourne, Sydney, Brisbane, Perth, Adelaide, Canberra) and the Middle East (Dubai, Abu Dhabi, Riyadh, Jeddah, Doha, Kuwait City, Muscat). Start a conversation at erpheritage.com.au or email info@erpheritage.com.au.
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...
Sync certifications, qualifications and employee document metadata from the Employment Hero people platform into...
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
Discuss (mail)
|
| Community Apps Dependencies | Show |
| Lines of code | 3626 |
| Technical Name |
eh_hero_country_base |
| License | OPL-1 |
| Website | https://www.erpheritage.com.au/ |
Odoo Proprietary License v1.0 This software and associated files (the "Software") may only be used (executed, modified, executed after modifications) if you have purchased a valid license from the authors, typically via Odoo Apps, or if you have received a written agreement from the authors of the Software (see the COPYRIGHT file). You may develop Odoo modules that use the Software as a library (typically by depending on it, importing it and using its resources), but without copying any source code or material from the Software. You may distribute those modules under the license of your choice, provided that this license is compatible with the terms of the Odoo Proprietary License (For example: LGPL, MIT, or proprietary licenses similar to this one). It is forbidden to publish, distribute, sublicense, or sell copies of the Software or modified copies of the Software. The above copyright notice and this permission notice must be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
Please log in to comment on this module