ERP and software integrations
ModernMES books finished work in your ERP as a production receipt and takes stock items and customers from it, so nobody types the same thing twice. Here is what it connects to and how.
SAP Business One Integration for Shop Floor Output
ModernMES books finished work in SAP Business One as a Goods Receipt and scrap as a Goods Issue through the Service Layer, and pulls items and customers.
Read moreDynamics 365 Business Central MES Integration
ModernMES pulls items and customers from Business Central and sends output and scrap as item journal lines through a partner-published API page. How it works.
Read moreOdoo MRP Integration: Shop Floor Output to Odoo
ModernMES turns each finished job into a completed Odoo manufacturing order, consuming the BoM, and books scrap. Odoo 16 to 18 with MRP and Inventory.
Read moreWebhooks and JSON Integration for Work Order Events
Receive signed work order webhooks and send production and scrap records to your own endpoint with the generic JSON connection. Headers, signatures, retries.
Read more
How it works
When an operator finishes a job on the terminal and enters the good and scrap quantities, ModernMES queues a transfer. It is written to the ERP in the background, so the operator never waits for the ERP.
- What is sent: a production receipt for the good quantity and, if you want it, an issue or scrap record for the scrap. The document carries the work order number, the project and the record's unique ModernMES reference.
- When: when the part's last operation finishes (the default), after every operation, or only when someone presses send.
- Never lost, never booked twice: the same finished job is queued only once. If the ERP is unreachable, ModernMES tries 8 times at intervals growing from 1 minute to 12 hours; data errors, such as a missing item, are not retried — you fix them and send again.
- Transfer log: each record's status, ERP document number and error message, with retry and cancel.
- Master data: stock items and customers are pulled from the ERP with a button in the settings; new codes are added and nothing is deleted. Differing codes are mapped per part.
- Security: usernames, passwords and keys are stored encrypted and never sent back to the browser.
The cloud version of ModernMES deliberately refuses private network addresses. An ERP running inside your company needs its web service reachable from the internet (over HTTPS, restricted to ModernMES's address); otherwise ModernMES is installed on your own server and reaches the ERP over your internal network. The ERP integration add-on is included in Enterprise and can be added to the other plans.
Connectors
| System | Connection | Booked in the ERP | Page |
|---|---|---|---|
| Logo Tiger / GO / Wings | Logo Objects REST service (needs a Logo Objects licence) | Production receipt slip; scrap slip | — |
| Mikro | Mikro Desktop API | Production slip or warehouse receipt; scrap movement | — |
| Netsis | NetOpenX REST (internal network only) | Warehouse receipt of type production; warehouse issue | — |
| DİA | DİA web service (each call uses credits) | Material slip, or a production slip that consumes the BoM; scrap slip | — |
| Paraşüt | Paraşüt API v4 | Adds the quantity made to the warehouse stock count; no scrap, no BoM consumption | — |
| SAP Business One | Service Layer | Goods Receipt; Goods Issue (not linked to a production order) | SAP Business One |
| SAP S/4HANA | Material document OData API (cloud or on-premise) | Material document: movement 521 receipt, 551 scrap (configurable) | — |
| Dynamics 365 Business Central | API v2.0 with Entra ID; output via an item journal API page your partner publishes | Item journal line: Output / Negative Adjmt. | Business Central |
| Odoo 16–18 | JSON-RPC (Odoo Online needs the Custom plan) | Completed manufacturing order (consumes the BoM); scrap | Odoo |
| Anything else | Generic JSON: a signed POST to your endpoint | Whatever your endpoint books | Webhooks and JSON |
Each connector is written against the ERP vendor's published API documentation. During setup we configure the connection with you and post trial records to a test company or a copy of your database, and check them with your accountant, before going live.
What the ERP integration does not do
- It does not bring sales orders, or work and production orders from the ERP, into ModernMES; jobs are opened in ModernMES as projects.
- It does not pull bills of materials or routings from the ERP. (With Odoo, and DİA's production slip option, the ERP itself consumes the BoM.)
- It does not read stock levels or stock movements from the ERP back into ModernMES.
- Master data pulls are not scheduled; they run when you press the button.