Fixing Sample Errors: When to Return or Rebuild

Procurement managers face a hard choice when a sample fails. This guide explains how to assess sample feedback, identify root causes, and decide between a simple revision or a full rebuild based on defect severity and production risk.
- Categorize sample errors by severity before deciding on a fix path.
- Use a structured feedback form to track defects and revision history.
- A full rebuild is warranted when fit, construction, or fabric issues cannot be corrected in a single pass.
- Document all changes in the tech pack to prevent recurrence in bulk production.
- Set clear approval gates to avoid sending flawed samples to the floor.
Define the Error Before You React
A sample arrives on the desk and the first reaction is often frustration. The color is wrong. The hem is uneven. The zipper catches. Before drafting a return note or calling the factory, step back and classify the defect.
Not every failure requires the same response. A crooked label can be fixed in an afternoon. A collar that collapses when worn cannot. The decision between a sample revision and a full rebuild hinges on the nature of the error, the time already spent, and the risk to the final bulk order.
Start by separating errors into three groups: cosmetic, functional, and structural. Cosmetic errors affect appearance but not wear. Functional errors impact how the garment is used. Structural errors threaten the integrity of the piece. This distinction drives the next steps.
Read the Sample Feedback Against the Tech Pack
Do not rely on memory or casual notes. Open the tech pack and compare every item on the sample against the written specifications. Check the fabric composition, the trim list, the stitch types, and the measurement tolerances.
Write down every discrepancy. If the sample shows a 2 cm difference in chest width and the tech pack allows a 1 cm tolerance, that is a measurable failure. If the fabric hand feels too stiff and the spec calls for a specific drape, that is a subjective but critical failure.
Record each item with a severity code. Use a simple scale. A one indicates a minor cosmetic note. A two indicates a functional issue that must be corrected before bulk. A three indicates a structural flaw that stops the line. This coding system turns a vague complaint into a workable list.
It is common to find that the sample deviates in areas not covered by the tech pack. This is a red flag. If the factory made a call on a detail you did not specify, the gap must be closed immediately. Do not let ambiguity slide into bulk production.
Decide Between Revision and Rebuild
The core decision is whether the current sample can be saved or must be discarded. A sample revision is appropriate when the garment structure is sound and the errors are isolated. A rebuild is required when the base construction, fit block, or fabric sourcing is flawed.
Consider the time factor. If the sample is already three weeks old and the factory has spent significant labor on it, a full rebuild costs more in time and money. However, if the fit is wrong, no amount of trimming or re-sewing will fix the block. Sending a misfit sample to the floor will create hundreds of defective units.
Look at the defect pattern. If the errors are scattered and unrelated, a revision may work. If the errors cluster around one area, such as the sleeve attachment or the waistband, the underlying pattern or construction method is likely at fault. In that case, the factory needs to scrap the sample and re-cut from the corrected pattern.
Also consider the factory’s capacity. If the factory is already running bulk production on other orders, a rebuild will delay your timeline. A revision might be faster. But speed should not override quality. A rushed fix on a flawed base will only create a larger problem later.
Use a Structured Feedback Table to Drive the Fix
Vague feedback creates vague results. If you tell a factory that the sample is not right, they will guess what you mean. If you tell them that the shoulder seam is 4 mm too high and the armhole is too tight, they can make a specific correction.
Use a table to organize your findings. This format forces you to be specific and makes it easy for the factory to see exactly what needs to change.
| Symptom | Likely cause | What to do |
|---|---|---|
| Collar sits too low on the neck | Pattern block is sized incorrectly for the fabric | Request a new collar block and re-sew the neck area |
| Hem is uneven on the side seams | Fabric grain was not aligned properly during cutting | Re-cut the garment using a balanced grain line |
| Zipper does not align at the front opening | Zipper tape is too narrow or the opening is mis-cut | Replace with a wider tape or adjust the opening width |
| Fabric puckering around buttons | Buttonhole tension is too high | Adjust machine tension and re-stitch the buttonholes |
| Color appears darker under factory lighting | Fabric dye lot variation | Request a new dye lot or adjust the shade match |
This table should accompany every return shipment. Include photos of each defect. Mark the exact location on a sketch of the garment. If possible, attach a sample of the correct trim or fabric swatch.
Prevent the Next Round of Errors
Fixing the current sample is only half the job. The other half is ensuring the same error does not appear in the next sample or in bulk. This requires a structured prevention process.
First, update the tech pack. If the factory made a wrong call on a detail, add that detail to the tech pack with a clear instruction. If the tolerance was too tight or too loose, revise the tolerance. The tech pack must reflect the reality of what is needed.
Second, implement a pre-sample checklist. Before the factory cuts the first piece, they should verify the fabric lot, the trim inventory, and the pattern files. A simple sign-off sheet at this stage catches many errors early.
Third, hold a virtual or in-person review of the first sample. Do not wait for the sample to arrive by mail. Watch the factory assemble the first unit. Ask questions about their process. If they explain how they are attaching the sleeve, you can correct them before the work is done.
Finally, track the history of revisions. If the same issue appears in multiple samples, the root cause is not the sample. It is the process. Address the process change with the factory in writing. Document the corrective action and the date. This creates an audit trail and sets expectations for future orders.
Set Clear Approval Gates
A sample is not finished until it is approved. Do not let a sample sit in a “pending” state for weeks. Set a deadline for approval or rejection. If the factory does not respond to your feedback within three to five business days, escalate the issue.
Create an approval gate for each stage. The first sample is a fit check. The second sample is a final check. Only when the final sample is approved should you release the bulk order. This prevents the factory from starting production on a flawed design.
Communicate the approval clearly. Send a written confirmation. State that the sample is approved for bulk and that any changes to the design or fabric are prohibited without your written consent. This protects your position if the factory makes unauthorized changes later.
If the sample is rejected, state the reason clearly. Do not say the sample is not good. Say exactly what is wrong and what must be fixed. This removes ambiguity and speeds up the revision cycle.
When to Escalate or Change Suppliers
Sometimes the errors are not fixable within a reasonable timeframe. If the factory has failed to correct a structural issue after two revisions, the problem is not the sample. It is the supplier’s capability.
Evaluate the factory’s response. Are they responsive? Do they understand the technical requirements? If the communication is poor and the fixes are slow, the risk of bulk failure is high.
Consider moving to a different supplier. This is a major decision. It requires re-qualifying a new factory, re-sending samples, and rebuilding the relationship. But if the current factory cannot produce a garment to spec, staying will cost you more in the long run.
If you choose to stay, negotiate a corrective action plan. Define the timeline for the next sample. Define the penalty for missing the deadline. Make the terms clear in writing.
The goal is not to punish the factory. The goal is to protect your product and your customers. A well-managed sample process prevents defects from reaching the market. It builds trust and ensures that the bulk order matches the approved sample.
Frequently asked questions
How many revisions should I expect before a sample is approved?
Most garments require two to three rounds of revision. The first round addresses major fit and construction issues. The second round fine-tunes details and finishes. A third round is usually only needed if the initial tech pack was unclear.
What is the difference between a sample revision and a rebuild?
A sample revision modifies the existing garment to correct isolated errors. A rebuild discards the current sample and creates a new one from scratch, usually because the base pattern, fabric, or construction method is flawed.
Should I send photos with my sample feedback?
Yes. Photos provide clear visual evidence of the defect. They reduce the chance of misinterpretation. Pair each photo with a written description and a reference to the specific tech pack section.
How do I know if the factory is capable of fixing the issue?
Ask the factory to explain their proposed solution. If they cannot identify the root cause or suggest a realistic fix, they likely do not have the capability. Request a small test piece before committing to a full rebuild.
What should I do if the same error appears in two consecutive samples?
Stop the sample process and hold a meeting with the factory. Review the tech pack, the cutting process, and the assembly steps together. Identify the root cause and agree on a corrective action plan in writing before continuing.


