Employment Hero Sync Engine
A reusable, auditable sync engine that keeps Odoo and the Employment Hero platform in step, idempotently and safely.
Store price is USD 98 all-in: installing this also pulls the 1 paid ERP Heritage module it depends on.
Why this module
Employment Hero Sync Engine
Re run without duplicating
An external id cross reference keys every synced record to its Employment Hero id and a payload hash, so re running a job updates in place and skips records that have not changed. No accidental duplicates, no re writing unchanged rows.
One bad record does not stop the run
Each record is processed in its own savepoint. A failure is recorded as an error line and the run carries on to a partial state, with batched commits so progress is never lost on a crash midway through a large fetch.
Mapping is config, never eval
Dotted source paths map to Odoo fields through a registry of named transformers. No arbitrary code is stored or run. Edit a mapping in the UI and the per record hash changes, so existing records are correctly rewritten on the next run.
Day in the life
A nightly delta sync that you can trust unattended
The daily scheduled run picks up the jobs you flagged. Each one reads only the records changed since it last succeeded, maps them through your configured field mapping, and upserts by external id. A handful of records carry malformed data; those fail in isolation, land as error lines on the run, and the delta cursor holds short of them so they are tried again tomorrow instead of being lost. Everything that succeeded is committed, the run shows created, updated, skipped and failed counts, and you open the run to see exactly what happened to each record. Before changing a mapping you hit dry run first and read the preview, no writes, then run it for real.
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 repeated delivery for the same record is a no op: the external id cross reference finds the existing link and the matching payload hash skips it, so a webhook replay or a re run never duplicates.
A webhook triggered update is forced to newest wins. A snapshot with no usable source timestamp cannot prove it is newer, so it is skipped rather than allowed to overwrite a fresher record.
Each record runs in its own savepoint. An IntegrityError on one record rolls back only that record, is logged as an error line, and the rest of the batch still commits.
The delta cursor advances only to the highest timestamp that actually succeeded and never past a failed record, so a failure or a concurrent change is re fetched next run instead of being skipped forever.
A create carries a stable idempotency key per Odoo record and an update keys on the payload hash, so a retried write is deduplicated by the platform rather than creating a second record.
On push, a payload that is byte for byte the same as the last successful push is skipped, so a two way job does not re send every record every run.
A delete event archives the linked record when the model supports it, otherwise unlinks it, and severs the cross reference. A blocked hard delete is kept and recorded as skipped rather than failing forever.
A display mask or a key unavailable placeholder is never pushed outbound, so a masked identifier can never overwrite the real upstream value.
The per record hash folds in a fingerprint of the mapping, so adding a line or changing a transformer correctly forces existing records to be rewritten on the next run instead of skipped as unchanged.
What is inside
Built to do the job, end to end.
- Sync jobs. A job binds an endpoint, a mapping and a target model with policy knobs for direction, mode, batch size and conflict resolution. Run a job manually, on the daily schedule, or as a dry run, and view its run history. Domain modules ship jobs as data and you can add or tune them in the UI.
- Field mappings. Each mapping says how one Employment Hero resource maps onto one Odoo model, line by line, with a named transformer per field and optional per company and per country variants. Lines can be pull only, push only or both, so an identifier the platform owns is never overwritten by a local value.
- External id cross reference. A dedicated model links each Odoo record to its Employment Hero id per connection, storing the source timestamp, the last pulled payload hash and the last pushed payload hash. This is what makes the engine idempotent, delta aware and conflict aware.
- Sync runs and lines. Every run records counts, timing and a per record line that says whether each record was created, updated, skipped, deleted or errored, and why. The history lives on the run, not in the chatter of every synced record.
- Transformer registry. Built in transformers cover trim, number, boolean, date and datetime, JSON value maps, country and currency codes, relation by field or by external id, and sub lines from a nested array, each with a reverse for push. Numbers and unmapped enums fail loudly rather than guess.
- Scheduled run and master switch. A daily cron runs the jobs you flag as scheduled, gated by a single enable switch in Settings so you can pause all automated syncing at once without touching individual jobs.
Honest about the edges
What this does not do, so nothing surprises you.
- This is a pull first engine with a working push leg. The Employment Hero platform is the system of record on pull, and a two way job applies a separate push policy outbound.
- It reads and writes through the Employment Hero connection provided by the base module. Network transport, OAuth token refresh, rate limiting and retry with backoff live in that base layer, not in this engine.
- It does not receive HTTP webhooks itself. It provides the targeted single record sync path that webhook delivery uses; the webhook receiver, signature verification and event queue are a separate module in the suite.
- Field mappings ship as configurable defaults from the domain modules. Mapping a model the suite does not already cover means defining its endpoint, mapping lines and target fields yourself.
- Conflict resolution is policy based, not a merge UI. It decides which side wins per record using timestamps and hashes; it does not present field level conflicts for manual reconciliation.
- Pagination, delta filtering and timestamp formats depend on what the endpoint exposes. A job needs a source updated timestamp path to use delta mode and timestamp based conflict policies.
Employment Hero Odoo integration, Odoo 18 sync engine, Employment Hero sync, HR data synchronisation Odoo, idempotent upsert Odoo, external id cross reference, field mapping engine Odoo, delta sync Odoo, conflict resolution sync, KeyPay Odoo sync, Odoo HR integration, two way sync Odoo
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...
The Australia country pack for the ERP Heritage Employment Hero integration
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 | 3532 |
| Technical Name |
eh_hero_sync |
| 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