What Is a Supplier Quality Agreement in Apparel?

Many quality problems in apparel are not caused by a factory that cannot make the garment. They come from nobody having agreed, in advance, what happens when the fabric supplier changes, when a trim is unavailable, when a lot fails inspection, or when somebody sends a revised measurement by email on a Friday.

Have the agreement reviewed for the relevant jurisdiction and project. General guidance cannot determine the rights or obligations of the parties to a specific contract.

Four documents, four different questions

The confusion is structural rather than careless. All four of these documents contain requirements, all four are sent to suppliers, and each one is regularly asked to do another one's job.

The vendor manual belongs to the buyer's whole supply base and is covered in supplier performance management; the purchase order is set out in apparel purchase orders; the specification layer is in tech packs and the bill of materials. A quality agreement sits between the manual and the specification: more specific than the first, more permanent than the third.

Supplier-level requirements, not style-level ones

A common drafting error is copying the tech pack into the agreement. Measurements, seam types, artwork placement and material references belong to the style and change with it; an agreement that restates them creates two sources of truth that will disagree within a season.

• Reference, do not restate. The agreement should point at the current controlled specification by name and revision, and let that document carry the detail.
• Keep what recurs. Responsibilities that apply across styles and orders, such as who inspects, what gets notified and how deviations work, are exactly what a style specification cannot hold.
• Say where the current version lives. An agreement that governs revisions but does not say where they are obtained is missing the point of itself.

Change control: notification is not approval

This is the section that does much of the work in practice, and the distinction it turns on is simple enough to be overlooked. Requiring a supplier to tell you about a change is not the same as requiring your permission before making it, and an agreement that fails to separate them either drowns the buyer in approvals or lets significant changes pass silently.

Notification is not approval, and the agreement is what says which changes need which.

The useful approach is to sort changes by what they touch rather than by how large they seem. A change that affects the approved product, the approved process, the compliance position or the site the approval was based on is a different category from an internal adjustment that leaves all four untouched.

• Manufacturing site, production moving to another facility, including one belonging to the same company
• Subcontracting, a critical process moving in or out, or to a different partner
• Fabric, a different mill, a different construction, or a different finish
• Trims and components, substitution of anything named in the bill of materials
• Decoration, a different technique, setup or subcontractor
• Construction or pattern, anything that changes how the garment is made or how it measures
• Packaging, where it affects labelling, assortment or how goods are received
• Compliance evidence, a certificate, test report or audit status that lapses or changes scope

Deviations, and the trap inside them

A deviation, sometimes called a concession, is an explicit, reviewed exception allowing production or shipment outside the normal specification in defined circumstances. Used properly it is a practical tool that keeps a season on track. Used loosely it quietly rewrites the product.

The same logic applies to how deviations are recorded. A verbal approval on a factory visit is not a controlled record, and neither is an email that names no style, quantity or duration. What matters is not a form, and this guide prescribes none, but that the affected product, the difference, the approval and its limits are all recoverable afterwards.

When production does not conform

An agreement is most valuable at the moment something has gone wrong, because that is when improvisation is most expensive. What it usually settles is sequence rather than blame.

• Tell the buyer, within a timeframe that reflects how serious it is
• Identify the scope, which lots, which quantities, and whether anything has shipped
• Hold what is affected rather than letting it move while the question is open
• Agree the disposition, which might be rework, repair, acceptance under a deviation, or rejection depending on the facts
• Follow with corrective action where the problem warrants it

What happens after the immediate problem is handled belongs elsewhere. The distinction between correction, containment, root cause and corrective action, and what makes a corrective action actually effective, is set out in supplier performance management. A quality agreement's job is to establish that the supplier will do those things and how it will communicate about them, not to re-teach them.

Who inspects, and against what

Inspection is a recurring responsibility, which is why it belongs at this level rather than in a style specification. The agreement settles who does it and when; the mechanics belong to the quality-control layer.

• Which stages are inspected, incoming materials, in-line, final, or some combination
• Who performs each one, whether the factory, the buyer or a third party
• What the criteria are, by reference to the agreed sampling and defect classification rather than by restating them. Those sit in quality control and, for materials, incoming fabric inspection
• What is reported, to whom, and by when
• What happens on a fail, connecting back to the nonconformity route above

When documents disagree

A real and under-discussed failure mode: the tech pack says one thing, the purchase order says another, the vendor manual implies a third, and somebody emailed a fourth. The factory has to build something, so it picks, usually the most recent message, which is usually the least controlled one.

• Decide which document governs for which kind of requirement, and make sure both sides know.
• Keep the specification as the specification. A quantity on a purchase order and a measurement in a tech pack are not competing claims about the same thing; conflicts usually arise where one document restates content owned by another, which is the argument for referencing rather than duplicating.
• Treat email as a request, not an instruction, unless the buyer's own process says otherwise. A message asking for a change is the start of change control rather than the end of it.
• Make revisions unambiguous. A revision number and a date are worth more than any amount of wording about precedence.

Formal precedence clauses are a legal drafting matter and this guide does not attempt them. The operational point stands on its own: ambiguity between documents produces defects and disputes, and the cheapest fix is to stop the same requirement living in two places.

Do you need one?

Often not. The question is whether the responsibilities above are controlled somewhere, not whether a particular document exists.

The worst outcome is a document that exists to be pointed at. If an agreement is written, the test of whether it was worth writing is whether anybody consults it the first time a fabric is unavailable or a lot fails, and whether what it says is specific enough to settle the question.