Integrations / ERP / MRPeasy
MRPeasy Integration Guide for Production Scheduling with SkyPlanner APS
This MRPeasy integration guide shows consultants and IT teams how to connect MRPeasy to SkyPlanner APS. SkyPlanner integrates with MRPeasy in both directions over the MRPeasy REST API:
- Manufacturing orders, routings, BOMs, workstation groups, workstations, items, stock and purchase orders flow in.
- Planned dates and progress are written back to each Manufacturing Order.
- SkyPlanner webhooks push schedule changes as they happen.
SkyPlanner has been integrated with MRPeasy in customer projects. The SkyPlanner team configures the integration to your MRPeasy setup during onboarding and supports it after go-live. This guide is for consultants and developers who want to take part, or to build on SkyPlanner’s documented REST API (API reference) themselves.
The MRPeasy REST API: v1 and v2
MRPeasy is one cloud product with no on-premises versions, so every customer runs the same API. Two versions exist:
- REST API v1 (OpenAPI 1.0, server
https://api.mrpeasy.com/rest/v1) is the production API. It covers/items,/boms,/routings,/manufacturing-orders,/work-centers,/work-center-types,/customer-orders,/purchase-orders,/stock/inventory,/lots,/unitsand production reports such as/report/production/operations. - REST API v2 (OpenAPI 2.0.0, server
https://api.mrpeasy.com/rest/v2) is in early development. It adds/workstation-groupswithwork_hoursandholidays,/workstationswithproductivityandidle,/inventory,/stock-movementand PATCH. Manufacturing orders stay on v1.
Mind the naming. A Workstation group in the MRPeasy UI is work-center-types in v1 (type_id). A Workstation is work-centers (center_id). Routing operations point to a group through type_id, not to a machine.
The API comes with MRPeasy’s Unlimited plan, for paying accounts. MRPeasy also states that “Our Support Department cannot help you using the API.” So the integration needs an owner: SkyPlanner, your MRPeasy consultant or your developer. The SkyPlanner team takes on exactly that work during onboarding.
Authentication and limits
MRPeasy uses HTTP Basic authentication: Authorization: Basic base64(api-key:api-secret). The key and secret are created under Settings → Integration → API access. Clearing the key disables the API.
The limits shape the sync design:
- One concurrent request per client: requests are processed sequentially.
- At most 100 requests per 10 seconds. Above that, the API returns 429.
- Lists return 100 records by default and up to 1,000 with the
Rangeheader.Content-Rangein the response gives the total.
On the SkyPlanner side, the REST API authenticates with an API token (SkyPlanner Settings > API) and is documented in Swagger/OpenAPI. The integration tutorial walks through the first calls.
Events and polling
MRPeasy’s pricing page lists “API, webhooks (for paid accounts)”, but the v1 and v2 specs document no webhook events for manufacturing orders. The integration therefore polls MRPeasy incrementally:
- Manufacturing orders filtered to Not scheduled (15), Scheduled (20), In progress (30) and Paused (35).
- Purchase orders and inventory on a schedule, or before each schedule run.
- Master data on change, or nightly.
Sequential, filtered polling stays well inside the 100-requests-per-10-seconds limit. In the other direction, SkyPlanner’s own webhooks push schedule changes as they happen, so the write-back side is event-driven.
Data mapping
| MRPeasy object (endpoint) | SkyPlanner object | Direction | Frequency |
|---|---|---|---|
Item, Unit of measurement (/items, /units) | Products and materials | MRPeasy → SkyPlanner | Initial load, then nightly |
BOM with components (/boms) | Product structure, subproducts, materials per product | MRPeasy → SkyPlanner | Initial load, then on change |
Routing operations (/routings): type_id, fixed_time, variable_time, variable_quantity | Process steps with durations, setup times, batch size | MRPeasy → SkyPlanner | Initial load, then on change |
Workstation group (/work-center-types; v2 /workstation-groups) | Workstation groups, shifts | MRPeasy → SkyPlanner | Initial load, rarely after |
Workstation (/work-centers; v2 /workstations: productivity, idle) | Workstations, efficiencies, absences | MRPeasy → SkyPlanner | Initial load, daily for idle time |
Manufacturing Order with operations, due_date (/manufacturing-orders) | Orders and jobs | MRPeasy → SkyPlanner | Polling every few minutes |
Inventory, Stock lots (/stock/inventory, /lots) | Stock balances | MRPeasy → SkyPlanner | Hourly or per schedule run |
Purchase Order (/purchase-orders) | Incoming material with expected delivery date | MRPeasy → SkyPlanner | Hourly or per schedule run |
Manufacturing Order due_date and custom_<id> fields (PUT /manufacturing-orders/{id}) | Planned start, planned finish, progress | SkyPlanner → MRPeasy | On schedule change, via SkyPlanner webhook |
| Not in MRPeasy | Setting time matrix, tools as finite resources, operator counts, alternative workstations | Maintained in SkyPlanner | Set up during onboarding |
Integration patterns
1. Initial master data load. Pull items, units, BOMs and routings from v1, and workstation groups and workstations from v1 or v2. Take calendars from v2 /workstation-groups (work_hours, holidays) or set shifts directly in SkyPlanner. Map each Active processing group to a SkyPlanner workstation group with its workstations as members.
2. Order sync. Read open manufacturing orders with their operations, plus open purchase orders and inventory. SkyPlanner treats ordered material as available on the PO delivery date and updates stock when the PO is marked Delivered. The schedule checks both stock and incoming purchases on every replan.
3. Schedule write-back. PUT /manufacturing-orders/{id} supports code, quantity, due_date and assigned_id, plus custom fields as custom_<id>. SkyPlanner writes the planned finish to due_date where agreed, and planned start, planned finish and progress to MRPeasy custom fields. Sales and purchasing in MRPeasy then see the real schedule. The detailed operation sequence and workstation per operation live in SkyPlanner, which is the dispatch view for the floor.
4. Orders created outside MRPeasy. If orders are ever created through the API, POST /manufacturing-orders accepts no_scheduling and no_bookings. Use them so MRPeasy does not book workstations that SkyPlanner already schedules.
5. Shop-floor confirmations. Operators log work with SkyPlanner Mobile Confirmations, Production Timer or Quick Log Mode, and the timelogs keep the schedule current. Pick one reporting channel. Running MRPeasy’s Internet-kiosk and SkyPlanner side by side for the same operations creates two versions of the truth.
6. Ownership and conflict rules. Write them down before go-live:
| Data | Owner |
|---|---|
| Items, BOMs, routings, quantities, stock, procurement | MRPeasy |
| Operation sequence, start and end times, workstation assignment | SkyPlanner |
| Setting time matrix, tools, operator counts, alternative resources | SkyPlanner |
| Shifts and absences | One system, chosen in scoping |
| Order progress and logged work | SkyPlanner, summarized on the Manufacturing Order |
Engineer-to-order flow. In one delivered MRPeasy project, each customer project becomes a main product plus one to three semi-finished products. Each has its own BOM and routing in MRPeasy, and the manufacturing order exists in both systems. Keep a stable shared identifier on every order so updates never create duplicates.
Typical project steps
Implementation is normally completed within weeks after onboarding starts. Before that, the 30-day free trial runs on your own data on any MRPeasy plan. Export items, BOMs, routings, workstations and open manufacturing orders from MRPeasy list views to CSV, import them and validate the schedule.
The project itself contains:
- Plan check. Confirm the MRPeasy plan includes the API, and create the API key and secret.
- Mapping. Fix the mapping table, ownership rules, custom fields for write-back and the reporting channel.
- Initial load. Items, units, BOMs, routings, workstation groups, workstations, calendars.
- Order and purchase order sync. Incremental polling by status, with 429 handling.
- Constraint setup in SkyPlanner. Setting time matrix, tools, operator counts and alternative workstations.
- Write-back. Due dates and custom fields on each Manufacturing Order.
- Parallel testing. Run SkyPlanner beside the current Production schedule, compare dates, fix master data.
- Go-live. Switch on write-back once the data matches.
What to plan for in an MRPeasy integration
- Time fields differ by interface. The UI’s Setup time, Cycle time and Capacity are
fixed_time,variable_timeandvariable_quantityin the API. Capacity above 1 means batch processing, as in an oven. Map it as a batch job, not a longer cycle. - Passive processing groups. Drying and cooling groups run 24/7 without capacity limits. Map them as wait times, not finite workstations.
- Calendars are missing from v1.
work-centersreturns onlycenter_id,type_id,codeandtitle. Use v2 or maintain shifts in SkyPlanner. - Idle time. Workstation idle time holds maintenance and downtime. Sync it, or SkyPlanner plans work on a machine that is down.
- Routings point to groups. MRPeasy picks the machine with the best availability. In SkyPlanner the group’s workstations become real alternatives the engine chooses between.
The MRPeasy integration: who configures and supports it
The work covers mapping your routings, workstation groups and order flow, plus the constraints MRPeasy does not hold: setting time matrix, tools, operator counts and alternative resources.
- The SkyPlanner team configures it during onboarding and supports it after go-live. Every plant runs MRPeasy differently, and this is where that know-how goes. Because MRPeasy support does not cover API work, having one team own the integration matters.
- Your MRPeasy consultant or integration partner can build it. In a delivered MRPeasy project, an integration partner connected the two systems through both REST APIs. SkyPlanner provides the REST API, Swagger/OpenAPI documentation and webhooks.
- Your own developers can build on it with an API token. An API token is enough to start, and the SkyPlanner team assists when needed. Product documentation, including purchase orders and the products and materials API, is at SkyPlanner docs.
SkyPlanner starts from 199 € per month with 5 workstations included, billed monthly. 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 pricing, features and how MRPeasy’s own scheduler compares in MRPeasy finite capacity scheduling. The overview is on the MRPeasy page, and other ERPs are in the ERP integrations hub.
SkyPlanner reviews from manufacturers
2 hsaved every week
“SkyPlanner has taken our production planning from Excel spreadsheets to real-time production optimization.”
Kalle Kalliomäki, Supply Chain Specialist
UTU · Electrical switchboards and switchgear
Production planning saves 2 hours of working time every week, and a new work queue reaches the line in seconds.
+90%production efficiency
“Efficiency has gone up 90% in production.”
Abdul Rucyinga, Head of IT
Laboratory & Allied · Pharmaceutical manufacturing
Production efficiency is up 90%, and a three-month optimized plan across all workstations takes under 30 minutes.
6 monthsof free capacity visible to sales
“SkyPlanner creates the foundation and reliability for all production planning.”
Anu Järvinen, Production Manager
Fredman Operations · Food-safe packaging papers
Sales sees free capacity six months ahead, and schedule-change requests that took an hour or more are answered in seconds.
FAQ
Does MRPeasy have an API, and which plan do I need?
Yes. MRPeasy offers a REST API, v1 in production and v2 in development, on the Unlimited plan for paying accounts. Authentication is HTTP Basic with an API key and secret from Settings → Integration → API access.
Can SkyPlanner write the schedule back into MRPeasy?
Yes. SkyPlanner updates each Manufacturing Order through PUT /manufacturing-orders/{id}, writing the due date and custom fields for planned start, planned finish and progress. The detailed operation sequence lives in SkyPlanner, where operators work from their own queue.
Does MRPeasy push changes in real time?
The API specs document no webhook events for manufacturing orders, so SkyPlanner polls open orders by status every few minutes. SkyPlanner’s own webhooks push schedule changes as they happen.
Who builds the MRPeasy integration?
The SkyPlanner team configures the two-way integration during onboarding and supports it after go-live. Your MRPeasy consultant, an integration partner or your developers can also build on SkyPlanner’s documented REST API.
Can we test SkyPlanner before building the integration?
Yes. The 30-day free trial supports up to 20 workstations with CSV imports from MRPeasy, on any MRPeasy plan, no credit card needed. Start the trial, or talk to sales to scope the integration.
