Employment Hero Planning Sync
Pull people platform rosters into Odoo Planning shifts, configured as data and tunable without code.
Store price is USD 196 all-in: installing this also pulls the 3 paid ERP Heritage modules it depends on.
Why this module
Employment Hero Planning Sync
Stop rebuilding the roster twice
Rosters from the people platform land in Odoo Planning as shifts, so the schedule lives in one place instead of being re keyed by hand.
Mapping you tune from the UI
The roster endpoint, field mapping and sync job ship as data. Adjust source paths to match your organisation's payload from the user interface, no module edit required.
Reconcile, never duplicate
Every shift is keyed by its upstream id through the external id cross reference, so running the job again updates the existing slot rather than creating a second one.
Day in the life
A planner keeps Odoo shifts in step with the roster
Rosters are built in the Employment Hero people platform. Run the roster sync job and each roster arrives in Odoo Planning as a shift, with start and end times from the payload and the slot attached to the right employee resource. Run it again after the roster changes upstream and existing shifts are updated in place, new ones are created, and nothing is duplicated. Any record that fails to map is logged on its own line and the rest of the run continues, so one bad roster never blocks the batch. The mapping stays editable, so when your organisation's payload field names differ you adjust the source paths in the user interface and run again.
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 shift is keyed by its upstream roster id through the external id cross reference. Re running the job updates the linked slot instead of inserting a duplicate, and an unchanged payload is recorded as a skip.
Every record is processed inside its own savepoint. A roster that fails to map is written as an error line and rolled back on its own, the run continues, and it ends in a partial state rather than aborting the whole batch.
The per record change hash folds in a fingerprint of the mapping. Edit a source path or transformer and existing shifts are rewritten on the next run instead of being skipped as unchanged.
The roster endpoint is fetched page by page until a short page ends it. If a hard page cap is reached the run logs a loud truncation warning telling you to narrow the query, rather than silently dropping rosters.
The roster's resource reference is resolved through the cross reference, scoped to the connection so two connections holding the same upstream id never cross bind. Planning then derives the employee from that resource.
The shipped mapping carries upgrade safe flags, so source paths you tune to your organisation are not overwritten when the module is updated.
Links are stored per connection, and a connection belongs to a company. A job runs against the default connection for its product and company, keeping companies separate.
Underlying API calls retry transient failures and rate limit responses with exponential backoff plus jitter, honour a server Retry-After header within a safe clamp, and only then raise.
What is inside
Built to do the job, end to end.
- Roster endpoint as data. Ships the rosters endpoint for the HR platform path, with page style pagination, a 100 item page size and an items path that reads the wrapped response envelope.
- Planning shift mapping. Maps roster start and end to the slot datetimes through an ISO datetime transformer, the note to the slot name, and the resource through the external id cross reference. Marked upgrade safe so your edits persist.
- Roster pull sync job. One pull job from the people platform into planning.slot, keyed by the roster id with an updated at path, and a conflict policy that treats the upstream copy as authoritative on pull.
- Per run audit. Each run records counts for fetched, created, updated, skipped and failed, with a per record line carrying the operation, the upstream id and any error message.
- Built on the shared engine. Rides the ERP Heritage Employment Hero sync engine for the cross reference, mapping transformers, conflict handling and the resilient API client, so this module stays pure configuration.
Honest about the edges
What this does not do, so nothing surprises you.
- Sync is one direction only, from the Employment Hero people platform into Odoo Planning. This module does not push Odoo shift changes back upstream.
- It syncs rosters into planning.slot only. Other people platform entities such as employees, leave or timesheets are handled by other modules in the suite.
- Employees and their resources must be synced first by the HR module, because the shift to resource link resolves through the external id cross reference. A roster whose resource is not yet linked will not attach to an employee.
- The shipped mapping is a starter keyed to a common payload shape. If your organisation's roster fields differ you must adjust the source paths in the user interface before the sync matches your data.
- This module ships no scheduled cron of its own. The roster job is run on demand or wired to a schedule you configure, and runs in full mode unless you switch it to delta.
- Requires the eh_hero_hr module and the Odoo Planning app, and a configured connection to the people platform.
- Webhook driven single record pull and outbound push exist in the underlying engine but are not wired by this roster job.
employment hero planning, employment hero roster sync, odoo planning integration, roster to planning shift, workforce scheduling odoo, shift sync odoo 17, employment hero connector, planning slot import, hr platform integration, people platform roster, external id matching, idempotent sync, configurable field mapping, odoo workforce planning, roster pull sync
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.
Accept ZainCash wallet payments in Iraq at your Odoo checkout, on the ZainCash Payment Gateway v2 with OAuth2, re...
Sync Employment Hero ATS recruitment job openings into the standard Odoo Recruitment app, mapping each opening on...
The New Zealand country pack for the ERP Heritage Employment Hero integration
The complete ERP Heritage Employment Hero integration in one install
Sync timesheet entries from the Employment Hero people and payroll platform into the standard Odoo Timesheets app...
Real-time MRA fiscalisation for Point of Sale receipts in Odoo 17 Community, mapping each paid POS order to the M...
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Planning (planning)
• Employees (hr) • Discuss (mail) |
| Community Apps Dependencies | Show |
| Lines of code | 4095 |
| Technical Name |
eh_hero_ent_planning |
| 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