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.