Finding a defect at the end of the line is expensive in a way that’s easy to underestimate — by the time an inspector spots uneven topstitching on garment 500, garments 1 through 499 might already have the same flaw, and now it’s a rework pile instead of a five-minute correction.
A quality management system replaces clipboard inspections with digital inline checks: inspectors log defects on a tablet at each assembly stage, AQL sampling is set automatically per purchase order, and compliance documents sit in one live record. For BlueKaktus manufacturers this is ZedQ, a paid add-on to a Mozart plan, not part of base Mozart.
Is quality included in Mozart, or is it a separate module? It’s separate — ZedQ runs on top of a Mozart plan and isn’t bundled into base Mozart Premium or Enterprise pricing. This is worth saying plainly up front rather than letting it surface midway through a sales conversation. BlueKaktus Mozart is the ERP and manufacturing suite; ZedQ is what adds structured quality inspection on top of it.
ZedQ is priced on request, scoped against the size and number of lines being covered. It requires an existing Mozart plan as its base — there’s no standalone ZedQ deployment without Mozart underneath it.
Yes, a QMS needs tablets (or similar devices) at each inspection point, plus a reliable factory network connection for the tablet to sync data. BlueKaktus doesn’t supply this hardware — procuring rugged tablets and Wi-Fi infrastructure is the factory’s responsibility, typically sourced locally to match the shop-floor environment. Better to know this before the project starts than discover it during rollout.
Mozart’s base functions track order-level and style-level information; ZedQ adds the inspection layer itself — AQL sampling plans generated automatically per PO, inline defect logging at each stage of assembly rather than only at the end of the line, and defect-code analysis that shows which two or three fault types account for most of a line’s rework. When an inspector logs a recurring issue, say repeated skipped stitches at the same operation, it’s flagged to the line manager on the next check, rather than surfacing only once a batch fails final audit.
The system is built around a tablet-based inline checklist rather than a full desktop interface, which keeps the daily workflow close to what an inspector with a paper AQL sheet already does — log a defect, assign a code, move to the next unit. Formal training is part of implementation; specific language support should be confirmed directly for a given factory’s team.
| What’s covered | Base Mozart | ZedQ (add-on) |
|---|---|---|
| Style, costing, order entry | Yes | — |
| Production tracking | Yes | — |
| AQL sampling per PO | No | Yes |
| Inline defect logging (tablet) | No | Yes |
| Defect-code analysis | No | Yes |
| Compliance document storage | Partial | Yes |
(A “what’s included” diagram works well here — Mozart Premium core in solid blocks, add-on modules including ZedQ, Shopfloor MES, Production & Line Planning, Omni-Channel Retailing, SupplyKonnect and Capacity Marketplace shown as outlined, separate blocks.)
Bata runs across 70+ markets on BlueKaktus; Blackberrys moved from a fully manual two-year process to a data-driven one. Across the network, more than 300 factories are connected — BlueKaktus’s own materials currently show both “300+” and “350+ factories connected,” and a single figure will be confirmed and used consistently once available. Quality-specific outcome figures should be requested directly, since the approved fact pack doesn’t carry a QMS-specific number distinct from the general productivity figures.
It doesn’t detect a mechanical fault like a dull needle directly from machine data — a skipped-stitch pattern is flagged because an inspector logged it, not because a sensor detected it. It also doesn’t include overhead camera-based inspection; automated computer-vision scanning of garments on the line isn’t part of the current product, and where that’s discussed as a future direction, it should be labelled as an industry trend rather than a BlueKaktus capability.
Not sure whether your factory needs ZedQ or just cleaner ERP data first? BlueKaktus can walk through what your current inspection process would look like digitized.
Is quality management included in Mozart? No — ZedQ is a separate paid add-on that runs on top of a Mozart plan.
How much does ZedQ cost? Priced on request, scoped to the factory’s size and line count; requires an existing Mozart plan.
Does BlueKaktus supply the tablets and Wi-Fi needed for inline inspection? No — hardware and network infrastructure are the factory’s responsibility.
Can ZedQ detect a machine fault directly? No — it flags patterns from what inspectors log (e.g., repeated skipped stitches), not from machine-level sensor data.
Does ZedQ use camera-based inspection? No — inspection is inline and tablet-based, logged by a person at each stage.
What’s the difference between AQL sampling on paper and in ZedQ? The sampling plan itself follows the same AQL standard; the difference is that ZedQ generates and applies it automatically per PO and captures results digitally rather than on a paper form.
