Overview
Quality systems usually fail in the same place. The inspection happens — somebody walks the pallet, fills the form, files it — and the stock was already sellable before the form was signed. The check exists, and it changes nothing, because nothing was ever waiting on its result.
Nama ERP puts the inspection in the path instead of beside it. Received goods land in an inspection store and become available stock only once they pass. Production output is not accepted into the warehouse before its check is done. The result of an inspection is a state the goods are in, not a record of an opinion about them.
Two words that are not synonyms
The trade uses quality control and quality assurance almost interchangeably. Nama ERP keeps them apart, because they answer different questions and different people sign them off.
- Quality control asks is this batch conforming? It inspects the goods — incoming, in process, or finished — against acceptance criteria.
- Quality assurance asks was the step performed to specification? It verifies the process itself at a named operation, with a quality engineer assigned to it.
Both run as a request that opens the inspection and a document that records its result, so an inspection that was asked for and never done is visible as an open request rather than as nothing at all. Both can be chained: a multi-stage check links each document to the one before it, so the trail through a five-stage inspection is readable end to end.
The checklist is the part you maintain
What “passing” means is defined once, on a checklist: the questions asked of an item type, an assembly or a finished product, each with the kind of answer it takes — yes/no, a number, a range — and the rule that decides whether the answer is acceptable. Questions are classified so the same ones can be reused across products instead of retyped per item.
Attach a checklist to an item and the enforcement follows automatically. Nobody has to remember that this particular raw material is the one that needs testing.
What happens when it fails
An inspection has three honest outcomes, and the system carries all three: accept, and the goods move into available stock; reject, and they become a supplier return or defective goods; or accept part of the quantity and reject the rest, which is what actually happens most of the time.
Recording why a batch failed is what turns inspection into something more than a gate — rejection patterns are the clearest read you will get on a supplier’s real quality and on which process step keeps producing the same defect.
Where it sits in the flow
Inspection is a step inside larger paths rather than a module people visit. Receiving routes goods to an under-inspection location before they count as stock. Production and assembly embed checks at their stages, so output is not approved before it passes. And items with a re-test period — chemicals, pharmaceuticals — are brought back for re-inspection on schedule rather than when someone notices.
Read the quality control documentation for checklists, inspection levels and the receipt-inspection route in full.
