Odoo Integration Guide for SkyPlanner APS Production Scheduling

Plan for the removal now. Odoo has scheduled XML-RPC and JSON-RPC for removal in Odoo 22 (fall 2028) and Odoo Online 21.1 (winter 2027). Build on JSON-2 for 19.0 and isolate the RPC path behind one adapter for older databases, so an upgrade is a single change. Custom controllers with @route(type='jsonrpc') are not affected by the removal.

Authentication

Create a dedicated integration user with read access to Manufacturing and Inventory and write access to work orders. Generate its key under Preferences > Account Security > New API Key. On 19.0, keys last at most three months, so the middleware needs key rotation and an alert on authentication failures. Without them, an expired key stops the sync unnoticed. On the SkyPlanner side the REST API uses JWT, so the middleware holds both credentials.

Every JSON-2 call runs in its own SQL transaction, so a write spread over several calls is not atomic. Write per work order and log each result.

Events

Odoo pushes changes through automation rules. A rule on mrp.production or mrp.workorder with the trigger On create and edit and the action “Send Webhook Notification” sends a POST with the selected fields to a URL. Build the rule in Studio, or in developer mode from the Automation Rules form. Pair it with a scheduled search_read poll on write_date to catch imports and anything the rule missed. In the other direction, SkyPlanner webhooks push schedule and state changes as they happen.

Field names differ between versions. On 19.0 each database lists its models, fields and methods at /doc; on older versions, call fields_get. Map from there, not from memory.

“ POST /json/2/mrp.workorder/write Authorization: bearer <api-key> {"ids": [4711], "vals": {"date_start": "2026-11-03 06:00:00", "date_finished": "2026-11-03 09:30:00", "workcenter_id": 7}} “

JSON-2 takes every method argument by name plus ids and context, so write(vals) becomes the vals key. On 16.0 to 18.0 the same call runs as execute_kw(db, uid, key, 'mrp.workorder', 'write', [[4711], vals]) over XML-RPC or JSON-RPC, and on 16.0 the keys are date_planned_start and date_planned_finished. Datetimes go in UTC. A few rules keep the write clean:

• Send both dates in the same call.
• Add workcenter_id only when the engine chose an alternative machine.
• Write only scheduling fields, never quantities or BoMs.

Writing the dates moves Odoo’s own work center booking, so Odoo’s planning views show SkyPlanner’s plan.

Shop floor back to Odoo. Operators log work in SkyPlanner Mobile Confirmations. For each confirmation the integration calls create on mrp.workcenter.productivity (JSON-2: POST /json/2/mrp.workcenter.productivity/create with vals_list). It fills workorder_id, workcenter_id, date_start, date_end and a loss_id of type Productive, and labor time and costing post in Odoo.

When an operation is complete, the integration sets the produced quantity and calls button_finish on the work order. The last work order leaves the MO ready for button_mark_done. Each confirmation is posted once, and its Odoo record id is kept with the SkyPlanner timelog, so a retried webhook never creates a second Time Log.

Plants on the Enterprise Shop Floor app reverse this: SkyPlanner reads work order state and qty_produced, and Autopilot reschedules automatically when production changes.

Ownership. Write the rules down before go-live:

Planners stop pressing Plan and Unplan in Odoo on MOs that SkyPlanner schedules. Otherwise Odoo books its own slots over SkyPlanner’s dates.

• Renamed date fields. Up to 16.0, date_planned_start and date_planned_finished held the plan and date_start/date_finished held actuals. From 17.0, date_start and date_finished are the planned dates. A mapping copied from a 16.0 project silently reads actuals as plan on 17+.
• Work order dates are bookings. On 19.0, date_start and date_finished on mrp.workorder are computed from a resource.calendar.leaves record (leave_id) on the work center calendar. Writing the dates on the work order updates that booking. Never write into the leave table directly.
• Started work orders block Unplan. Odoo refuses to unplan an MO when “Some work orders have already started”. Skip work orders in progress or done on write-back and only move what has not started.
• Durations drift. Operations set to Computed take their duration from the last work orders (10 by default), scaled by Time Efficiency. Set them to Fixed for the trial, or accept moving inputs. Operations live on each BoM, with no shared routing master, so every BoM needs its own clean-up.
• Broken calendars. Every work center needs a working-hours calendar. Odoo’s own planner searches up to 700 days ahead and then stops with “Impossible to plan the workorder”. Fix calendars before the first load.
• Units of measure. mrp.bom.line carries its own product_uom_id, which can differ from the product’s stock unit. Convert before checking material availability.

The write-back is what turns the integration into daily value. Once it runs:

• Odoo work orders carry real dates. The Arcturus AI engine sequences every open MO in seconds, and its dates and workstation choices land on mrp.workorder, where Odoo’s planning views show them.
• Nobody replans by hand. Autopilot reschedules automatically when production changes, and the webhook pushes the new dates to Odoo.
• The shop floor closes the loop. Operators log work on phone or tablet with Mobile Confirmations, Production Timer and Quick Log Mode, and Time Logs post to Odoo for stock and costing. Scheduling and execution run in one tool, on Community as well as Enterprise.
• The schedule holds constraints Odoo does not. A setting time matrix sets sequence-dependent changeovers per product pair. Tools are finite resources shared between machines, and a job can take several operators at once. The engine turns to alternative machines or personnel when the primary is unavailable. The dates written back to mrp.workorder respect all of them.
• Material arrival drives the plan. Stock on hand and open Odoo purchase orders feed material-driven scheduling. Ordered components count as available on the PO delivery date, and stock updates when the PO is marked Delivered. Each job is checked against what is in the warehouse and what is on its way.

You can judge the schedule before any integration work. Start the 30-day free trial on CSV exports and see your own Odoo work orders on the Gantt, with up to 20 workstations and no credit card. Pricing is from 199 € per month with 5 workstations included, billed monthly, cancel any time. The integration is quoted up front for your process and needs, together with your plan, so you see the full cost before you start. See features and customers, or book a demo.