Colour Variants and Colorways in Fabric Sampling: A Practical Guide
A single fabric design rarely comes in just one colour. A shirting that sells well in white will be made in sky blue, mint, and pale yellow too. Managing those colour options — keeping them linked to the parent design, giving each its own identifier, and printing accurate stickers for every variant — is where many textile operations quietly lose control. This guide explains the concepts clearly and shows how a structured approach prevents the chaos that comes from treating every colourway as a separate design.
What is a colour variant?
A colour variant — also called a colorway — is a version of a fabric design produced in a specific colour. The construction, blend, and weave are identical to the parent design. Only the colour differs.
Consider a plain 65/35 polyester-cotton shirting registered as design number 1042. It has an EPI of 60, a PPI of 58, a GSM of 110, and a standard 58-inch width. If the same fabric is produced in white, sky blue, mint, and pale yellow, each of those is a colour variant of design 1042. The construction does not change. The colour does.
The concept exists because fabric production and sampling decisions follow the construction first and the colour second. A buyer evaluating design 1042 is evaluating the hand feel, the weave structure, the blend composition, and the weight. Colour is a downstream decision — important, but separate. Keeping that distinction in the records reflects how the business actually works.
Why colour variants are not separate designs
Treating each colourway as a separate design record causes library bloat, makes searching harder, and makes the relationships between related fabrics invisible. If design 1042 in four colours becomes four separate records — 1042, 1043, 1044, and 1045 — the library has consumed four design numbers for one construction. A staff member searching for "blue shirting poly-cotton 65/35" will find only 1043 and miss the context that three other colours of the same construction are also available.
For a buyer visiting the sample room, the failure is more visible. They pick up a white fabric, ask whether it comes in blue, and the salesperson either knows from memory or does not. If the records do not group variants under one design, the answer requires manually searching multiple records rather than opening one design and scrolling through its colorways.
Design 1042 in four colours should be one design with four variants — not four separate records. This is the structural distinction that purpose-built software enforces correctly, and that manual Excel-based systems almost always get wrong over time as the library grows.
What is an MPN?
MPN stands for Material Product Number. Each colour variant gets a unique MPN. Where the design number identifies the design — the construction, the blend, the weave — the MPN identifies the specific colour variant within that design.
In SampleLedger, MPNs are assigned automatically when a colour variant is created. For design 1042 with four colorways, the system generates MPNs such as 1042-001, 1042-002, 1042-003, and 1042-004. The structure keeps the design number visible in the MPN, so anyone looking at the code immediately knows which design it belongs to. MPNs must be unique within a sample — the system enforces this and prevents duplicates at the point of entry.
Manual overrides are supported for operations that have existing MPN conventions they need to honour. In those cases, the MPN can be entered directly rather than generated. What cannot happen is two variants sharing the same MPN — the uniqueness constraint is always enforced regardless of whether the value was auto-generated or manually entered.
Variety: the count that stays in sync
The variety field on a sample record is the count of colour variants. When a fourth colorway is added to design 1042, the variety automatically becomes 4. It cannot be set manually to an incorrect value — it is derived directly from the number of variants attached to the design, not entered independently.
This field appears on the sticker. When a buyer picks up a sample, they can see at a glance how many colours are available for that design. "Variety: 4" is a prompt — it tells the buyer to ask about the other three colours they may not have seen. It is a small detail that turns a sticker into a sales tool.
How to manage colorways without chaos
The discipline that prevents colorway chaos comes down to a few consistent practices.
Always create colour variants as children of the parent design — never as standalone records. If you are tempted to create a new design number for a colour of an existing construction, that is a signal to add a variant instead. The moment you start treating colours as independent designs, the library begins to fragment.
Name colours consistently using master table colour options rather than free text. If one person enters "sky blue" and another enters "light blue" for the same colour, you now have two colour options that look like different things in search results. Organisation-level master tables for colour ensure that the same name is used every time.
Generate stickers per variant at the time of creation, not retrospectively. Stickers produced from the live record at creation time are guaranteed accurate. Stickers added later from memory are not.
When a buyer asks for "that blue version of design 1042," the answer should take seconds, not minutes. Open design 1042, view variants, identify the blue — done. The entire interaction depends on the data having been entered correctly in the first place.
Stickers and QR pages per variant
Each colour variant gets its own sticker and its own public QR spec page. The sticker carries the variant's MPN, its colour, and the parent design's construction specs. The QR code on that sticker links directly to a spec page for that specific variant.
When a buyer scans a colourway sticker, the page they see shows that variant's colour alongside the parent design's construction details — blend, weave, GSM, GLM, width, and variety count. A buyer holding a blue sample scans its sticker and sees the blue variant's page, not a generic design page that requires them to find the right colour themselves. The specificity matters — it removes a step and removes ambiguity.
Manage colour variants the right way from the start.
SampleLedger structures colour variants correctly — one design, multiple colorways, unique MPNs, derived variety count, stickers per variant. Purpose-built for how textile sample management actually works.