Employment Hero Planning Sync
Pull Employment Hero rosters into Odoo Planning shifts, mapped 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
The roster lives in one place
Rosters from the Employment Hero platform land in the Odoo Planning app as shifts, so planners stop rebuilding the same schedule a second time inside Odoo.
Tune the mapping from the interface
The endpoint, field mapping and pull job ship as data. Source paths and target fields are configuration rows you adjust to your organisation's payload, not a code deployment.
Re running never duplicates
Every shift is keyed by its Employment Hero id through the external id cross reference, so a second run updates the same slot in place and an unchanged roster is skipped.
Day in the life
A roster goes from Employment Hero to an Odoo shift
You point the pull job at your Employment Hero connection. The job reads the roster endpoint page by page, and for each roster it maps the start and end times into a Planning shift and resolves the assigned resource through the external id cross reference, so Planning shows the right employee. The note becomes the shift name. One bad roster is logged as an error line and the run carries on, ending in a partial state rather than aborting the batch. Run it again later and the same shifts reconcile in place instead of piling up duplicates. When your payload shape differs, you open the mapping and change a source path, no code, no redeploy.
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 Employment Hero id and a payload hash. A second run updates the same planning.slot in place; an unchanged roster is recorded as skipped, never duplicated.
Each roster is processed inside its own savepoint. A single record that fails to write is rolled back and logged as an error line while the rest of the batch continues, and the run ends in a partial state.
The roster endpoint is read page by page using the platform's page index and item per page parameters, stopping on a short or empty page, so a large roster list is pulled in full.
When a roster's resource has no external id link yet, the resource resolves to empty rather than crashing, so the shift is created and the employee links once the resource has been synced from the HR module.
Start and end times are marked required in the mapping, so a roster missing either is failed as its own error line instead of writing a half formed shift.
The per record hash folds in a fingerprint of the mapping, so after you change a source path or transformer the next run rewrites existing shifts instead of skipping them as unchanged.
Roster timestamps with an offset or a trailing Z are normalised to UTC before they are stored, so a shift near a day boundary lands on the correct datetime.
The external id cross reference is scoped per connection, so two connections that happen to hold the same roster id never cross bind to each other's shift.
What is inside
Built to do the job, end to end.
- Roster endpoint. Ships the roster list endpoint that is not in the base catalogue, configured for the platform's HR path with page style pagination and the data items envelope.
- Shift field mapping. A pull mapping for planning.slot with four lines: start datetime, end datetime, the resource resolved by external id, and the shift name from the roster note. Shipped with noupdate so an upgrade never overwrites your tuning.
- Pull sync job. A ready to run job that binds the endpoint and mapping to planning.slot, reads the external id from the roster id, captures the updated timestamp for conflict handling, and uses an Employment Hero wins conflict policy.
- Runs on the suite engine. Inherits idempotent upsert, the external id cross reference, per record isolation, pagination, and request retry with backoff from the Employment Hero sync engine it depends on.
- Automated test. Ships a test that drives the shipped mapping and job against a faked API, asserting a roster creates one shift attached to the right resource and employee.
Honest about the edges
What this does not do, so nothing surprises you.
- Pull only. This module brings Employment Hero rosters into Odoo Planning; it does not push Odoo shifts back to the platform.
- Covers rosters to planning.slot only. Employees and their resources are synced by the HR module this one depends on, and the resource link resolves through that data.
- The shipped sync job runs in full mode, re reading the roster list each run rather than fetching only changed rosters.
- It does not ship its own scheduled action; runs are triggered on demand or by a schedule you configure on the job.
- The starter mapping assumes a common roster payload shape. A different organisation payload may need source paths adjusted, which is a configuration change in the interface.
- Requires the Odoo Planning app and the Employment Hero HR and sync modules from this suite to be installed.
- Built and tested for Odoo 18 Community.
Employment Hero Planning Odoo, Employment Hero roster sync, roster to Odoo Planning shifts, planning.slot import Odoo 18, Employment Hero Odoo integration, workforce scheduling sync, shift import Odoo, Employment Hero HR connector, roster sync Odoo Community, data driven field mapping 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.
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 18 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 | 4083 |
| 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