It is subjective
Two inspectors reach two conclusions about the same garment, and neither can show why. The technical documentation exists, but almost nothing is checked against it directly.
Quality control for garment manufacturing
SeamProof is an automated quality control system for small and ultra-small garment manufacturers, and for the buyers and inspectors who accept their work. Computer vision examines the finished item against the technical documentation it was ordered against, and returns a verdict.
Not a checklist app that records someone’s opinion. A system that does the checking itself, applies the same standard every time, and leaves a document behind.
The problem
Large manufacturers run laboratories, instruments and trained inspectors. Below that line, which is where most of the world's garments are actually made, acceptance comes down to whoever is holding the item and how their day is going.
Two inspectors reach two conclusions about the same garment, and neither can show why. The technical documentation exists, but almost nothing is checked against it directly.
A person can look at a handful of things per item before the line moves on. Whatever is not looked at is, in effect, approved.
Problems surface after shipping, and by then there is nothing to point at. A disagreement over a container of goods becomes one company’s word against another’s.
What we do
Every order already carries a specification: what the item should look like, how it should be assembled, where each component belongs. SeamProof uses computer vision to hold the finished garment against that specification and report where the two disagree.
Inspection stops depending on attention, experience and fatigue. The same item examined twice produces the same result, which is the part a human inspector can never promise.
The specification the order was placed against becomes the thing the item is measured against, rather than a document nobody opens after production starts.
Each inspection produces a record: what was checked, against which reference, and what the result was. It outlives the conversation that produced it.
Where we stand
Acceptance is a negotiation between a manufacturer and a buyer, and each has a reason to see the goods their way. A system that applies the same rules to both, and shows its working, is worth more to both than another opinion would be.
The verdict comes from the specification and the tolerances written into it, not from who is asking. Neither side can lean on it, which is precisely what makes it usable by both.
Every verdict is traceable to what was inspected and the rule that was applied. A dispute stops being a contest of confidence and becomes a question of fact.
What changes
A result that can be checked, in place of an opinion that cannot.
Inspection that keeps pace with production instead of holding it up.
Problems found before goods leave, which is the last point at which fixing them is still cheap.
A protocol per item, so a shipment can be discussed with a document on the table.
Who it is for
Quality control software has been written for factories that can afford a quality department. We are building for everyone underneath that, where the same mistakes cost proportionally more.
Check your own output before it ships, and keep a record of what you sent. One rejected shipment costs more than every inspection that would have prevented it.
Accept goods on site, in someone else’s factory, without carrying a laboratory or a team. Leave with findings rather than notes.
Where we are
We are building the system and testing it against real garments with partner manufacturers. The first checks are going in now, and the set of control points will keep growing: the goal is an acceptance protocol that covers the specification, not a single test. This page describes what the company is for. Results will be published here as they arrive.