This page teaches the sequence of steps, and the sample types each step produces, that turn a written private-label brief into an approved first sample ready for bulk production, for a retail buyer or merchandiser who now owns a private-label specification and has to actually develop it. This lesson teaches a product-flow skill: a private-label style does not go from an idea to a shop shelf in one step; it passes through a fixed sequence of sample rounds, each one checked before the next is made.
Without following this sequence, a retailer risks committing to bulk production on a style that has never been properly checked for fit, construction or fabric behaviour. A brief on paper describes what a retailer wants; only a physical sample, made and checked, proves the factory can actually produce it. Skipping a step to save time usually means paying for that step later, once a problem is found in a much larger, much more expensive batch.
You need: Lesson 1 of this course, or an existing understanding that private label makes the retailer the specification owner. You should also be comfortable with basic tech pack contents (Track 5, Course 5).
By the end of this lesson you can:
Not covered here: what changes in the retailer's own role when it takes on private label at all (Lesson 1), protecting a style's own quality and consistency once it is in repeat production (Lesson 3), and building a complete private-label development tracker across every stage (Lesson 4).
| Term | Meaning |
|---|---|
| Product brief | A customer's description of a product's requirements, such as season, care, price point and look, often written without naming a fibre. |
| Proto sample | The first, rough sample made from the tech pack, often in the wrong fabric, to prove the design and construction idea works before investing further. |
| Fit sample | A sample made in the correct fabric at the sample size, checked against the size specification to prove the garment fits. |
| Sample approval outcome | The named result a buyer issues once a sample review is complete: approved, approved with comments, or rejected. |
| Private-label development cycle | The fixed sequence of steps, brief, proto sample, fit sample and approval, a private-label style passes through before bulk production starts. |
A private-label style's own development cycle starts with a written product brief stating what the retailer wants: construction, fabric, price target and look. The factory turns that brief into a proto sample, a rough first sample proving the construction idea works, often in a substitute fabric. Once the construction is proven, the factory makes a fit sample in the correct fabric, checked against the size specification. The retailer then issues a sample approval outcome: approved, approved with comments, or rejected. Only an approved fit sample clears the style to move toward bulk production.
| What can differ | The shapes you meet | Why it matters |
|---|---|---|
| Export vs. domestic development | An export private-label style, such as Fairway Stores' own T-shirt, adds a pre-production sample stage checked against bulk fabric before shipment; a domestic style on open account, such as Cedar & Co.'s own T-shirt, can move from an approved fit sample straight into a first production batch, since there is no overseas shipment risk to guard against separately | A domestic buyer copying an export order's full sample-round list onto a simple open-account style adds cost and time the shorter supply chain does not need |
| MTO vs. MTS vs. hybrid development | An MTO private-label style is developed once, for one confirmed quantity; an MTS style is developed once, then the same approved sample is reused as the reference for every future reorder, with no repeat approval round needed unless the spec changes; a hybrid style is developed as MTO first, then converted to an MTS reorder cycle once it proves it sells | Treating an MTS style's every reorder as if it needed a fresh full sample round from brief to approval wastes time the fixed reference sample already made unnecessary |
| Proto sample vs. fit sample | A proto sample proves construction only, often in the wrong fabric; a fit sample proves fit and fabric behaviour together, in the correct fabric | Approving a proto sample as if it were a fit sample risks confirming a garment that fits wrong or drapes wrong once made in the real fabric |
| Sample approval outcome | Approved clears the style to move forward unchanged; approved with comments requires a stated, specific change before moving forward; rejected requires a new sample from scratch | Treating "approved with comments" as a full approval skips the specific changes the comment sheet named, carrying an unfixed fault into bulk production |
| Product families | The same development cycle, brief, proto sample, fit sample, approval, applies to socks and hosiery, knit-to-garment, terry and towels, and home textiles and bedding, with each family's own sample types substituted where its construction differs | A retailer new to private label in one product family can reuse the same development cycle when it extends private label to a different family later |
Cedar & Co., a local brand with 12 shops, decides to develop its own private-label T-shirt against its own sales forecast, rather than reselling another brand's product. Cedar & Co. writes a product brief: 180 GSM single jersey, Ne 30/1 combed cotton, the same construction already fixed for Order A, targeting an illustrative first batch of 5,000 pieces made by Delta Garments on Cedar & Co.'s own 60-day open account terms.
Delta Garments makes a proto sample first, in a substitute fabric, to prove the basic construction. Once Cedar & Co. confirms the construction is right, Delta Garments makes a fit sample in the actual 180 GSM fabric, at the sample size, and sends it back to Cedar & Co. for review. Cedar & Co.'s own buyer checks the fit sample against the size specification and issues a sample approval outcome before any bulk fabric is committed.
The worked numberThe sample round's own fabric cost, about USD 2.30, is a small fraction of the USD 5,750 bulk fabric commitment it protects. This is why the development cycle is followed in order: a small, cheap check at the sample stage is what prevents a fault from being discovered only after the much larger bulk fabric purchase has already been made.
A common mistake is treating a proto sample's approval as if it already proved fit, simply because the construction looked right. A proto sample is often made in a substitute fabric, so it cannot show how the real 180 GSM fabric will actually drape, stretch or feel once worn. If Cedar & Co. approved the proto sample and moved straight to bulk fabric, skipping the fit sample stage, a fit or fabric-behaviour fault would only be found once thousands of pieces were already cut, a far more expensive point to discover it than the fit-sample stage this lesson describes.
Developing a private-label style means writing down what the retailer wants, then checking a sequence of samples before committing to a large order. First comes the brief: a written description of the product. Then comes a proto sample, a rough first attempt that proves the basic construction, sometimes in the wrong fabric. Then comes a fit sample, made in the real fabric, checked to see if it actually fits. Only once the retailer approves the fit sample does bulk production start. Skipping a step to save time usually costs more later, once a problem shows up in a much bigger, much more expensive batch.
Cedar & Co.'s buyer reviews the fit sample for its own-label T-shirt against the size specification. The facts in front of the buyer:
The comment sheet, as returned by Cedar & Co.'s buyer:
Should Delta Garments proceed straight to cutting the 5,000-piece bulk fabric, or resubmit a corrected sample first? Decide before you open the decision.
Resubmit a corrected sample first; do not proceed straight to bulk fabric.
Two facts decide this. First, the sample approval outcome is "approved with comments," not a plain "approved"; this lesson's own rule states that an approved-with-comments outcome requires a specific, stated change before moving forward, not a general go-ahead. Second, the stated change, a firmer rib knit, is a fabric-level fix, not a cosmetic note; proceeding to cut 5,000 pieces before it is corrected would carry the loose-neck-rib fault into the entire bulk batch, at a cost far higher than the USD 2.30 sample-round fabric this lesson's worked number already showed.
Delta Garments should make one corrected sample with the firmer rib knit, Cedar & Co. should check it against the same comment, and only a plain "approved" outcome on that resubmitted sample should clear the style to bulk fabric.
If Delta Garments cut the full USD 5,750 of bulk fabric before correcting the neck rib, every one of the 5,000 pieces would carry the same fault, since a knit fault at fabric level cannot be fixed once garments are cut and sewn. The cost of a corrected resample, a small addition to the already small USD 2.30 sample-round fabric cost, is what protects the full USD 5,750 bulk commitment from being spent on a fault the sample stage already found.
Use the T19-C06 Private-label development tracker. For Cedar & Co.'s own-label T-shirt, record the brief date, the proto sample and fit sample dates, the sample approval outcome for each round, and the comment sheet point for any "approved with comments" result, before authorising bulk fabric.
[Download the Private-label development tracker](../../templates/T19-C06-private-label-development-tracker.xlsx)
1. What does a proto sample prove that a fit sample does not, and what does a fit sample prove that a proto sample does not?
2. Cedar & Co.'s fit sample comes back with the outcome 'approved with comments,' naming a specific fabric-level fix. What should happen next?
3. A different private-label style, made for export rather than Cedar & Co.'s domestic open-account terms, has already passed an approved fit sample. What does this lesson's own 'what you meet in real life' table say the export style still needs that Cedar & Co.'s domestic style does not?
| EN | AR | FR | TR | Meaning |
|---|---|---|---|---|
| Product brief | إحاطة المنتج | Cahier des charges du produit | Ürün brifi | A customer's description of a product's requirements, such as season, care, price point and look, often written without naming a fibre. |
| Proto sample | عينة البروتو | Prototype (échantillon proto) | Proto numune | The first, rough sample made from the tech pack, often in the wrong fabric, to prove the design and construction idea works before investing further. |
| Fit sample | عينة الفيت | Échantillon de fit | Fit numunesi | A sample made in the correct fabric at the sample size, checked against the size specification to prove the garment fits. |
| Sample approval outcome | نتيجة اعتماد العينة | Résultat d'approbation de l'échantillon | Numune onay sonucu | The named result a buyer issues once a sample review is complete: approved, approved with comments, or rejected. |
| Private-label development cycle | دورة تطوير العلامة الخاصة | Cycle de développement de la marque de distributeur | Özel marka geliştirme döngüsü | The fixed sequence of steps, brief, proto sample, fit sample and approval, a private-label style passes through before bulk production starts. |
You now know how to take a private-label style from a written brief to an approved first sample. The next lesson moves past the first sample into repeat production, and shows how to protect that style's own quality and consistency once it is being made again and again. Back to the course map