Quality Is Not a Department That Inspects at the End. It Is a Set of Gates in the Process
A quality module earns its place by doing two things. It stops bad material moving forward, by holding stock the picker cannot then pick. And it makes the record of that automatic, instead of a clipboard someone files in a drawer. Everything else, the certificates, the supplier scorecards, the recall trace, falls out of those two once the gates are real.
50+ ERP and software projects. Zero failed projects since 2021.
The economics are decided by where you catch it
A defect found at goods receipt costs a return. The same defect found by the customer costs the return, the replacement, the freight, the credit note and the relationship. Every stage it escapes multiplies the bill, and that arithmetic is the entire case for inspecting early rather than thoroughly at the end.
The cost of a defect rises by roughly an order of magnitude at each stage
Reject a supplier lot at incoming and you have spent an inspector's hour and a debit note. Miss it, and the same material gets issued to a work order, machined, assembled and part-built before anyone notices, so now you scrap your own labour and material too. Miss it again and it ships, and you pay for freight both ways, a replacement build, a credit note and an audit from a customer who no longer trusts you. That is why the incoming gate matters more than its modest cost suggests, and why in-process checks belong on the operations where a defect becomes expensive to undo, not on all of them.
- Incoming: the cheapest place to say no, and the least used.
- In-process: stop the work order before more value is added.
- Final: the last defence, and the most expensive one to rely on.

A quality module will not improve your quality
It enforces the gates and keeps the evidence. That is genuinely valuable, and it is not the same thing. If the specification is wrong, the system will faithfully pass defective material against it. If nobody acts on the non-conformance, the system will document the problem more neatly every month while the defect rate stays exactly where it was. The gains come from two places: material that cannot move forward once it has failed, and a record that is complete enough to show you where the failures actually cluster. What you do with that second part is a management decision, not a configuration one.
- The specification has to be right before the gate means anything.
- A hold only works if it blocks the pick, not if it prints a label.
- Recorded non-conformances are worth nothing until someone owns them.

Six areas the quality module owns
Inspection execution sits here. Production execution sits in manufacturing and equipment upkeep sits in maintenance, and both are deliberately outside this boundary so the same event is not recorded twice.
The quality control cycle, end to end
What we set up when we configure this module
Specifications and plans
Characteristic lists with targets and tolerances, measurement methods, sign-off authority and version control on every change.
Sampling and skip-lot rules
Sample size and acceptance level by item and inspection type, with reduced rates earned by suppliers with a clean run behind them.
Quarantine and dispositions
A hold that blocks picking and issue, a quarantine location, and the four dispositions each wired to its own follow-on transaction.
Non-conformance and CAPA workflow
Raise, investigate, act and verify, with owners, due dates, escalation on overdue items and a verification step that cannot be skipped.
Certificate templates
Certificates of analysis and conformity populated from recorded results, and supplier certificates captured against the received batch.
Trace and audit reporting
Two-way batch and serial trace, supplier rejection analysis, calibration due lists and the evidence pack an ISO 9001 audit asks for.
What running the gates properly actually buys you
What this connects to
Quality sits between the process that makes the product, the equipment that has to be capable of making it, and the automated inspection layer that can read the result for you.
Why teams hand us the quality module
Quality management questions
Where do inspection points sit in the process?
How do sampling plans work and can we reduce inspection for good suppliers?
What happens to material that fails an inspection?
How is CAPA tracked and how do you know it worked?
Does the module support ISO 9001 and regulated audit requirements?
How does batch traceability work for a recall?
Put Real Gates in Your Process
Book a free consultation. We will walk your receiving bay, your routings and your despatch bench, look at where defects are actually being caught today, and give you a straight view on which gates are worth building first and which inspections you could safely stop doing.
Book a Free Consultation →No commitment. A practical look at your inspection points and your non-conformance record, whichever ERP you run.
What Is Inside the Quality Management Module
The specification that defines a good part, the sampling plan that decides how many you check, the hold that stops a failed batch moving, and the record that proves all of it happened. Here is how each of those is set up and what it does when something fails.
From the specification to the signed certificate
A plan that says what to measure, how, and on how many
An inspection plan lists the characteristics, each with a target and an upper and lower tolerance, the measurement method and the instrument to use, and the role authorised to sign the result. Variable measurements record an actual value, so you get a trend and can see a process drifting towards a limit before it crosses it. Attribute checks record only pass or fail, which is cheaper to capture and tells you far less, so we use them where a value genuinely does not exist. The sampling plan then sets the sample size and the acceptance level, and skip-lot rules reduce the rate for suppliers who have earned it through a clean run.
- Target with upper and lower tolerance per characteristic.
- Variable and attribute checks stored and reported differently.
- Skip-lot reduction tied to real supplier history, not to goodwill.

A failed batch is quarantined, then someone named decides
When a check fails, the stock goes to a quarantine location or carries a status that blocks picking, issue to a work order and sale. That is the whole point: a hold which only exists as a label on a pallet is not a hold, because the picker follows the screen and the screen said it was available. From quarantine an authorised person records one of four dispositions. Use as is, which needs a documented justification. Rework, which raises a rework order and a re-inspection. Concession, where the customer or engineering accepts a deviation in writing. Or reject and return, which raises the debit and the supplier corrective action request together.
- Quarantine that blocks pick, issue and sale, not just a label.
- Four dispositions, each wired to its own follow-on transaction.
- The reason and the approver stay attached to the batch for good.

The evidence trail, built as work happens rather than before an audit
Every non-conformance carries the batch, the quantity, the defect and the cost, then root cause, corrective action for the instance and preventive action for the recurrence, each with an owner and a due date. A separate verification date after closure asks the only question that matters, whether the defect stopped. Certificates of analysis and conformity are generated from the results actually recorded against the batch, so they cannot say something the inspection did not. Supplier certificates are captured against the receipt. And batch trace runs both ways, back from a customer delivery to the supplier lots and forward from a suspect lot to every customer who received it.
- CAPA with an owner, a due date and a verification date.
- Certificates populated from recorded results, never typed.
- Two-way trace, tested with a mock recall before sign-off.

Everything the module setup delivers
Approved specification library
Characteristics, tolerances, methods and signatories per item, under version control with a log of who changed what.
Sampling and skip-lot rules
Sample size and acceptance level by item and gate, with reduced rates released and withdrawn on supplier performance.
Working quarantine
Hold statuses and locations that block picking, issue and despatch, with the four dispositions and their approvals configured.
CAPA register and workflow
Raise, investigate, act, close and verify, with escalation on overdue actions and a verification step that cannot be bypassed.
Certificate output
Certificates of analysis and conformity drawn from recorded results, plus supplier certificates filed against the received batch.
Supplier and audit reporting
Rejection rate by supplier and defect, open corrective action requests, calibration due lists and a mock recall run on your own data.

