Handbag Private Labelby QUANZHOU JUNYUAN BAGS Get a quote

Build a Handbag QC System That Scales as You Add Styles

How much does quality control cost once a handbag brand runs more than one style? Three programmes illustrate it cleanly. A three-style programme spends roughly USD 60-95 per style per lot: a shared inline visit, a shared final inspection, and lot files that reuse one template. At nine styles the number drops to USD 45-70 per style, because inspections consolidate into combined visits. At eighteen styles it drops again to USD 30-55 per style, but only if the specification architecture was built for it — programmes that copied documents per style typically see the number go the other way, because the cost is in maintaining eighteen versions of roughly the same page. This page prices the three tiers, sets out the four triggers that decide when a style earns more inspection, and gives the document structure that makes the eighteenth style cheaper than the third.

Build a Handbag QC System That Scales as You Add Styles

How much does quality control cost once a handbag brand runs more than one style? Three programmes illustrate it cleanly. A three-style programme spends roughly USD 60-95 per style per lot: a shared inline visit, a shared final inspection, and lot files that reuse one template. At nine styles the number drops to USD 45-70 per style, because inspections consolidate into combined visits. At eighteen styles it drops again to USD 30-55 per style, but only if the specification architecture was built for it — programmes that copied documents per style typically see the number go the other way, because the cost is in maintaining eighteen versions of roughly the same page. This page prices the three tiers, sets out the four triggers that decide when a style earns more inspection, and gives the document structure that makes the eighteenth style cheaper than the third.

Quality cost per style at three programme sizes

Three styles, one lot eachUSD 60-95 per style per lot
Nine stylesUSD 45-70 per style per lot
Eighteen stylesUSD 30-55 per style per lot
Copied-per-style programmesCost per style rises instead of falling
Shared inspection dayUSD 220-320, covers two or three lots
Typical lot size500 pcs per style / colourway
Lead time to protect35-50 days bulk, 6-10 working days of sampling
Standard in forceAQL 2.5 under ISO 2859-1

Three Styles, Nine Styles, Eighteen Styles

The economics change twice on the way up, and both changes come from the same place: an inspection visit is priced per day, not per style. One man-day at USD 220-320 covers a lot of 500 pieces comfortably. Two lots running side by side in the same building can often be covered within one and a half days rather than two, because carton selection, opening and closing routines are shared. Where a programme has three lots finishing in the same week, the third lot's incremental inspection cost can fall to little more than the extra hours.

What does not consolidate is documentation. Every additional style carries its own drawing, defect annex and golden sample file, and if each of those is a separate hand-made document, the cost per style stays flat while volume grows. This is the point at which most programmes either plateau or get expensive, and it is entirely a structural question rather than a sourcing one. Eighteen slab copies of the same defect list is not eighteen specifications; it is one specification with eighteen opportunities to be out of date.

QC file folders and golden reference units for several handbag styles organised in one laboratory cabinet
Inspection days consolidate and get cheaper per style; documentation does not, unless the architecture is shared from the start.

Where the Money Actually Goes at Scale

Split the spend and the reason becomes obvious. Roughly sixty per cent of a growing programme's quality cost is people inspecting, twenty-five per cent is chamber and laboratory testing on components, and fifteen per cent is administration — maintaining the files, reconciling versions, answering questions that the documents should have answered unaided. Only the first of those three falls with scale naturally.

Which quality costs fall with volume and which quietly rise
Cost lineBehaviour as styles growWhy
Inspection man-daysFalls per styleSeveral lots share one visit and its fixed routines
Component testingFalls sharply per styleOnce tested, a component stays tested if its source is unchanged
Specification upkeepRises unless sharedEvery copied page becomes another version to reconcile
Defect resolution timeRises unless classifiedEach new style brings questions nobody has answered before
Training new staffRises unless templatedUndocumented judgements must be re-taught per style

That last pair is what separates the two kinds of eighteen-style programme. The one with a shared architecture answers a new style in an afternoon, because ninety per cent of the specification already exists and only the differences need writing. The one with per-style documents spends four days rediscovering decisions it already made eleven times, and usually reaches a slightly different conclusion each time — which is how two styles in the same collection end up with incompatible tolerance bands.

The Four Triggers That Upgrade a Style

Not every style deserves the same depth, and pretending otherwise wastes money on products that do not need it while leaving genuinely risky products under-covered. Four conditions are enough to decide.

  1. New construction. A silhouette the line has never made gets an inline visit plus twelve-unit dimensional measurement rather than five, until it has passed two lots cleanly.
  2. New material or new component source. A first leather or a first hardware partner gets full component testing: cycling, static pull and chamber work, regardless of how simple the style is.
  3. Functional claim. Anything that must perform — a device sleeve, a fit-driven strap, a closure given a specific retention load — gets testing on quantities rather than visual checks.
  4. Compliance exposure. Children's items, and anything sold into markets with specific substance restrictions, gets per-component restricted substance verification rather than reliance on a past pass.

Every other style runs the standard set. In most programmes that means roughly one style in four carries extra cost in its first lot, dropping to one in ten in subsequent seasons as constructions and components become proven. The result is a quality budget that grows far more slowly than the collection, which is what scaling actually means in practice. The nine QC practices list is the standard set referred to here, and worth keeping as the baseline layer.

One Specification Architecture, Not One per Style

The structure that keeps the eighteenth style cheap has three layers. A general specification covers everything true of every bag the brand makes: defect classes with examples, measurement conditions, thread and needle defaults, reference-edge conventions, packaging and marking. A style annex carries only what differs: dimensions with tolerances, the six load joins, materials, and the finish or colour notes. A lot file records what happened: the revision in force, golden sample photographs, the inline note and the final report.

  • Nothing is repeated. If two annexes carry the same sentence, that sentence belongs in the general specification.
  • Revisions are numbered together. Annex R3 against general specification v2.1 is unambiguous; two files each called 'latest' are not.
  • The general layer changes rarely and deliberately. A change there touches every style, which is exactly why it should be slow and reasoned.
  • The annex is the only layer that changes often. Adding a style therefore means adding a short document, not rebuilding a long one.
three-layer specification structure with a general document, per-style annexes and per-lot files on a desk
Three layers: general specification, style annex and lot file. Only the middle layer changes when a new style arrives.

A useful test for whether the architecture is working: ask how long it takes to write the specification for a new colourway of an existing style. If the honest answer is under an hour, the structure is doing its job. If it involves opening a previous file and saving it under a new name, the structure is a filing system rather than a specification, and its cost will scale linearly forever.

Tiering Inspection Depth by Style Risk

Three tiers cover most ranges. Tier one is a proven style of proven construction with an unchanged component source: final inspection only, standard sample sizes, no chamber work. Tier two adds an inline visit at 15-30 per cent completion and twelve-unit dimensional measurement. Tier three adds component testing and, for the first lot of anything new, retained-unit destruct testing at six units rather than three.

Three inspection tiers, and what belongs in each
TierApplied toWhat it includesRough cost index
OneProven style, proven partsFinal inspection under ISO 2859-1 Level II1.0
TwoNew silhouette or new colourwayPlus inline visit at 15-30 per cent, 12-unit measurement1.6
ThreeNew construction or new component sourcePlus component cycling, load and chamber testing2.4
DowngradeTwo clean lots at a tierMove down one tier, keep the golden sampleLower by about 40 per cent

The rule that makes this work is symmetrical: styles climb tiers automatically on a trigger, and step back down after two consecutive clean lots. Without the downgrade rule, every style drifts permanently to tier three and the savings never arrive. With it, a mature programme typically settles with twenty to thirty per cent of styles at tier three, forty per cent at tier two and the remainder at tier one.

What a Shared File Structure Looks Like

Naming conventions carry more weight than they appear to. One folder per lot, named from four fields — purchase order number, style code, colourway and ship date — means anyone a year later can locate everything about a shipment without opening three systems. Inside it, four items: the revision-in-force annex, the golden sample photographs, the inline note if one was taken, and the final report with one conclusion line at the top.

  • One conclusion line per report. Whether the defect family was systemic or incidental is the sentence that changes the next specification.
  • Photographs attached, not linked. Linked images break within about two years with tedious reliability.
  • Rectification notes filed with the lot. What was fixed, how many units, and who paid, since that pattern repeats.
  • Component test certificates filed once, referenced many times. Put them against the component code rather than against each lot that used it.

That last item is a quiet source of savings. A chamber test certificate for a metal component stays valid for as long as the component source and its plating process are unchanged, so it belongs to the component rather than to the order. Filing it once and referencing it from every subsequent lot removes a charge from every repeat purchase, which across eighteen styles is a genuinely meaningful number by the end of a year. Sedex and BSCI audit frameworks both expect exactly this traceability, so the same structure serves a compliance visit at no extra effort.

The Cost of Getting the Structure Wrong

The failure mode is specific and easy to recognise in hindsight. A programme reaches ten or twelve styles, quality cost per style has not fallen at all, and inspection reports start disagreeing with one another because two documents define the same defect differently. Nothing has broken visibly; the brand simply pays tier-three prices for tier-one products, forever, and every new style adds another document whose differences from the others nobody can recall.

There is a second cost that does not appear on an invoice. Undocumented judgements have to be re-made by whoever is in the room, so quality outcomes become dependent on individuals rather than on method. That is tolerable with one person checking three styles and unmanageable at eighteen, and it is the reason some brands find their quality inexplicably declining just as their volumes justify doing the work properly. The remedy is unglamorous — write the general layer once, properly — and it is considerably cheaper than discovering the gap in a container. How each defect gets classified in the first place is covered in the quality control reference.

A Two-Quarter Plan for Moving up a Tier

For a programme sitting at two or three styles preparing to grow, the sequence below takes roughly two quarters and does not require stopping anything. It assumes the stitching and hardware defect family definitions have already been settled, since those form most of the general layer.

  1. Weeks 1-2: write the general specification — defect classes with examples, measurement conditions, thread defaults, reference-edge conventions.
  2. Weeks 3-4: convert existing styles to annexes against it, noting every place they conflict, then resolve each conflict once.
  3. Weeks 5-8: establish tiering and apply the four triggers to the existing range, writing each style's tier into its annex.
  4. Quarter two, weeks 1-4: introduce the downgrade rule and run the first two lots under it, checking that nothing degrades.
  5. Quarter two, weeks 5-8: consolidate inspection visits for styles shipping in the same week and measure the saving per man-day.

The expected result at the end of two quarters is a drop of roughly twenty-five to thirty-five per cent in quality cost per style, with inspection depth unchanged or higher on the styles that actually carry risk. Programmes that skip weeks 1-2 and go straight to tiering tend to reach the same place about six months later, having written the general specification three times in three slightly different forms.

Triggers for Going Back Down a Tier

The downgrade rule needs conditions written down, otherwise nobody ever applies it. Three are sufficient: two consecutive clean lots at the current tier with no critical defects and no systemic major family; no change to construction, material or component source since the last predicted pass; and no open rectification note older than sixty days. Meet all three and the style moves down one tier from the next lot.

One caution on the first condition. 'Clean' has to mean something countable, not merely that nobody complained. A lot that passed with five majors found against an accept number of seven is not clean in any useful sense — the operating characteristic curve under ISO 2859-1 means such a lot has roughly a genuine defect rate near the limit — and downgrading on that basis steadily erodes protection. Set the bar at a number: downgrade when two consecutive lots sit below half the accept number, not simply below fail.

Sample Size Under ISO 2859-1 at Each Lot Size

The standard inspectors work to scales the sample to the lot, and the relationship is not linear: a lot four times larger is not inspected four times as hard. Knowing the sample size and the accept number at each lot size is what makes a report readable, and it is what stops a buyer treating a pass on 50 units as evidence about 5,000.

General inspection level II sample sizes and accept and reject numbers at AQL 2.5
Lot sizeCode letterSample sizeAcceptReject
51-90E1301
91-150F2012
151-280G3223
281-500H5034
501-1,200J8056
1,201-3,200K12578
3,201-10,000L2001011
  • A 500-piece lot is 50 units with an accept of 3. Finding three majors passes the lot and says nothing comfortable about the other 450.
  • The operating characteristic curve matters. A lot accepted at the accept number has a genuine defect rate near the limit, which is why the downgrade rule uses half the accept number.
  • Switching rules change the sample. Tightened inspection after two rejected lots raises the sample size without raising the cost of the visit.

Defect Classes and the Numbers Attached to Each

Three classes and three numbers turn a report from an opinion into a decision. Critical defects are zero-acceptance at every lot size because they are safety or compliance failures. Majors and minors carry the accept numbers the standard sets, and the distinction between them is the single judgement most programmes never write down, which is why two inspectors can read the same bag differently.

The three defect classes, with examples and the number each one carries
ClassAccept at a 500-piece lotExamplesAction on failure
Critical0Broken needle fragment, exposed sharp edge, restricted substance failureLot rejected and quarantined
Major3 of 50Strap attachment short, zip that jams, panel colour outside Delta E 2.0Re-sort and rework before release
Minor5 of 50, counted separatelyThread end over 3 mm, edge paint uneven, label off position by 2 mmRecorded; passed unless the count exceeds the number
  • Write the examples into the general specification. A class without examples is a class that will be argued about at the inspection table.
  • Critical is never negotiable. Zero accept means zero, and a single critical in 50 units stops the lot.
  • Count separately. Majors and minors are drawn against different accept numbers; adding them together is the most common reporting error.

Four Numbers to Track Each Quarter

Cost per style is the number the tiering is judged on, but it is a lagging measure and it does not say whether inspection got better or simply cheaper. Four measures together do: quality cost per style, defects per hundred units, first-pass yield and re-sort hours. Track them per lot and the fourth one tells you when a tier change is working.

Four quarterly quality measures, with a target band and what each reveals
MeasureTarget bandWhat it revealsReview action
Quality cost per style per lotUSD 30-95 depending on tierWhether consolidation is workingBelow target, look at shared visits
Defects per hundred unitsUnder 2.0 on a proven styleWhether specification drift is happeningAbove 3.0, revisit the general specification
First-pass yield at final inspectionAbove 95 per centWhether the inline visit is catching anythingBelow 90 per cent, move the style up a tier
Re-sort hours per failed lotUnder 8 hoursWhether defect families are systemic or incidentalAbove 12 hours, classify the family properly
  • Track per lot, not per year. A yearly average hides the one lot that cost three times the rest.
  • First-pass yield is the cheapest measure. It is already on the inspection report and it predicts next quarter's cost better than anything else.
  • Set the review at quarter end. Four numbers reviewed quarterly beats a spreadsheet reviewed never.

Tell us how many styles you run and we will return a tiering plan with per-style inspection depth and a general specification skeleton to build on. Get a Quote → /contact-quote/

Frequently Asked Questions

How much does quality control cost per style on a growing handbag range?

Roughly USD 60-95 per style per lot at three styles, USD 45-70 at nine and USD 30-55 at eighteen, assuming lots of 500 pieces and a man-day in the USD 220-320 range. Those falls come from consolidating inspection days and reusing tested components. Programmes that copy documents per style see the number rise instead, because upkeep grows faster than anything else.

When should a style receive more inspection than the rest of the range?

Four conditions: a construction the line has not made before, a new material or component source, any functional claim such as device clearance or strap fit, and any compliance exposure such as children's items. In most programmes one style in four qualifies in its first lot, falling to about one in ten in later seasons as parts become proven.

What is the difference between a general specification and a style annex?

The general specification holds everything true for every bag the brand makes: defect classes, measurement conditions, thread defaults, reference edges, packing and marking. The annex holds only what differs between styles: dimensions with tolerances, load joins, materials and finish notes. Adding a style then means writing a short annex rather than rebuilding a long document.

How many inspection tiers are worth maintaining?

Three is usually enough: final inspection only for proven styles, plus an inline visit and twelve-unit measurement for new silhouettes, plus component cycling and chamber testing for new constructions or sources. What makes it work is the symmetric rule — climb automatically on a trigger, step down after two consecutive clean lots — which keeps the range from drifting to the most expensive tier permanently.

What does a clean lot actually mean for downgrading purposes?

Something countable. A lot that passed with five majors against an accept number of seven is not clean, because under ISO 2859-1 the operating characteristic curve places its true defect rate close to the limit. A workable rule is two consecutive lots below half the accept number, with criticals at zero and no systemic family identified.

How should lot files be named and organised?

One folder per lot named from four fields: purchase order number, style code, colourway and ship date. Inside it put the revision-in-force annex, golden sample photographs, any inline note, and the final report with a single conclusion line stating whether each defect family was systemic or incidental. Attach images rather than linking them, since links break reliably within a couple of years.

Do component test certificates expire?

They stay valid as long as the component source and its process — particularly plating — remain unchanged. File the certificate against the component code rather than against each order that uses it, then reference it from subsequent lots. Doing this removes a recurring charge from repeat purchases and satisfies the traceability expectations built into Sedex and BSCI audits at the same time.

Can a small three-style brand justify building the shared architecture now?

Yes, and it is considerably cheaper at three styles than at fifteen. The general layer takes around two weeks to write properly, and it becomes progressively harder to extract later because by then eleven conflicting versions exist and every reconciliation requires a decision nobody remembers making.

What happens if inspector reports start disagreeing across styles?

That is the clearest signal the architecture is missing. It means the same defect is defined in two documents with slightly different language, so identical units are being judged differently depending on which page was opened. Fix it at the general layer once rather than patching each annex, then check whether past lots need re-reading.

Does quality improve or degrade as a range grows?

It depends almost entirely on documentation. Well-specified programmes improve, because each lot adds learning to a shared file and triggers genuine improvement. Poorly specified ones degrade even with good people, because undocumented judgements must be re-made from scratch and outcomes start depending on who happened to be in the room rather than on method.

People Also Ask

Why does QC cost per style fall as a range grows?

Because an inspection visit is priced per day rather than per style, so lots finishing in the same week share carton selection and opening routines, and the incremental cost of a second lot might be little more than the extra hours. Component testing also amortises once the source is unchanged. Only documentation fails to consolidate, which is why structure decides whether the saving appears at all.

Is it ever right to reduce inspection on a proven style?

Yes, provided it is rule-driven and countable. Two consecutive lots below half the accept number, no critical defects, no systemic major family, and no change to construction, material or source together justify stepping down a tier. Reducing depth out of budget pressure rather than evidence is how a mature range quietly accumulates defects nobody is looking for.

How do you stop versions of a specification getting out of sync?

Keep anything true of every style in one general layer and hold style-specific facts in short annexes, numbered against a general specification version. If the same sentence appears in two annexes it belongs in the general layer. Numbering revisions together means an annex R3 against a general v2.1 is unambiguous, whereas two files each named latest are not.

Sources and further reading

Every figure on this page is either our own programme data or attributed below. Open the originals before you write them into a specification.