What Is a Pre-Production Sample Review and When It Belongs in PLM

It is week ten of a twelve-week production cycle. The factory in Tirupur sends three PP samples by DHL. The design lead is in Paris for market. The production manager opens the box on a Tuesday, notices the neck binding is the wrong width and the woven label is sewn into the side seam instead of the center back, and emails the factory. The factory replies Thursday asking whether to hold bulk or proceed. By Friday afternoon the brand approves with conditions over WhatsApp. The conditions never make it into the tech pack. Six weeks later, 4,200 units arrive at the 3PL with the label in the wrong position, and the retailer rejects the shipment on a packaging compliance code.

That sequence is not a freak event. It is the default outcome when the pre-production sample review is treated as a courtesy step rather than a controlled gate.

What is a pre production sample review in apparel?

A pre production sample review, commonly called a PP sample review, is the formal approval checkpoint where a brand evaluates a sample made in the exact production fabric, trims, and construction the factory intends to use for bulk. The review compares the physical sample against the approved tech pack, the bill of materials, the graded spec, the fit history, and any retailer-specific labeling or packaging requirements. The output is a signed decision: approve for bulk, approve with corrections, or reject and resample. It is the last point at which a change costs hours instead of weeks.

This is distinct from a fit sample (earlier, often in substitute fabric, focused on pattern and grading), a salesman sample or SMS (built to sell wholesale, not to validate construction), and a top of production or TOP sample (pulled from the actual bulk run as a check, not as approval). A pre production sample review apparel teams can rely on sits between proto and bulk, and it carries legal and commercial weight: it is what the factory will reference if the brand later claims the bulk does not match approval.

Why does this checkpoint quietly fail at $10M to $20M?

Looking at where apparel brands keep buckling at $10M to $20M, the PP review is one of the most reliable indicators of whether production execution will hold. Below $10M, a small team usually has the founder or head of design physically inspecting samples, holding the tech pack in one hand and the garment in the other. Decisions are fast because the same person is the memory of the brand.

Above $20M, brands have usually invested in a production coordinator role, a structured PLM workflow, and a defined approval calendar. The handoff is documented because it has to be.

In between is the danger zone. Design has grown, production has grown, the factory base has expanded from two reliable partners to seven, and the PP review is still being run the way it was at $4M: by email, on a shared drive, with comments in PDF markups that never get reconciled back into the master tech pack. The reason the 6 Breakpoints framework exists in the form it does is that this pattern repeats across every brand we work with in that revenue band. Breakpoint 2, production and supply execution drift from the plan, almost always starts here, at the sample approval gate, not at the factory floor.

The failure mode is not that brands skip the review. It is that the review happens, the decision is made, and the decision never gets written back to the system of record. Twelve weeks later, when the goods arrive and something is wrong, nobody can produce a single document that shows what was actually approved versus what was made.

What artifacts does a PP review actually need?

A defensible pre-production sample review evaluates the physical sample against a fixed set of artifacts. If any one of them is out of date or living in a different system, the review is theatre.

• The current tech pack, with revision number and date, including all callouts (stitch type, SPI, seam allowance, interlining, fusing)
• The bill of materials with exact suppliers, references, and color codes for shell, lining, interlining, threads, zippers, buttons, labels, hangtags, polybag, and carton
• The graded spec with points of measure, tolerances, and the size set being reviewed
• The fit history from proto and fit samples, including resolved and unresolved comments
• Labeling requirements per market and per retailer (care label content, fiber content compliance, country of origin, RN number for US, CA number for Canada, GB labeling, retailer-specific brand labels)
• Packaging requirements per channel (polybag specs, hangtag placement, carton markings, retailer ASN packaging codes)
• Test reports if applicable (colorfastness, shrinkage, chemical compliance for children’s wear or specific markets)

If those seven artifacts are not all sitting in one place at the moment of review, the reviewer is making judgments from memory. Memory is exactly what fails at scale.

Why does this belong in PLM and not in email?

The artifacts above are PLM artifacts. The tech pack lives in PLM. The BOM lives in PLM. The graded spec lives in PLM. The fit comments live in PLM. The reason the PP review belongs inside the same system is not philosophical. It is that every other location for the decision creates a reconciliation problem.

When the PP review happens over email, the email becomes the source of truth for what was approved. The tech pack in PLM is now stale, but nobody updates it because the production cycle has moved on. Three seasons later, when a similar style comes through, the designer pulls the old tech pack as a reference. It is wrong, because the corrections that were approved verbally never went back in. The same mistake gets re-made on a new style. This is how production drift compounds.

When the PP review happens inside PLM, three things change. The reviewer is forced to compare against the current revision of the tech pack rather than a printed PDF from two months ago. The decision is captured as a status change on the style and the sample, not as a sentence in an email thread. And the corrections required for bulk are written back into the tech pack revision that the factory will reference, so the bulk PO and the tech pack stay in sync.

A PP review run over email and shared drives is not a review. It is a conversation that happened to be about a sample.

When should the review happen in the timeline?

For a standard twelve-week production lead time on cut-and-sew apparel, the PP sample should arrive at the brand no later than week four, with bulk cutting authorized in week five. That gives one week for review, comments, and either approval or a resample decision. For drop-driven brands running compressed eight-week cycles, the PP sample needs to be in hand by week three.

The non-negotiable rule: bulk fabric should not be cut before the PP review is signed off, even if the factory is pushing to hold the delivery date. The cost of one week of delay on the delivery date is almost always lower than the cost of 4,000 units in the wrong configuration. Brands that consistently allow factories to cut on verbal approval are the brands that consistently absorb the cost of unsellable inventory.

Magnolia Pearl, which runs frequent drops with same-day fulfillment expectations and ships internationally with duty implications, is a useful reference here. When the drop cadence is tight and the product is sold the week it lands, there is no margin to absorb a PP miss. A wrong trim or label on a drop product is not a markdown problem, it is a cancellation problem. The PP gate is what protects the drop calendar.

What does a clean PP review workflow look like?

The operational sequence, run inside PLM, looks like this:

1. Production coordinator triggers the PP review on the style when the sample is logged into receiving.
2. The system surfaces the current tech pack revision, BOM, graded spec, and fit history as the review packet.
3. Reviewer (design lead or technical designer) evaluates against the packet and logs comments at the point of measure or BOM line level, not as freeform notes.
4. Comments are categorized: approved, approved with correction, rejected. Corrections write back to the tech pack as a pending revision.
5. Production manager reviews the corrections for cost and lead time impact, accepts or negotiates with the factory.
6. Factory acknowledges the corrected tech pack revision in writing. This is the document the bulk PO is now bound to.
7. Bulk cut is authorized against the corrected revision, not the original.

That is seven steps. Most brands at $10M to $20M are running steps 1, 3, and 7. Steps 2, 4, 5, and 6 are the ones that fall to email, and they are the ones that determine whether the bulk matches the approval.

What is the cost of getting this wrong?

The cost is not abstract. On a $15M brand running wholesale and DTC with 3PL fulfillment, the back-of-envelope cost of operational drift is already 6 to 9 hours per week spent reconciling inventory across Shopify, the 3PL, and wholesale, plus a 2 to 3 percent oversell rate at peak, plus roughly one FTE doing data plumbing instead of real work. A PP review failure adds to that load in a specific way: when bulk arrives wrong, the inventory cannot be received cleanly. The 3PL flags it, the wholesale team cannot allocate against it because retailer compliance will reject it, and the DTC team cannot list it because the labeling is off. The goods sit in a receiving exception bay while the brand decides whether to relabel, return to vendor, or sell as off-price.

For a wholesale-heavy brand, the failure mode is sharper. If retailer chargebacks exceed 1 percent of wholesale revenue, the EDI integration is usually not the problem. The problem is upstream: bulk that does not match the approved spec, arriving at the retailer’s DC with the wrong label, the wrong polybag, the wrong carton marking. The chargeback is a downstream symptom of a PP review that did not capture or enforce retailer packaging requirements.

Lufema, which runs multi-entity wholesale across multiple brand catalogs with a B2B portal, surfaces this pattern at a different angle. When one PP review serves bulk that will be sold under three different brand identities into different retailer compliance regimes, the review packet has to enumerate the labeling and packaging requirements per brand and per retailer at the gate, not at the warehouse. A miss at the PP review becomes three downstream problems instead of one.

How do you know your PP review process is broken?

Five operational signals, any one of which is sufficient:

• Tech packs in PLM are routinely on revision 3 while the bulk in the warehouse was made to revision 5, and the only place revisions 4 and 5 exist is in an email thread.
• The same construction or labeling correction shows up across multiple seasons because nothing was written back to the master.
• Receiving exceptions at the 3PL are dominated by labeling, polybag, or hangtag issues rather than count discrepancies.
• Retailer chargebacks are concentrated in packaging and labeling compliance codes, not in late shipments or ASN errors.
• The production team cannot, within five minutes, produce the signed approval document for the bulk that arrived last week.

None of these are exotic. They are the operational fingerprints of a review process that runs outside the system of record.

What this means for an apparel operations team

The PP review is a small ceremony with disproportionate downstream consequences. It is the last cheap moment in a production cycle. Every hour of clarity invested at the PP gate avoids days of receiving exceptions, weeks of chargeback disputes, and seasons of repeated design mistakes. Treating it as a project management task rather than a data event is what causes Breakpoint 2 to fire.

The architectural fix is not more discipline from the design team or more pressure on the factory. It is that the review has to happen against the live PLM artifacts, the decision has to be captured as a status change tied to those artifacts, and the corrections have to write back to the tech pack revision that the bulk PO is bound to. Anything less is a verbal agreement dressed up as a process.

For operations leaders at $10M to $20M brands, the action is to audit the last ten PP reviews. Find the signed approval. Find the tech pack revision the bulk was actually made to. Confirm they match. If you cannot do that exercise quickly, you have already identified where the next quarter’s inventory pain is going to come from.