Quality Control and Non-Conformance Tracking in ERP: A Practical Setup for Foreign-Owned Manufacturers in Türkiye

A rejected batch gets written on a sticky note. A supplier's out-of-spec delivery gets a phone call instead of a record. Six months later a customer audit — or a group compliance review — asks for the non-conformance log, and there isn't one. This is the most common quality gap in mid-sized manufacturing subsidiaries in Türkiye: the production line works, the certificates exist, but the paper trail connecting a defect to its correction does not.

What does "quality control in ERP" actually mean?

It is not a separate quality department buying separate software. In a well-set-up ERP, quality control is a set of checkpoints attached to the transactions that already happen — goods receipt, production output, shipment — plus a structured way to record what happens when something fails a checkpoint. The two halves are inspection (did this batch meet spec?) and non-conformance management (what happens when it didn't?). Most manufacturers have informal versions of both. The gap is that informal systems don't produce a record an auditor, a customer, or a foreign parent company can review months later.

Where do inspection checkpoints belong?

Three points cover most manufacturing operations:

• Incoming inspection — raw material or component received from a supplier is checked against agreed specifications before it enters usable stock. A failed check should block the material from being consumed in production, not just get flagged after the fact.
• In-process / final inspection — a batch or work order is checked at a defined stage (end of a production step, or before it moves to finished goods). This is where scrap rate and rework rate become visible per batch, not just as a monthly average.
• Outgoing inspection — before shipment, particularly for regulated or export-bound goods, a final check confirms the shipped batch matches what was ordered and inspected.

Which of the three matters most depends on the industry. A food or pharmaceutical operation leans heavily on incoming and in-process checks tied to lot and serial traceability. A metal or plastics manufacturer often puts more weight on final inspection against a drawing or tolerance spec.

What happens when a batch fails inspection?

This is where most informal systems break down. A failed inspection needs to trigger a structured non-conformance record, not just a rejected quantity in a spreadsheet. A usable non-conformance record answers four questions:

1. What failed, and against which specification? (linked to the batch, lot, or work order — not a free-text description alone)
2. What is the disposition? Scrap, rework, use-as-is with customer concession, or return to supplier.
3. What is the root cause, and what corrective action was taken? This is the step most often skipped under time pressure — and the one a customer or ISO 9001 auditor asks for first.
4. Is the action closed, and when? An open non-conformance with no closure date is functionally the same as no record at all.

Without this structure, the same defect tends to recur quarter after quarter, because nobody connects this month's rejection to the identical one from six months ago.

Why does traceability matter more for a foreign-owned subsidiary?

A Türkiye subsidiary of a foreign group usually answers to two audiences at once: local regulatory or customer audits, and a parent company's own quality or compliance review — sometimes as part of a broader group ISO certification. When lot and serial data live in the ERP rather than in a separate spreadsheet, a single non-conformance can be traced in both directions: backward to the supplier lot and incoming inspection record, forward to every customer shipment that included the affected batch. That forward trace is what makes a targeted recall possible instead of a blanket one — a distinction that matters directly to cost and to customer relationships.

What metrics does this structure actually make visible?

Once inspections and non-conformances are recorded against transactions rather than in free-standing notes, a handful of numbers stop being estimates and start being calculable per batch, per shift, or per supplier:

• First-pass yield — the share of output that passes inspection without rework, which is usually the single number a plant manager is asked for in a monthly review.
• Scrap and rework rate — split by cause code (material, machine, operator, design) instead of a single blended percentage, which is what actually points to where to intervene.
• Corrective action cycle time — how long a non-conformance stays open from identification to closure. A rising average here is an early warning that quality issues are being logged but not resolved.
• Supplier rejection rate — rejections per supplier lot, which feeds directly into the vendor scoring below.

None of these require a separate reporting tool once the underlying transactions carry the data; they are a query away rather than a monthly manual reconciliation.

How does this connect to supplier evaluation?

A non-conformance tied to a specific supplier lot is only useful if it feeds back into how that supplier is scored. Treating supplier quality as a running record — rejection rate, on-time delivery, corrective action responsiveness — turns anecdotal "that supplier gives us trouble" impressions into a defensible basis for renegotiating terms or switching sources. This is also usually the data a group procurement function asks a Türkiye subsidiary to report on.

What does this look like set up in ERP?

Birasyo's Quality module attaches inspection checkpoints directly to goods receipt, production, and shipment transactions, so a failed check blocks the material or batch rather than relying on someone remembering to flag it. Non-conformance records capture disposition, root cause, and corrective action against the specific batch or lot, with an open/closed status that makes overdue corrective actions visible instead of buried. Combined with batch and serial traceability, a single non-conformance can be traced back to the incoming supplier lot and forward to every shipment it touched — the trace an audit or a targeted recall actually needs.

Summary

Quality control in ERP is not a separate system bolted onto production — it is inspection checkpoints attached to receipt, production, and shipment, paired with structured non-conformance records that capture disposition, root cause, and corrective action. For a foreign-owned manufacturing subsidiary in Türkiye, this record serves two audiences at once: local customer or regulatory audits, and a parent company's own quality review. The cost of skipping it isn't visible until an audit or a recall asks for a trail that was never built.

---

This article is general operational guidance, not a certification or legal opinion. Confirm specific ISO 9001, IATF, or customer-specific quality system requirements with your quality management or certification body.

Sources

• ISO 9001 — Quality Management Systems (general framework for inspection and non-conformance/corrective action requirements)