[0·2·0] · Crown Product & pilot module · on request

MESmate: native shop floor MES right inside Odoo Enterprise.

Once manufacturing operations outgrow simple bills of materials, a gap opens between ERP planning and the shop floor. MESmate closes that gap natively in Odoo 20 Enterprise: with a 3-pane shop floor workspace, five status axes, a 10-quantity ledger, physical tool lifecycle, quality hold logic, and an audit-safe event architecture.

Native in Odoo 20 OWL-3 workspace directly on MRP, QMS & PLM
5 Axes · 10 Quantities 13 execution states without blind scrap
3D Tooling Dossier Type, instance, assembly & reconditioning
MESmate 3-Pane Workspace · CNC Cell 04 OWL-3 · Outbox rev.14
Shift: Early-01 As-of cascade: 12 steps Scenario: Savepoint B BOM Rev. 04 protected WORK ORDERS MO-2041 · OP 20 Mill housing block RUNNING MO-2039 · OP 30 Check dims · Lot L8 blocked_quality MO-2044 · OP 10 Turn shaft · Setup completion_pending SHIFT HANDOVER 2 open notes OEE snapshot live MO-2041 · 5 STATUS AXES Material: OK Machine: CNC-04 Quality: Passed Tooling: TL-19 10-QTY LEDGER (NO AUTO-SCRAP) Plan / Rebaseline 120 pcs Good qty reported 84 pcs Quarantine / Rework 2 pcs (Q-Check) Reported variance Open: 34 pcs OUTBOX & CNC TRANSFER base_revision #14 · Hash verified NC prog: G54_BLK_R04.nc → CNC-04 DETAIL DOSSIER 3D TOOLING LIFECYCLE Unit: TL-19-04 Assembly: Spindle A Tool-life monitor Regrind: Cycle 2/4 QMS GENEALOGY Raw lot: RM-402 QC plan: 1st piece OK 360° causal net live EDGE & ALARMS 0 critical alarms Counter feed in sync
MESmate Odoo 20 Enterprise · MRP, QMS, PLM & Planning

Shop floor reality modeled cleanly inside the ERP data model.

MESmate does not replace your Odoo core — it supplies the missing execution depth for complex production, tooling, and quality workflows.

3-pane workspace & 360° causal network

A native OWL-3 operator workspace unites work order queue, live execution, and polymorphic detail dossiers. Via the planning context bar, production managers and schedulers see immediately which material, tooling, or quality dependency affects an order.

5 status axes & 13 execution states

Production is rarely simply "open" or "done". MESmate separates material, machine, operator, tooling, and quality status — including intermediate states like completion_pending and blocked_quality without premature auto-scrap postings.

10-quantity ledger & 12-stage time cascade

Target quantities, rebaseline adjustments, good output, quarantined stock, and reported variances are recorded separately. A 12-stage lead-time cascade with point-in-time logic (as_of) keeps scheduling calculations and post-costing dependable.

Physical 3D tooling lifecycle

Tool definitions, individual physical tool instances, mounted assemblies, and reconditioning or regrinding cycles are modeled cleanly apart. Operators can verify at the workstation which tool is cleared for use and when reconditioning is due.

QMS disposition, genealogy & PLM protection

Inspection plans, quality dispositions, and lot genealogy attach directly to the manufacturing order. Active orders remain shielded from uncontrolled BOM or CAD revision jumps, while planning scenarios commit changes only through verified savepoints.

Transactional outbox, shift handover & CNC

A command outbox and event inbox safeguarded by base_revision and payload_hash checks protect shop floor postings, machine alarms, ETL/counter feeds, CNC program transfers, shift handovers, and OEE snapshots against duplicate or conflicting processing.

Pilot fit: prerequisites and honest boundaries.

An MES reaches deep into production, quality, and equipment operations. That is why we never rush MESmate into live plants — we introduce it along a clearly scoped pilot area.

When it fits & prerequisites

  • Manufacturers on Odoo 20 Enterprise: Companies in mechanical engineering, machining, or precision manufacturing running MRP, work orders, quality, PLM, and maintenance on Odoo.sh or dedicated self-hosting.
  • Complex operations & tooling constraints: Valuable whenever tool life tracking, multi-stage inspections, structured shift handovers, or lot genealogy go beyond standard Odoo.
  • Reliable master data foundation: Clean part records, bills of materials, and work center data are the prerequisite for trustworthy shop floor reporting.
  • Scoped pilot entry: Starting on one representative production line or machine group before rolling out step by step has proven most effective.

Limits & honest boundaries

  • Not for Odoo Community or Odoo Online: MESmate builds directly on Odoo Enterprise modules (mrp_workorder, quality_control, mrp_plm, planning, web_gantt) and therefore requires Odoo Enterprise.
  • No replacement for PLC real-time control: Safety interlocks and millisecond machine control loops belong on the PLC/CNC layer; MESmate orchestrates orders, states, quality, and data handoffs above them.
  • Often oversized for simple assembly: If your operation builds single-level assemblies without tool lifecycles or quality hold dispositions, well-configured standard Odoo MRP is usually sufficient.
  • Rollout on request & pilot validation: Functional scope, machine/edge interfaces, and operating model are aligned in a written architecture blueprint ahead of implementation.

Frequently asked questions on MESmate.

Core architectural questions around native production control, quality holds, and tooling management in Odoo Enterprise.

Why choose a native MES inside Odoo over an external MES interface?

External MES tools frequently create duplicated master data, delayed feedback, and conflicting inventory between shop floor and ERP. MESmate runs directly on Odoo Enterprise's data model for MRP, inventory, quality, maintenance, and planning, keeping manufacturing orders, lots, and costs on a single source of truth.

How does MESmate handle quality deviations and scrap at the workstation?

Instead of blindly booking scrap on an inspection failure, the execution model provides dedicated states such as blocked_quality and completion_pending. Affected quantities are tracked cleanly in the 10-quantity ledger and resolved through an auditable quality disposition (release, rework, or scrap).

What does the physical tool lifecycle track in practice?

MESmate separates tool types (ToolDefinition), individual physical tools (ToolInstance), mounted assemblies (ToolAssembly), and reconditioning or regrinding cycles (ToolReconditioning). Tool life, usage locations, and lock states remain traceable down to every physical tool.

What Odoo prerequisites apply to running MESmate?

MESmate is built for Odoo 20 Enterprise on Odoo.sh or dedicated self-hosting and builds on standard Enterprise modules including Manufacturing (MRP), Work Orders, PLM, Quality, Maintenance, Repair, and Planning. Before rollout, we verify your specific shop floor workflow in a pilot blueprint.

Can machines, counters, or CNC programs be connected?

Yes. The architecture includes ETL channels, counter and edge monitoring, machine alarms, CNC program transfers, and a transactional command outbox and event inbox with revision and hash verification so shop floor events stay consistent even across brief network interruptions.

Inspect a real manufacturing order together.

Bring a representative manufacturing order with its operations, quality checks, and tooling requirements to the call. We will honestly assess where standard Odoo MRP is enough and where MESmate makes sense as a pilot module.

Matthias GrdanManaging Director · Manufacturing & ERP Architecture
MES & Odoo TeamShop Floor & Pilot Rollout · Villingen-Schwenningen

The introductory call is non-binding. Your inquiry is delivered directly via our Google Workspace mail service — or prepared locally as an email draft.

Delivered via our Google Workspace mail service or as a local email preview without third-party trackers. Privacy Policy

Book a call