Size run

Size grids are the densest part of any vendor document and the easiest to misread. A wide run can carry eighteen or more columns, quantities are frequently sparse, and the header row may be several lines above the numbers it labels. Reading a quantity into the wrong column produces an order that looks correct in total and is wrong in every size.

That failure is quiet. The purchase order totals match the invoice, so nothing looks amiss until stock arrives and the sizes do not match what was counted.

Apparel typically runs alpha sizing from XS to XXL. Footwear runs numeric and often half sizes. Bottoms run numeric waist, sometimes with a separate length. Accessories may have no run at all. A catalog that forces one sizing scheme across all of them will misdescribe most of them.

Runs also differ within a category by who the product is cut for, and the run itself is often the only signal. A men's and a women's version of the same style will carry different size ladders, and the presence of certain sizes at the small end of a run is frequently the clearest indication of which one you are looking at when the document does not say.

The same size written as M, Med and Medium across different products fragments reporting and breaks matching against vendor documents. Pick one label per size per category and apply it consistently, the same discipline the attribute set needs.

Watch for labels that carry a unit on some products and not others. A width recorded as 52 on one style and 52mm on another describes the same thing and will not reconcile, so receiving creates a second variant beside the first. Whichever form you choose, the rule is that it is the only form, because a size label is an identifier even though it does not look like one.