Quality Master
For: Anyone building the QC checklists used to inspect materials, production runs, or finished goods
A QC report here isn't just a name. It's a real checklist of tests, each with its own response scale, that you build once and can point an item's purchasing, sales, or production setup at later.
What this module does
1. A QC report is a named checklist of tests
Four fields identify the report itself, before you get to what it actually checks.
QC Report Name and Product Name: What the report is called and what it applies to.
QC Report Responsible: Who's named as the checker on this report.
Type: One of four fixed categories: In Material QC, On Production QC, Batch QC, or R & D QC.
Report ID: Assigned automatically with a QC- prefix unless you change prefix or next number on the number preferences icon. You cannot type a one-off ID on the form.
2. Each test picks a response scale, not free text
Add Test Type doesn't ask you to build a response scale from scratch. You pick one of six presets, and it fills in the choices for you.
Yes / No, Pass / Fail, Compliant / Non-Compliant, Good / Fair / Poor: Four ready-made multiple-choice scales, each with its own N/A option.
Our Standard: Switches the test to custom numeric fields instead: weight, length, width, height, and volume.
Size: A single value response rather than a multiple-choice one.
Title on QC Report and Remark: Every test also carries its own display title and an optional remark, independent of which scale you picked.
3. Where a QC report gets linked, and what actually happens
An item can point at a QC report from three of its own tabs.
Purchasing Data: Before Dispatch From Vendor Factory and After GRPO On Our Warehouse can each carry their own IQC standard.
Sales Data: Before Dispatch From Warehouse carries an FQC standard.
Production Data: OQC carries its own standard for output leaving production.
Warning: Linking a report to an item saves the reference and nothing more. No GRPO, Bill, Delivery Challan, or Production Order currently checks or blocks on it. Treat this as a checklist definition, not an enforced gate, until that changes.
4. Editing and deleting
Editing: Every save adds to a running history of who edited the report and when, rather than overwriting who last touched it.
Deleting: Blocked outright if any item still names this report as its IQC, FQC, or OQC standard. There's no deactivate step in between. A report is either in use or deletable.
Business rules
| Topic | Rule |
|---|---|
| Report ID | Auto-generated with a QC- prefix unless you change prefix, next number, or auto-generate under the number preferences icon on Add Quality |
| Required fields | Type, QC Report Name, QC Report Responsible, Product Name, and at least one test |
| Report Type | One of four fixed values: In Material QC, On Production QC, Batch QC, R & D QC |
| Test response | Every test is either a preset multiple-choice scale, a set of custom measurement fields, or a single value — never free text |
| No active/inactive status | There's no deactivate action on a QC report, only Edit and Delete |
| Editing | Keeps a full history of every editor and when they saved, on every save |
| Deleting | Blocked if any item currently points to this report as its IQC, FQC, or OQC standard |
| Enforcement on transactions | None yet. No GRPO, Bill, Delivery Challan, or Production Order actually checks or blocks on a linked QC report |