CNCN Ally
← Back to blog
Quality Control

How to Write a Product Specification Your QC Team Can Use

CN Ally Team·April 25, 2026

A product specification template for QC that inspectors can actually work from: every section your spec needs, the five ways specs fail, how inspectors use the document on inspection day, and a weak spec rewritten strong.

A usable product specification is a document that lets a stranger decide, without calling you, whether any given unit passes or fails. If your spec cannot do that, it is a wish list, not a specification. A product specification template for QC usually runs ten sections: version control, product description, materials and bill of materials, dimensions with tolerances, colors and finishes, functional and test requirements, packaging, labeling, acceptance criteria, and the reference samples that sit next to it on the inspection table.

Most quality disputes trace back to a spec that said "good quality" and meant nothing measurable. As a China sourcing agent, CN Ally treats the spec as the first deliverable on a new product, written before any supplier is contacted. Everything downstream, from the golden sample to the pre-shipment inspection, judges itself against this document. Get it right and inspections become routine. Get it wrong and every inspection turns into an argument.

This guide gives you the full template, shows how an inspector actually uses it on inspection day, walks through the ways specs typically fail, and ends with the same specification written twice: weak, then strong.

What a product specification actually is (and what it isn't)

A product specification is a contract-grade description of what you are buying. Not a marketing blurb. Not a mood board. A set of statements precise enough that two people who have never met, the factory technician and the inspector, can independently agree on whether a unit conforms.

"Good quality" is the most expensive phrase in importing, because it costs nothing to write and everything to argue about. Compare it with "powder-coated matte black, no visible scratches at 50 cm under standard office lighting." The first is an opinion. The second is a test an inspector can run. Every line of your spec should move toward the second kind of sentence.

A spec has three readers. The factory's production manager reads it as instructions: what to buy, what to build, what to print on the box. The inspector reads it as a test plan: what to measure, what to compare, what to reject. And months later, when a shipment arrives wrong, both sides read it as a judge: who promised what. Writing for all three readers at once is the whole skill.

The reference guide at QC China puts it plainly: a spec sheet is not only for the factory but for the independent inspector, who compares the state of the products against your specifications. Internalize that before you write a word. You are writing for the inspector's clipboard as much as for the production line.

Every section your spec needs

Here is the full template. Each row is a section, what belongs in it, and how the QC team puts it to use.

# · Section · What goes in · How QC uses it

  • 1: Header and version control · Product name, SKU, spec revision number, date, author, who approved it · Confirms the inspector and factory are working from the same revision; every report references it
  • 2: Product description · One paragraph: what the product is, who uses it, key features · Frames every judgment call; "intended use" decides what counts as a functional defect
  • 3: Materials and BOM · Every material, component, coating, ink, adhesive, battery; approved suppliers where it matters · Catches material substitution, the most common silent cost-cut; inspector checks against the BOM
  • 4: Dimensions and tolerances · Every critical dimension as nominal value plus tolerance (e.g., 260 ± 2 mm) · The measurement checklist; without tolerances there is no pass/fail line
  • 5: Colors, finishes, appearance · Pantone (PMS) codes, finish type, gloss level, cosmetic standards, defect catalogue with photos · Cosmetic inspection criteria; photos of acceptable vs. reject examples
  • 6: Function and test requirements · What the product must do, and exactly how to test it: method, equipment, pass criteria · The inspector runs these tests verbatim during inspection
  • 7: Packaging · Retail packaging spec, master carton spec, packing method, drop-test or transit standard · Checked at packing stage and during loading; prevents the "perfect product, destroyed box" outcome
  • 8: Labeling and markings · Barcodes, country of origin, care labels, regulatory marks, artwork file versions · Verified piece by piece; wrong labels are a classic inspection failure
  • 9: Acceptance criteria · AQL levels per defect class, inspection level, what happens on fail (rework, re-inspection terms) · The verdict rules; the inspector's accept/reject math comes from here
  • 10: Reference samples · Golden sample ID, who holds copies, photos, dimensional report attached · The physical tiebreaker; every dispute resolves against the signed sample

A few of these sections deserve extra attention because they are where specs most often go soft.

Tolerances are the pass/fail line. A dimension without a tolerance is a suggestion. "Height 260 mm" invites the factory to deliver 257 and argue it is close enough. "Height 260 ± 2 mm" ends the argument before it starts. Decide which dimensions are critical (they affect function or fit), which are major (visible, affect perceived quality), and which are minor. Put the tight tolerances where they matter and looser ones elsewhere.

Test methods must be executable. "Must be durable" is not a test. "Drop test: 1.2 m onto concrete, 3 drops, no cracking or functional loss" is a test. For each functional requirement, write the method, the equipment, the conditions, and the exact pass criterion.

The BOM is your substitution alarm. Factories under margin pressure swap materials: thinner steel, cheaper plastic resin, a different battery cell. If the spec names the material grade and the approved component, the inspector can flag the swap.

How your inspector uses the spec on inspection day

Understanding the inspector's workflow changes how you write. Here is what actually happens with your document.

The inspection opens with a short meeting where the inspector confirms the spec revision, the purchase order quantity, and the golden sample. Every defect found later gets judged against these three references.

Quantity verification comes next, measured against the spec's order quantity and carton counts. Then workmanship: the inspector pulls samples per the AQL plan and compares each one against the spec's appearance section and the golden sample, side by side. Dimensions get measured at the points the spec defines. Functional tests run exactly as the test section describes. Packaging and labeling get checked against sections seven and eight.

When the inspector finds a defect, the spec decides what happens. The defect catalogue says whether a scratch is minor or major. The AQL table says how many are allowed. If your spec is silent on a defect type, the inspector either flags it as an observation or makes a judgment call you may disagree with.

The report the inspector sends you that evening references your spec by revision number, section by section. That is why version control sits at section one. For the full walkthrough of what inspection day looks like from the buyer's side, our pre-shipment inspection guide covers the timeline in detail; this article is about the document that makes that day work.

The five ways product specs fail

After the template, the failure modes. These are the patterns behind most spec-related quality disputes.

1. Vague language with no measurable threshold. "High quality materials." "Nice finish." "Sturdy construction." Every one of these is an argument waiting to happen. For each adjective, ask what an inspector would measure. If nothing, rewrite the line.

2. Dimensions without tolerances. A surprising number of specs list dimensions to the millimeter and tolerances to none.

3. No golden sample, or photos as the only reference. Photos lie about color, texture, weight, and feel. The golden sample is the physical anchor: signed and dated by both sides, one copy with you, one on the factory floor, with high-resolution photos and a dimensional report attached. Industry practice is unambiguous here. A well-known piece on sample-to-bulk drift puts it bluntly: every quality dispute gets resolved against the physical object, not against photos or memories, and "good quality" is not a spec. Measurable numbers are.

4. Written for the wrong reader. Western companies often hand their factory the same spec they would give a domestic supplier, full of idioms, assumptions, and implied standards. The factory's English-speaking salesperson is rarely the person who programs the machines. Renaud Anjoran's classic quality-assurance guidance makes three points that still hold: write requirements in precise terms with no room for interpretation, have the spec translated into Chinese so meaning is not filtered through a non-technical salesperson, and get a manager's signature on both the spec and the approved sample. A signature at the bottom of the document, he notes, is a powerful reminder when it is needed.

5. Version drift. The spec gets updated after a sample round. The update goes to the salesperson's inbox. The factory floor and the inspector keep working from the old PDF. The discipline is simple: every change gets a new revision number, a date, and a re-send to everyone, with the old revision marked superseded.

Before and after: the same spec, rewritten

Theory is cheap. Here is a short spec for a 750 ml insulated stainless bottle, first as most importers write it, then as an inspector can use it. The product is illustrative; the pattern is what matters.

Before: the wish list.

750 ml insulated water bottle, stainless steel, matte black. Good quality, no scratches. Leakproof lid. Nice gift box packaging. Must pass our quality standards.

An inspector receiving this can verify the volume, more or less. Everything else is judgment. "No scratches" at what distance, under what light? "Leakproof" tested how, for how long? And "our quality standards" are nowhere in the document.

After: the usable spec.

Product: Insulated stainless bottle, 750 ml, matte black. SKU WB-750-BLK. Spec rev 2.0, dated 2026-09-23.

Materials: Body 304 stainless steel, 0.5 mm wall; double-wall vacuum insulation; lid PP food-grade with silicone seal ring. No material substitution without written buyer approval.

Dimensions: Height 260 ± 2 mm; diameter 73 ± 1 mm; weight 380 ± 15 g empty.

Finish: Matte black powder coat. Cosmetic standard: no visible scratches or chips at 50 cm under standard office lighting; minor marks under 0.5 mm acceptable as minor defects.

Function: Leakproof: filled, inverted, and shaken for 30 seconds, zero leakage. Insulation: 500 ml water at 95°C, after 6 hours ≥ 60°C. Lid opens and closes 500 cycles without thread failure.

Packaging: Individual white gift box, 280 × 90 × 90 mm, 350 gsm artboard, logo per artwork file v3. Master carton 12 pcs, drop-tested per ISTA 3A.

Labeling: Barcode per file v2 on box base; "Made in China" molded on bottle base.

Acceptance: AQL 1.5 major, 4.0 minor, 0 critical; inspection level II. Failed lot: factory reworks within 7 days, re-inspection at factory's cost.

Reference: Golden sample GS-WB-023 signed 2026-09-10, copies held by buyer and factory.

Same product. The second version can be inspected by someone who has never seen the bottle: every adjective became a number, every requirement got a test, the failure path is written down before anyone needs it.

Get it signed, translated, and attached to the order

A spec only works if it is the spec everyone is using. Four habits keep it that way.

First, both sides sign and date the spec and the golden sample. People treat signed documents differently from emailed ones.

Second, translate the spec into Chinese. Not machine translation of the final PDF, but a proper translation by someone who knows the technical terms, reviewed against the English original. The production floor works in Chinese. If your requirements only exist in English, they have been summarized by the salesperson, and summaries lose the tolerances first.

Third, attach the spec revision to the purchase order. The PO should name the spec revision it is issued against. When the factory confirms the PO, it confirms that revision. This closes the version-drift loophole from the buyer's side.

Fourth, freeze the spec before compliance testing and keep a change log. If the factory changes a material or component mid-production, earlier test reports may no longer describe the product, and the relevant approvals restart.

Our quality control overview places the spec inside the full QC lifecycle, and the AQL guide will help you set the acceptance numbers in section nine. If you would rather not write the document alone, CN Ally drafts, translates, and version-controls product specs as part of its quality control service. Email hi@cnally.com and bring whatever you have, even if it is the wish-list version.

The spec review cadence: keeping the document alive

A specification is not a write-once document. Products evolve, suppliers change materials, and every quality incident teaches something the spec should have said. Without a review cadence, the spec quietly goes stale and the factory reverts to its own judgment.

Review the spec on three triggers. After every quality incident: each corrective action should end with a spec revision, whether it's a clarified tolerance, a new checkpoint, or a photo of the acceptable limit. Before every reorder with changes: new packaging, a different component, a revised logo — all go into a new revision that both sides sign. Annually for stable products: materials get discontinued, regulations change, and the factory's "equivalent" substitution needs to be captured in writing before it becomes the default.

Version control is what makes this work. Number every revision, date it, note what changed, and name the revision on the purchase order. When a dispute arises six months later, the question "which spec were we building to?" should have a one-line answer. The factories that resist version control are usually the ones that benefit from ambiguity; insist anyway.

Do I need a spec sheet if I already approved a golden sample?

Yes. The golden sample shows what right looks like; the spec says what right means in numbers. A sample cannot state tolerances, test methods, AQL levels, or packaging requirements. Inspectors need both.

Who should write the product specification, me or the supplier?

You own it. The supplier can contribute technical detail, but the buyer writes the requirements because the buyer defines acceptable. A supplier-written spec tends to describe what the factory finds convenient to build.

Should my spec be translated into Chinese?

Yes, and by someone who understands the technical vocabulary. The English version remains the controlling document if there is a conflict, but the Chinese version is what the production floor actually reads. Skipping translation means your tolerances pass through a salesperson's summary, which is where precision goes to die.

What happens if the supplier ignores the specification?

That is what section nine is for. The acceptance criteria define the consequence, rework, replacement, or re-inspection at the factory's cost, before the dispute starts. With a signed spec attached to the PO, you have a documented basis for the claim.

How detailed should a spec be for a simple product?

As detailed as the failure modes require. A simple product still needs dimensions with tolerances, finish standards, packaging, labeling, and acceptance criteria. The template scales down naturally; it does not disappear.

Can I change the spec after production starts?

You can, but every change needs a new revision number, both signatures, and confirmation of what happens to units already produced. Mid-production changes are where version drift does its worst damage, so the bar should be high: change only for real problems, never for preferences you could have settled during sampling.

How often should I update my product specification?

Update it after every quality incident (each corrective action should end with a spec revision), before every reorder that includes changes, and annually for stable products. Number and date every revision, and name the revision on the purchase order so there's never ambiguity about which version the factory built to.

The one-page test: is your spec ready?

Here is the decision rule. Print your spec, hand it to someone who has never seen the product, and ask them to describe exactly what would pass and what would fail. If they can, with numbers, your spec is ready for the factory and the inspector. If they hesitate or ask what you meant, the weak lines are the ones they stumbled on.

A specification is the cheapest quality control you will ever buy. It costs a few hours at a desk and it governs every inspection, every sample round, and every dispute for the life of the product.

Need help sourcing this kind of product?

Our team handles supplier verification, QC inspections, and logistics every day.

Get a Free Quote

Ready to source smarter from China?

Tell us what you want to source. We'll reply with vetted factory options and pricing within 24 hours — free, no obligation.