The Quality Workspace
Quality in GarmentFlow exists to do two things: catch problems while they're cheap to fix, and leave a data trail that surfaces patterns no single inspector could see alone. This section is built around both.
Open Desk → GarmentFlow → Quality Control and the workspace fans out into the tools the quality team uses every day:
- QC Inspection — every check, in-line and final, lives here as one record.
- QC Parameter, QC Defect Category, IQ Template — the masters the team owns.
- QC Unit Status, QC Issue Radar, QC Heatmap — the dashboards that turn captured data into decisions.
- Reports — the tabular reports for monthly reviews, brand audits, and root-cause meetings.
- Quality App — a direct link to the touch-friendly inspector interface at
/garments/quality.
Two flavors of quality
Every check in GarmentFlow is one of two kinds:
- In-line Quality Check — happens during production, at operation boundaries. Goal: catch a problem before the rest of the batch repeats it. If a stitching defect is showing up on the first 20 garments, you want to know before the next 380 are stitched the same way.
- Final Quality Check — happens after production, before the finished garments leave for boxing or shipping. Goal: confirm the batch as a whole meets the spec the brand signed off on, and decide accept / accept-with-deviation / reject / hold.
Both use the same QC Inspection doctype. What separates them is the inspection stage: an in-line check points at a mid-production operation (Stitching, Embroidery, Wash); a final check points at the last operation before packing.
The mental model
An inspection captures readings and defects. A defect points to a category and a severity. A threshold breach triggers an alert. An alert turns into action.
The whole section is a pipeline from data captured by inspectors to decisions taken by managers. Every doctype, every dashboard, every report is a stop on that pipeline.
Where to start
If you're new to the section, read in this order:
- Installing the Quality App — get the app on a tablet first; everything below assumes you can open it.
- Inspections — what an inspection is, how the two flavors differ.
- Setup — the masters and alert config the team owns.
- Dashboards — what to look at when you want to know if the floor is in control.