Quality management belongs in ERP when inspection results, releases, and holds must steer the same order and stock picture as production and warehouse. Island solutions create media breaks: measured values do not match the batch, releases are missing on the order, shipping runs without a reliable status. Standard QM modules rarely fit special processes. What matters is modeling inspection logic on the real flow and documenting it in an audit-proof way.

Why does QA fail beside the ERP?

Because quality is not a side process. It decides whether goods may leave the yard, whether rework starts, and whether customers get reliable evidence. When inspection plans live in spreadsheets, gauge software, and email, three problems appear:

• Status break: Warehouse and shipping do not see releases in time.
• Data break: Batch, measured value, and production order are not connected.
• Evidence break: Audits take weeks because documents must be gathered.

Production, QA, and shipping need a shared basis. Overview: ERP in manufacturing.

Which requirements must QM cover in ERP?

Typical requirements in manufacturing companies:

• Inspection plans per article, batch, order, or operation
• Capture of measured values, deviations, and samples
• Release or hold processes before goods issue or further processing
• Documentation for customer audits, certifications, and internal audit
• Traceability: who released or held what, and when?

In ERP these steps can be coupled as workflows to manufacturing data. The advantage: the same data basis as production planning, stock, and shipping. No second master-data model for “QA articles.”

When are standard modules enough, and when do you need individual inspection logic?

Standard modules help with recurring, clear inspection patterns. You need individual inspection logic when make-to-order, customer-specific inspection plans, multi-level structures, or industry-specific evidence shape the flow. Then “QM out of the box” often fails on status models and field structures, not on lack of will in the specialist department.

Platform approaches model inspection logic without a parallel system. Nuclos couples releases and holds to the manufacturing and stock transaction instead of banishing QA into a side tool. That is process-first: the inspection step follows the order, not a module name.

How do you start without a certification big bang?

Choose one critical inspection step with clear risk or customer relevance. Map it digitally: plan, capture, release, documentation. Align the result with audit requirements. Measure how often work is still done in parallel spreadsheets.

Only when that step holds do you extend to further article groups or levels. Build auditability in: document and change history belong here, see GoBD and ERP. That builds acceptance in QA and production before the full picture escalates.

Which decisions come next?

Clarify which releases today block shipping or further processing. Identify the largest media break between measurement and order. Decide whether workflow and data basis in the ERP can carry the evidence, or whether a specialist system is unavoidable and then must be cleanly connected.

Further reading: ERP in manufacturing and production planning in ERP. For release logic and traceability: workflow in ERP.