Building a SKU matrix that scales
Code each style once and generate variants by colour and size, for example AW24-TS-001-BLK-L. Keep style, colour, size and season as separate attributes so you can report at any level.
- Use a two-dimensional matrix when creating variants to avoid omissions.
- Assign barcodes per variant, not per style.
- Record season or collection as an attribute for carry-over reporting.
- Archive discontinued variants instead of deleting them, so history remains.
Retail, wholesale and promotion prices
Set price levels per customer type and keep promotions time-bound. A customer-specific price should override the general level, and every manual change should record the user.
| Level | Use | Override rule |
|---|---|---|
| Retail | Walk-in customers | Promotion price if active |
| Wholesale | Trade accounts | Customer price beats wholesale |
| VIP | Regular retail customers | Customer price beats VIP |
| Cost | Internal only | Hidden by permission |
Exchanges without destroying the numbers
Handle a size exchange as a return plus a new sale, linked by reference, rather than editing the original invoice. That preserves revenue, stock and customer history.
- Record the reason: size, colour, quality or change of mind.
- Return defective items to a quarantine warehouse before deciding the outcome.
- Print a credit note or exchange receipt for the customer.
- Report return rates by style to improve buying.
Seasonal stock and replenishment
Review sell-through by style, colour and size weekly. The useful question is not total stock but “which size is missing and which colour is stuck?”
- Set safety stock per fast-moving size, not per style total.
- Mark end-of-season stock for promotion before it becomes dead stock.
- Use stock ageing to identify carry-over that should not be reordered.
- Count high-value styles monthly during peak season.