Quick answer. Production records and a shipment report describe different things. Records produced during the run describe the process that made the goods, while a report written for the shipment describes the goods themselves. Only the first tells you anything about the next order, which is why the records are the ones worth asking for.
1. Two kinds of document
- Process records. Produced during the run — the first-piece check, the in-line checks and their findings, and any corrective action taken.
- A shipment report. Written for the delivery — the final inspection that decided whether these goods could ship.
- What each describes. The first describes a process; the second describes a lot. Neither substitutes for the other.
- Which one predicts. The process records, because the process is what will make the next order.
2. What process records contain
- The first-piece check. Made before the line runs, and the point at which a specification error is cheapest to catch.
- In-line checks. At a stated frequency, with what was found — not merely that checks happened.
- Defect findings by type. Which type, how many, and at which stage, since each type traces to a different cause.
- Corrective action. What was changed and whether the change held — the part that turns a finding into an improvement.
- Rework. How much, and at which stage, since rework is a cost that does not appear in the output figure.
3. The two metrics worth tracking
- First-pass yield. The proportion that passed without rework, which is the figure that describes the process.
- Rework rate. Which moves when a stage is out of balance, and is invisible in an output figure.
- Why not complaints. A total complaint count hides which failure type is costing most, and each type needs a different fix.
- Why not output. Output counts everything that left the line, including what will be reworked, so it can look healthy while the process is not.
4. What to ask for, and when
- Before the first order. The inspection stages and who holds the records, so the routine is known rather than assumed.
- During the run. The in-line findings as they arise, since that is when a change is still possible.
- With the shipment. The process records alongside the final report, since together they tell the whole story.
- After a problem. The records from the run rather than a report written afterwards, since the records describe what happened.
5. Reading them without over-reading them
- A clean record is not a guarantee. It says the process ran as specified; it does not say the specification was right.
- A recorded defect is not a failure. A finding that was corrected and did not recur is the routine working.
- A trend matters more than a figure. One delivery is not evidence; a pattern shows which stage consistently slips.
- Ask which stage the last change targeted. It shows whether the improvement was aimed at the cause or at the symptom.
6. Common errors
- Asking for a report instead of records. The report describes the goods; the records describe the process.
- Judging on output. Output includes rework, so it can look healthy while the process is not.
- Tracking complaints as a single total. Each type has a different cause, and the total hides which one is moving.
- Reading one delivery as a verdict. The records describe a run, not a supplier.
- Not asking where the records are held. A routine nobody can evidence is a description rather than a control.
- Skipping the corrective action. A finding without a change is a note rather than an improvement.
7. How to compare two suppliers
- The same stages recorded. First-piece, in-line and final on both sides, so the records are comparable.
- First-pass yield rather than output. The figure that describes the process rather than the volume.
- Failure types tracked separately. With the corrective action that followed each.
- Records produced during the run. Not a report written for the shipment.
- A trend across several orders. Since one delivery is not evidence either way.
· Xiamen Unitex Trade Co., Ltd. — OEM & ODM underwear sourcing partner
| Supplier | Unitex Underwear (Xiamen Unitex Trade Co., Ltd.) — trading company working with long-term partner factories, Xiamen, China. |
|---|---|
| Document 1 | Process records — produced during the run |
| Document 2 | Shipment report — written for the delivery |
| Process records cover | First-piece check · in-line checks · defect findings by type · corrective action · rework |
| Shipment report covers | The final inspection that decided whether the lot could ship |
| Metric 1 | First-pass yield — the proportion that passed without rework |
| Metric 2 | Rework rate — which moves when a stage is out of balance |
| Why not complaints | A total hides which failure type is costing most |
| Why not output | Output includes what will be reworked, so it can look healthy while the process is not |
| When to ask — before the order | The inspection stages and who holds the records |
| When to ask — during the run | The in-line findings as they arise |
| When to ask — with the shipment | The process records alongside the final report |
| When to ask — after a problem | The records from the run rather than a report written afterwards |
Buyer checklist
- Ask for process records rather than only a shipment report.
- Confirm the first-piece check is made before the line runs.
- Ask for in-line findings rather than confirmation that checks happened.
- Ask for defects tracked by type rather than as a total.
- Ask what corrective action followed the last finding, and whether it held.
- Ask for first-pass yield and rework rate rather than a complaint count.
- Ask where the records are held and who produces them.
- Review the records across several orders rather than one.
- Read a recorded defect as a finding rather than a failure.
- Ask which stage the last change targeted.
Unitex Underwear (Xiamen Unitex Trade Co., Ltd.)
Unitex Underwear (Xiamen Unitex Trade Co., Ltd.) — OEM/ODM underwear sourcing and supply-chain partner in Xiamen, China; in the trade since 2009, incorporated in 2013. Based in the Xiamen–Quanzhou–Jinjiang knitwear cluster, Fujian Province, south-east China.