Yarn Store Discipline: Counts, Cones, and Lots
Yarn is the most expensive material most knit factories hold and the easiest to lose track of, because it hides behind three unit systems, dozens of counts and lots, and a store culture of "it is all cotton anyway". A yarn store run loosely leaks money in every direction at once: over-purchase, dead stock, knitting faults, and claims that cannot be traced to a spinner. The discipline that stops it has three parts.
One count, stated in one system
Yarn fineness arrives in whichever system the spinner uses: English count (Ne), metric (Nm), denier, tex. A store that records "30s" without the system is storing ambiguity, and a knitting program fed the wrong assumption produces the wrong GSM at full machine speed. Record the count system explicitly on every item and convert deliberately with the yarn count converter rather than in heads. The same goes for form: the store holds kilograms, cones, and sometimes cartons of cones, and any total that adds those without converting is fiction. Progress and stock are tracked per line in its own unit, never summed across units.
Lots are the quality boundary
Two deliveries of the same count from the same spinner are not the same yarn. Lot-to-lot variation in shade take-up, strength, and evenness is exactly the variation that surfaces as barre stripes in dyed fabric, which is why the knitting floor's rule (one program, one yarn lot, or a recorded blend decision) begins in the store: receipts keep spinner lot identity, issues name the lot, and stock reports show lots, not just items. This is the lot discipline applied where it earns the most, because a yarn defect discovered in dyed fabric is only claimable if the store can say which spinner lot knitted it.
Reconciliation closes the loop
The third discipline is arithmetic: yarn issued to knitting versus greige returned, per program, allowing the standard knit loss. Run monthly without it and the store drifts; run it per program and the drift names itself, a program consuming three points over standard is a machine, an operator, or a count problem, visible while it is still one program. The store that can produce this number is also the store whose numbers upstream capacity planning can actually trust.