Blog / MES
MES · Guide

MES vs QMS: Who Owns Which Quality Record

OL By OEE Lab Editorial |Updated 2 November 2026 |5 min read
Short answer

An MES runs and records production on the floor: orders, counts, in-process checks and holds. A QMS manages the quality system around it: procedures, deviations, CAPA, audits, training and supplier quality. They meet at the nonconformance, so let the MES capture the event and the QMS own the investigation.

The line between them

The two systems work at different speeds. An MES lives in the minute a bad seal appears on Line 2, and a QMS lives in the weeks it takes to find out why and stop it coming back.

MESQMS software
Main questionWas this order made right, and what is happening now?Does our quality system work, and can we prove it?
Time scaleSeconds to shiftsDays to years
Built aroundOrders, machines, lotsDocuments, processes, events
Typical recordsIn-process checks, rejects, holds, genealogyProcedures, deviations, CAPA, audits, training, supplier ratings
Main usersOperators, supervisors, line quality techsQuality engineers, auditors, management
Data arrives fromMachines, scans, operatorsPeople, by forms and reviews
Typical split. Products overlap, so check functions and not labels.

A QMS as a concept is wider than any software. It is your whole set of quality processes, under a standard such as ISO 9001 or, for US medical devices, FDA's QMSR, which took effect on 2 February 2026 and incorporates ISO 13485:2016 by reference.

QMS software is the tool that holds its records. For what the other side covers, read what is an MES.

Follow one bad seal across both

Example: a pouch line starts rejecting more seals on Tuesday morning. Here is who does what, from the first reject to the closed action.

1
MES: the check fails
The 08:30 seal check is out of limit, and the result is stored against the order and lot.
2
MES: hold the range
Pouches since the 08:00 pass go on hold. The operator tags the stop.
3
QMS: open a nonconformance
It receives the order, lot, line, time and check result from the MES.
4
QMS: investigate and act
The team runs root cause analysis and opens a CAPA with an owner and due date.
5
MES: show the effect
Reject data after the fix tells the QMS whether the action worked.
Hypothetical event. The record starts in the MES, moves to the QMS, and comes back to the MES for proof.

Step 5 is the one often missed. A CAPA closed on a signature, with no data behind it, proves only that someone signed.

What a CAPA looks like in MES data

Example: 10,000 pouches started before the fix, and 9,400 passed first time. The same volume after the fix gives 9,700.

Before: 9,400 / 10,000 = 94% first pass yield
After: 9,700 / 10,000 = 97% first pass yield
Rejects: 600 down to 300
Hypothetical line. The QMS holds the action, and the MES holds the numbers that judge it.
Seal, before380
Seal, after90
Label, before140
Label, after130
Other, before and after80
The same hypothetical 600 and 300 rejects, by reason. Seal fell. Label and other barely moved, so the fix did what it aimed to do.

See how to calculate first pass yield for the formula, or try the calculator. Each reject also feeds the Quality factor of OEE.

Who owns which record

RecordUsually lives inWhy
In-process check resultMESTied to the order, in the moment
Reject count and reasonMESComes from the line
Hold on a lot or rangeMES, reported to QMSMust stop shipment now
NonconformanceQMS, opened from MES dataNeeds a workflow and approval
CAPAQMSRuns for weeks, across departments
Procedures and work instructionsQMS owns; MES shows themOne controlled version
Training statusQMS owns; MES can check itSome sites block untrained operators
Audits and supplier ratingsQMSNot tied to any single order

One owner per record is the rule. If two systems both let people edit a check result, then neither one can be trusted.

How QMS and MES software connect

Start with the links that remove retyping, and leave the rest for later. A plain list of fields is enough for a first version.

  • From MES to QMS: order, product, lot, line, time, check result, quantity on hold.
  • From QMS to MES: current document version, and hold or release decisions.
  • Later: supplier lot status, and training checks at log-in.

Keep the link simple, and make it one way per field. Decide what happens when it fails, because a hold must still work if the QMS is offline.

One system or two?

Some suites cover both sides. The open source Carbon project, for one, describes ERP, MRP, MES and QMS on one Postgres schema.

A single system means one login and no interface to maintain. Two specialised systems often go deeper on each side, at the price of a link to look after.

  • Your pain is audits, documents and CAPA tracking: QMS software comes first.
  • Your pain is rejects found late, or no reject reasons: start with MES data at the line.
  • You are in a regulated sector: you will likely need both functions, and validation applies. See MES for pharma.
  • You are small: a controlled folder and a simple scrap record can carry you a long way.

Neighbours in the quality stack

Two other systems get confused with these. SPC watches process variation over time, and LIMS manages lab samples and tests.

All of them feed the same questions. Keep each record where it starts, and link by order and lot.

Where the split goes wrong

  • Running in-process checks in the QMS. Operators then fill in forms away from the order, often late.
  • Running CAPA in the MES. A long investigation fits badly in a production system.
  • Retyping lots and quantities. One typo breaks the link back to genealogy.
  • Hiding quality time in OEE. Decide how to count holds and checks, and see cost of poor quality for their true price.
  • Fixing with procedures only. Where you can, build the fix into the process, as in poka-yoke.
See it live in Fabrico

On the MES side of this split, Fabrico is a light MES for OEE. It takes stops, speed and counts live from PLCs or IoT sensors, with add-on AI cameras counting output where a machine has no usable signal, with causes tagged at the line, so you see OEE per line and shift. See Fabrico as a light MES for OEE.

What people ask next

Is a QMS part of an MES?

Not normally. An MES includes quality functions such as checks and holds, while a QMS covers the wider system of procedures, CAPA and audits. MES modules shows the quality records an MES usually holds.

Do I need both an MES and a QMS?

A certified or regulated plant needs a quality management system of some form, though not necessarily separate software. An MES is a choice based on your floor problems. Many small plants start with one and add the other later.

What is CAPA, and does it belong in the MES?

CAPA means corrective and preventive action, the process of removing a problem's cause. It usually belongs in the QMS, with the MES supplying the data on what happened and whether the fix worked. See root cause analysis.

Can QMS software replace an MES?

Only for the records it holds. It will not usually read machines, count parts or block a step on the line. If you need that live view, you need execution functions as well, as in what is an MES.

Where should in-process inspection data live?

Usually in the MES, tied to the order, the lot and the moment. The QMS can pull summaries or be fed exceptions. MES traceability shows why the lot link matters.

See OEE per line and shift on your own machines

Fabrico is a light MES for OEE. It takes stops, speed and counts from PLCs or IoT sensors, with add-on AI cameras counting output where a machine has no usable signal, and operators tag the cause at the line.

Book a Fabrico demo

← More OEE Lab guides · How to calculate first pass yield →

OEE essentials: OEE calculator · What is OEE · Six big losses · Availability · TEEP · Cost of downtime · OEE benchmark · Free OEE tracker · Free OEE software · How to track downtime · How to implement OEE · Light MES vs full MES