Syntha Lab RU

Material unification: SKUs per fabric

Calculates how many SKUs share one fabric, how many fabrics are used in all and which of them need less than the supplier’s minimum order (excess meters and their cost). Shows how many fabrics would be enough at your target of SKUs per fabric.

Collection calendar and materials For whom: Product and production directors planning the collection’s materials.

Calculate on your data →

At a glance

What question does it answer?
How many SKUs share one fabric and which fabrics need less than the minimum order.
What data is needed?
Per fabric: SKUs, the minimum order and the need in meters.
How to read the result?
Default example: 30 SKUs over 5 fabrics, 6 per fabric on average; one fabric (linen) has a single SKU (20%). Two fabrics (viscose and linen) are below the minimum order: 1,250 m of excess, or 562,500. At a goal of 8 SKUs per fabric 4 fabrics would be enough. Example on the default values: SKUs in total — 30; Fabrics — 5; SKUs per fabric — 6; Fabrics with a single SKU — 1 · 20%.

Why and how to reason

Every fabric costs money before the first garment is sewn: the supplier sells it not by the meter but in a minimum order, and you must buy the whole order. If one SKU with small demand sits on a fabric, you buy more than you sew and the excess meters lie dead. So we count not how many fabrics there are but how many SKUs share one fabric: Σ SKUs ÷ number of fabrics. The higher it is, the more demand pools into one purchase and the easier the minimum order is to fill. The second figure counts the hole directly: for each fabric take max(0; minimum order − need) and multiply by the price per meter. A mini example on the default values: 30 SKUs on 5 fabrics give 6 SKUs per fabric; viscose (900 m needed against a 1,500 m minimum) and linen (350 m against 1,000) fall short by 600 and 650 meters, 1,250 m in all, and at 450 per meter that is 562,500. At a goal of 8 SKUs per fabric, ceil(30 ÷ 8) = 4 fabrics would be enough, one fewer than now.

When to use it

It is useful when planning a collection and raw-material purchases, while SKUs can still be redistributed across fabrics: after cutting it is too late. It suits a brand with its own sewing or customer-supplied fabric. It does not suit buying finished goods from a factory, where fabric is not your concern. Assumptions: the need in meters is already derived from the sales plan, one price per meter fits all fabrics, and the minimum order is fixed and not negotiable. The goal of SKUs per fabric is your own guide, not a standard.

How to read the result

Look first at fabrics with a need below the minimum order: each one is money tied up in meters you will probably not use. Then compare SKUs per fabric with the goal: if lower, look for fabrics that can be replaced by close relatives. A fabric with a single SKU (linen in the example) is the most common candidate for merging or dropping. The decision is one of three: merge fabrics, raise the need (add a SKU from the same fabric) or negotiate a smaller order and pay a surcharge. Check that the surcharge is smaller than the cost of the excess meters. Then compare with the collection map and the material price in the unit cost calculation.

Common mistakes

The main mistake is entering the need as a wish rather than the real sales plan, so excess meters stay invisible. The second is treating excess meters as a 100% loss when part of the leftover goes to the next season or to samples. The third is chasing a high number of SKUs per fabric and ending up with a uniform collection the customer cannot tell apart.

What data is needed?

  • Per fabric: SKUs, the minimum order and the need in meters.
  • The fabric price per meter and your goal of SKUs per fabric.

Inputs

FieldUnitValue in the exampleMeaning
Fabric price per meter excl. VAT₽450The average across the table’s fabrics. Empty: the cost of excess meters is not calculated.
Goal: SKUs per fabricSKUs8An example. Set from your collection and how well styles can share fabrics. There is no single Russian benchmark: enter your own data from past seasons.

How it is calculated

StepFormula
SKUs per fabricΣ SKUs ÷ number of fabrics
Excess metresΣ max(0; minimum order − need)
Fabrics at the goalrounded up (SKUs ÷ goal)

Worked numbers

Default values from the app; in the interactive version you enter your own.

SKUs in total
30
Fabrics
5
SKUs per fabric
6
Fabrics with a single SKU
1 · 20 %
Fabrics with a need below the minimum order
2
Excess metres from minimum orders
1,250 m
Cost of the excess metres
562,500 ₽Money in fabric that may end up as leftover.
Fabrics that would be enough at your goal
4 · now 5

Fabrics and minimum orders

FabricSKUsNeed, mMinimum, mExcess metres
Cotton poplin82,2001,5000
Viscose39001,500600
Linen13501,000650
Knit, French terry124,1002,0000
Lining61,7001,5000

Below the minimum order: Viscose, Linen. Merge with another fabric, add SKUs or ask the supplier for a smaller order.

The goal of SKUs per fabric is your guide: there is no single Russian benchmark. Large international producers can have dozens of SKUs per fabric, but that is a reference to foreign practice.

Nuances and limits

  • Chasing the average SKUs per fabric at the expense of the idea of the collection: unification must keep the items feeling different.
  • Ignoring color: the minimum order is often set per color, see “Color and fabric minimum order”.
  • Taking the example goal for a standard: there is no single Russian benchmark.

Terms used

Calculate on your data →