June 2026 · 4 min read
Supplier drift, and how we catch it
Base specifications drift over time as suppliers change. The October garment is not always the March garment. Here is the surveillance practice that catches drift before customers do.
Supplier drift is one of those operational realities that nobody mentions in marketing copy. The cotton tee you sourced in March, in the same SKU from the same supplier, can feel measurably different by October. The dye lot shifts. The yarn density tolerance slips at the upper bound. The shoulder seam tension on the automated stitcher gradually wanders. None of these changes are bad-faith. All of them affect what your customer receives.
Why drift matters. A brand running a long catalogue depends on consistency. The customer who buys the same tee in March and October expects the same feel. When drift accumulates, the second tee feels off — and the brand wears the complaint, not the supplier. Our job as the fulfillment partner is to catch drift before it propagates.
The surveillance protocol. Every base in our catalogue is re-tested quarterly on a sampled basis. The sample is taken from current production stock, not the original test batch. Three measurements: fabric weight (gsm), dimensional accuracy (cm against template), and decoration receptivity (a controlled test print under standard conditions). All three are logged against the historical record.
Trigger thresholds. A drift above 5 percent on any single measurement triggers a conversation with the supplier. A drift above 10 percent triggers a base review (do we keep it, swap to an alternate, or de-list). A repeating drift trend across three consecutive quarters triggers a sourcing review even if any single quarter is within tolerance.
Communication to partners. When a base drifts within tolerance but in a direction we can detect, partners receive a quarterly note: "Base XYZ measured -3 percent on fabric weight this quarter, within tolerance but on a declining trend; we are watching". When a base drifts out of tolerance, partners receive a flag within five business days, with the proposed remediation (alternate base, supplier swap, de-list timeline).
The honest part. Some drift is invisible to instruments but detectable in customer feedback. Customer complaints flagged with phrases like "this feels different to last time" are reviewed monthly against our base test records. When they correlate, we adjust our test thresholds. When they do not, we investigate the order pipeline for handling issues.
Why we publish this. Partners who understand drift exists make different sourcing decisions. They buffer more conservatively. They sample more frequently. They build customer-service language that addresses inconsistency rather than denies it. Operational transparency, in our experience, makes the partnership more durable on both sides.