One Quality Checklist Doesn't Fit All: How I Sort Specs into Three Categories

When I first started reviewing specifications, I made a rookie error: I assumed a spec was a spec. Same tolerance, same inspection checklist, same everything—just swap the material name at the top of the page. Four years and roughly 200 rejected batches later, I know that doesn't work.

The things that go wrong with a technical outerwear fabric are not the things that go wrong with a decorative textile. And neither of those is the same as the things that go wrong with a finished-product dimensional spec like a duvet cover. You can't apply one checklist to all three and call it quality control. You'll either miss the real failure points or waste time checking things that don't matter.

Here's how I split incoming requirements before I touch a checklist. Three categories. They're not perfectly clean—nothing in real procurement is—but they've held up across enough audits that I trust them.

Category A: Technical Performance Fabrics

If the material's job is to keep something out—water, wind, contamination—you're in Category A. This is Gore-Tex territory. The stuff you find in a Rossignol Gore-Tex jacket or a pair of Vans Gore-Tex shoes, where the fabric isn't judged on how it looks but on what it prevents.

What I verify first: hydrostatic pressure resistance. ASTM D751 or the equivalent. The number matters less than consistency across batches—a membrane that tests at 28,000 mm on one roll and 19,000 mm on the next is a problem even if both numbers clear your minimum.

Second: seam integrity. This is where most failures happen. A jacket can have flawless fabric and still leak at the shoulders if the seam tape wasn't applied at the right temperature. We run a water-spray test on finished seams before approving any batch. Not a visual check. An actual spray test.

They warned me about this early on. I didn't listen once—assumed a trusted supplier's seam tape was fine because it always had been. Forty units failed the rain-room test. The tape had been applied three degrees too cold. They redid it at their cost, but the launch slipped by two weeks.

Third: breathability. For Gore's membrane technology and similar laminates, this is measured as RET or MVTR. I won't get into the testing methods here—what matters is that you test the finished laminate, not just the raw membrane. A 2-layer and a 3-layer construction behave differently, and the supplier's spec sheet usually quotes the best-case number.

One more thing about Category A: the terminal product decides your test standard, not the fabric alone. A ski jacket for Rossignol needs different performance thresholds than a tactical boot. Same membrane, different acceptance criteria. Ask the brand what test protocol they use before the product goes to market. If they don't have one, write one together.

Category B: Fashion and Decorative Fabrics

Rayon nylon blends. Hammered satin. Fibers and weaves where the end user will judge the material in their hands, on a body, or on a shelf—not on a lab bench.

The failure modes here are almost the opposite of Category A. Nobody returns a rayon nylon fabric jacket because the hydrostatic pressure was 300 mm short. They return it because the shade looked different in daylight, or the fabric shrank two inches after the first wash, or the surface texture didn't match the sample.

Most buyers focus on fiber content. What they miss is finishing consistency. A hammered satin can have identical composition and still look wrong if the calendering tension was off, or if the dye lot shifted one shade. I've rejected more batches for surface uniformity than for composition errors, and the composition errors are the ones people actually check for.

What I verify, in order:

• Shade against the approved standard, under controlled lighting. Not the "looks close enough" version—a physical standard under D65 light.
• Dimensional stability after a 3-wash cycle. Rayon blends are notorious for shrinking past tolerance.
• Surface consistency across the roll width and between rolls. This is where hammered and textured fabrics get expensive to fix.
• Hand feel, compared to the original sample. Subjective, yes. Still the one that gets products returned.

(I should mention: we also check colorfastness to rubbing before cutting, not after. Catching that late is a $4,000 mistake on a 2,000-unit order.)

Category B is where small trial orders get under-reviewed most often. A 50-unit test run from a new brand sometimes gets a lighter checklist because "it's just a sample." No. A rayon nylon fabric first delivery and a hammered satin fabric production run both get the full set of checks, regardless of quantity. The cost of a bad sample is a lost customer, not a lost shipment.

Category C: Finished-Product Dimensional Specs

This is the category that surprises people. The question "what are the measurements of a king size duvet cover" isn't a fabric question at all—it's a dimensional spec question. And the same logic applies to any finished product where the primary acceptance criterion is "does it match the stated dimensions."

From the outside, a duvet cover looks like two rectangles of fabric sewn together. The reality is that the measurement protocol decides whether it fits the comforter—and that protocol has to be written before the order, not after the first complaint.

Here's what I use as a reference point, as of Q1 2025:

• US king size duvet cover: 104 × 90 inches (264 × 229 cm), matching a standard king comforter of the same dimensions.
• UK/European king: varies by market—225 × 220 cm or 240 × 220 cm depending on the brand's home standard.
• Standard tolerance: ±1 inch on width and length. Tighter than that needs a custom spec and a written supplier agreement.

The measurement method matters as much as the number. We specify: lay flat, no tension, measure at three points per side, report the average. A 104-inch cover measured under tension can read 105 or 106 and pass a careless check. Then it doesn't fit the comforter.

The failure mode in Category C is ambiguity, not manufacturing error. If the spec doesn't say how to measure, you're not inspecting—you're guessing. And the supplier will always measure in the direction that favors their batch.

For small brands ordering their first run of bedding or apparel where dimensions matter, the temptation is to skip the measurement protocol because "it's a simple product." A duvet cover is simple. A duvet cover that fits is a spec question. Write the method down before you place the order, not after the first return.

How to Tell Which Category You're In

Most confusion happens at the boundary. A waterproof jacket with a decorative print is technically both A and B. A duvet cover with a hammered satin finish sits between B and C. The category isn't about the product—it's about what would cause the order to fail.

Ask three questions:

1. What does the end user do with this product? If it needs to perform under specific conditions (rain, wind, strain), you're in A. If it needs to look and feel right, B. If it needs to fit something else, C.
2. What's the cost of a return? Performance failures are catastrophic and usually visible. Appearance failures are costly but manageable. Dimensional failures are cheap to produce and expensive to fix, because you're re-cutting, not re-sewing.
3. Who defines the standard? If the terminal brand has a test protocol, you're in A and their protocol wins. If the market defines the look, you're in B. If you define the dimensions, you're in C and you need to write the measurement method yourself.

If your product falls into two categories, check both. The stricter standard doesn't automatically cover the weaker one—a waterproof lining doesn't help you if the outer fabric shades differently under store lighting.

And if you're a small brand placing a first order that crosses two or three categories, don't let the supplier talk you into a lighter review because of order size. The batch that fails doesn't care how many units you ordered. The first delivery is the one that defines the relationship—for better or worse. Get the spec right at the start, and the conversation stays about the product instead of the problem.