Odoo MES integration for manufacturing orders and production feedback
Your MES tracks shop-floor execution. Odoo brings together planning, purchasing, inventory and accounting. When the systems work in isolation, staff have to record production data again. We help manufacturers design and configure a clear data flow between their Manufacturing Execution System and Odoo.
How does the Odoo MES integration work?
An Odoo MES integration connects a Manufacturing Execution System to Odoo as the ERP system. MES is a category of systems, not a single supplier. Possible data flows include manufacturing orders sent from Odoo and agreed production feedback returned by the MES. Available functionality depends on the MES, its interfaces and your manufacturing workflow.
Odoo Manufacturing and an external MES: who does what?
Odoo Manufacturing can support manufacturing and work orders itself. If you also use a specialized MES, responsibilities must be clear. We define where manufacturing orders originate, where staff record execution and which system posts inventory movements. This helps prevent an operation from being completed in both systems or a planning change from failing to reach the shop floor.
Exchange manufacturing orders, consumption and quantities
An integration can, for example, send a released order with its product, quantity and reference to the MES. If the interface supports it, feedback can include quantities, consumption, scrap or status. These are design choices, not a fixed standard set of fields. We define how partial production, corrections and different units are mapped to the appropriate Odoo records.
Manage lot tracking, corrections and duplicate messages
Lot and serial-number tracking require a clear link between an order, its raw materials and finished products. We define identifiers and permitted changes before connecting messages. Delayed, duplicate and incomplete messages also need agreed handling. Failed production feedback must not disappear silently or post the same production twice on retry.
Connect shop-floor execution to planning and inventory
Less duplicate production recording
Capture data where the work happens and exchange only the agreed information with Odoo.
Clearly defined responsibilities
Planning, execution and inventory processing each have an agreed owner so the systems do not contradict each other.
Traceable production feedback
Production references and processing statuses help staff investigate and resolve exceptions.
Frequently asked questions about Odoo and MES
No. Manufacturing Execution System is a general term for software that supports shop-floor execution. This page covers connecting such a system to Odoo. Your MES supplier and version determine the actual integration options.
No. Odoo supports manufacturing and work orders itself. A separate MES can help meet specific shop-floor requirements, but it also adds administration and data-ownership decisions. Kilurion first assesses whether Odoo already provides the required functionality in a suitable form.
This is defined for each configuration. Examples include orders, products, quantities, statuses and, where supported, material consumption or lot data. The interface and posting rules determine what is possible. We document the exact mappings and supported exceptions before building the integration.
This depends on the available interface and how up to date the data need to be. Event-based processing may be suitable, or scheduled exchange may be enough. We define delays, recovery after failures and visibility of processing errors rather than promising real-time behavior without evidence.
We start with the supplier, version, documentation and required workflows. If the MES provides a usable interface, we investigate a suitable integration. Based in Veenendaal, Kilurion helps manufacturers in the Netherlands with this alignment. Feasibility and scope are assessed in advance.
Shop Floor is Odoo's own execution environment. An MES integration connects Odoo to a separate manufacturing system. First compare the functionality needed and the boundaries between workflows. Using two systems without clear responsibilities can create extra work and duplicate records.