How to Qualify and Approve an Apparel Supplier

The question that exposes how a supplier was really approved is boring and effective: what evidence do we have, and what is it evidence of? Very often the answer is an audit report about labour conditions, a certificate about a management system, and one sample that came back nicely, three documents that between them say almost nothing about whether ten thousand pieces will arrive correct in eleven weeks.

Six stages that are not each other

Conceptual buyer framework, not an industry standard. Onboarding operationalises an approval; it does not create one.

Two more distinctions are worth making at the start. Selection is deciding which candidate looks best; approval is deciding whether the evidence supports using them, and for what. And the activities that produce evidence, such as an audit, a visit, a sample or a document review, are not themselves approval. They are inputs to a decision somebody still has to make.

What each kind of evidence actually proves

Each source answers only the question inside its own scope. None of them is the decision.

None of this is an argument against audits or certification. An audit report is genuinely informative once you know what its scope was, and how to read one is covered in reading a factory audit report. The point is narrower: each source answers the question it was designed for, and stacking several of them does not produce an answer to a question none of them asked.

Approved for what?

"Approved supplier" used without a scope is close to meaningless. It is not an independent certification and no third party issues it. It is an internal status one buyer grants for its own purposes. The same factory can be approved by one buyer and not another, and approved by one buyer for one thing and not another. Nor does approving an organisation approve the parts it supplies: that is a separate layer, described in trims and components. Product-safety controls such as needle and foreign-metal control are a further capability to assess on their own terms.

Approval at a wider level does not carry down to a narrower one. Not every approval needs every level.

• Company is not site. A supplier may operate several factories, a separate sampling room, an external finishing unit and subcontracted sewing. Approving the legal entity does not establish that every physical site is equivalent, though requiring formal site-by-site approval everywhere is disproportionate for most programmes.
• Site is not product. A facility that runs jersey cut-and-sew well is not thereby qualified for seam-sealed outerwear, structured tailoring or certified protective equipment. Those are different machines, different operators and different process control.
• Product is not process. A factory can make the garment and send the embroidery, the printing, the dyeing, the washing or the seam sealing somewhere else. Where a critical process sits outside the approved site, it is worth knowing.
• Programme adds requirements. A buyer's own compliance requirements ride on top of all of it, and they are the layer most likely to be discovered late.

What is actually made where

Subcontracting is normal and is not a problem in itself. Very few apparel factories knit their own fabric, dye it, and run every decoration and finishing process in-house, and a supplier that manages good external partners may produce better results than one insisting on doing everything badly. The issue is visibility, not outsourcing.

• Where is cutting done, and where is sewing done?
• Is decoration in-house, and which techniques?
• Where is fabric knitted or woven, and where is it dyed?
• Is washing, seam sealing or any specialist finishing subcontracted?
• Where is final packing done?
• Which of those sit at a different site from the one you assessed?

The reason this belongs in qualification rather than in a questionnaire is that the answers define what was actually approved. If a programme depends on a particular site, process or compliance status, and production later moves elsewhere without that being reviewed, the approval no longer describes what is happening. How that is handled once production starts belongs in the written arrangement, covered in supplier quality agreements.

Capacity: verified, not reserved

A stated monthly output is a description of a factory. Qualification adds a second question to it, not merely whether the volume exists, but whether it exists for this product.

• Product-specific throughput. A basic tee and a lined, decorated jacket do not run at the same rate on the same floor, so a headline figure says little about your style.
• Relevant machine and process availability, rather than total machine count.
• The normal load, and what the seasonal peak looks like, since capacity in a quiet month is not capacity in the month you need.
• Upstream material dependency, which is usually the real constraint rather than sewing minutes.
• Subcontracted capacity, which may be shared with other customers in ways nobody has visibility of.

Development, and where product approval sits

For custom apparel, some development work is almost always part of qualification, but it is worth being precise about what it demonstrates. A sample proves that this supplier, in its sample room, produced this item once. That is real information and it is not bulk readiness.

• What each sample stage proves is already defined in the sampling process, and this guide does not redefine it.
• A pre-production sample is closer to the truth than a development sample, because it is made in bulk materials on the intended route.
• A pilot or first small production run exercises the bulk line rather than the sample room, and tells you more about repeatability than any sample can. It also costs real money and is not proportionate for every programme.
• Some buyers treat a first bulk order as a higher-monitoring phase. That is a reasonable approach and it is not a rule, and this guide does not prescribe an inspection level for it.

Approval is a state, not a badge

It helps to have language for the fact that suppliers sit at different points. The set below is a conceptual buyer framework rather than an industry standard, and nothing about it should be styled as a certificate.

• Not assessed. Known, but nothing has been established.
• Under qualification. Evidence is being gathered; not yet a decision.
• Conditionally approved. Usable within a defined scope with specific open items, such as a material evidence gap, a packaging validation or an agreed action. Whether production may proceed under a condition depends on what the condition is; some conditions should stop an order and some should not.
• Approved for a defined scope. The normal state, and the scope is the substance of it.
• Suspended or under review. Something changed, or performance did.

None of these should imply a permanent property of the factory. Approval goes stale, and usually because something changed rather than because time passed: a production site moves, ownership or management changes, a critical process is subcontracted differently, a material source changes, a compliance document lapses, the product scope expands, or performance deteriorates in a way that has not been resolved.

Onboarding: making an approval operational

Once a supplier is approved, a separate and much more mundane job begins: making sure both sides know how to work together correctly. This is not a capability question and it should not repeat qualification.

What a register should record

If approvals are written down at all, the useful version records the scope rather than a status flag. A list of supplier names against a tick answers no question anybody actually has.

Before the first bulk order

After the first order ships, the question changes again. Performance management takes over, meaning what actually happened against agreed requirements, and it is covered in managing supplier performance. Approval is what let the supplier start; performance is what tells you whether the decision was right, and it should feed back into the scope rather than sitting in a different file.