What Is a Design Number in Textiles? How to Structure Your Sample Library

A design number is the unique identifier assigned to a specific fabric design in a manufacturer's or trader's sample library. It is the primary key of your sample database — the reference that everything else is filed under.

Every sticker attached to a physical sample carries the design number. Every spec sheet sent to a buyer starts with the design number. Every buyer conversation about a specific fabric references the design number first. When a buyer places an order, they quote the design number. When a dispatch is prepared, the packing list references design numbers. When a quality dispute arises, both parties refer to the design number to establish which fabric is under discussion.

Because the design number is referenced at every stage of the sampling and sales workflow, its integrity is critical. A design number that is not unique — or that is applied inconsistently — corrupts every downstream reference. The design number is not a convenient label; it is the foundation that the entire sample library is built on.

There is no universal standard for design number format. Different organisations use different conventions, and several approaches are common in the industry:

Sequential numbering (1001, 1002, 1003…) is the simplest approach. Numbers are assigned in order as samples are created. Easy to generate, easy to verify uniqueness, and the numbers are short. The drawback is that the number carries no information about the fabric — you cannot tell from "1045" whether the design is a shirting or a denim.

Year-series prefixes (SL-2026-001, SL-2026-002…) encode the year of creation and a sequential counter. Useful for separating sample seasons and for quickly identifying when a design was first created. Numbers grow longer with each prefix segment added.

Category prefixes (SH-001 for shirting, DN-001 for denim, SU-001 for suiting) group samples by fabric type. Makes it easy to browse a sample list by category. The risk: the category prefix must be applied consistently, and samples that span categories (a cotton-polyester blended shirting weight suiting, for instance) can be hard to categorise.

Free-form assignment — numbers chosen ad hoc by whoever creates the sample — is common in operations that started with Excel. It is also the most problematic, because there is no system to enforce consistency or uniqueness.

Duplicate design numbers are the most serious failure mode in a sample library. They happen in predictable ways: two sales reps create samples independently without checking what numbers are already in use; design numbers are imported from multiple sources (a production system, an Excel file, a sample book) without deduplication; or the numbering system is informal enough that collisions happen accidentally over time.

The consequences compound quickly. When a buyer refers to design 1045 in a conversation, both parties must be confident they are talking about the same fabric. If 1045 exists twice — once as a 60 × 60 cotton poplin and once as a 70 × 42 poly-cotton twill — there is no clean resolution. One of those designs must be renumbered. Every sticker, spec sheet, and buyer record referencing the old number is now incorrect and must be corrected manually.

The operational risk extends further. Warehouse staff pulling samples by design number pull whichever one they find first. Dispatch notes reference a number that corresponds to two completely different constructions. A buyer receives the wrong sample and makes a purchasing decision based on a fabric that will not match what they ordered.

The specific design number format matters far less than uniqueness enforcement. A system that reliably prevents two designs from having the same number — regardless of how the number is structured — is dramatically more robust than any naming convention applied without enforcement. Enforcement at the point of entry (not at the point of review) is the only reliable approach.

Auto-generated design numbers — where the system assigns the next sequential number — eliminate the duplicate problem entirely. No human decides the number; no human can create a collision. The numbers are short, consistent, and require no thought at the point of sample creation.

The tradeoff is that auto-generated numbers are semantically empty. "1045" tells you nothing about the fabric. If you need to quickly identify from the number whether a design is a shirting or a denim, sequential numbers do not help. Some organisations find this acceptable because they search by other fields (category, blend, GSM); others find it disorienting.

Manual entry allows you to encode information into the design number — category, season, series — but introduces the risk of human error and inconsistency. The pragmatic recommendation: auto-generate by default, which eliminates the duplicate problem for the vast majority of entries. Allow manual override for organisations that already have an established numbering convention they need to preserve, but enforce uniqueness regardless of which path is used.

A design number and an MPN (Material Product Number) operate at different levels of the sample hierarchy, and understanding the distinction prevents confusion in catalogue management.

The design number identifies the design — the fabric construction, weave, blend, GSM, and all construction-level parameters. It is the parent record. A shirting at 60 × 60, 40s cotton, plain weave, 120 GSM has one design number regardless of how many colourways exist.

The MPN identifies a specific colour variant of that design — a particular colourway with its own shade, dye lot reference, and physical sample. One design number can have multiple MPNs: one per colourway. A design that exists in white, sky blue, and charcoal has one design number and three MPNs.

The hierarchy is: Design Number → parent record → one or more colour variants, each with their own MPN. When a buyer asks about a specific fabric and colour, they reference both: the design number to identify the construction, and the MPN to specify the colourway. Both appear on the physical sticker. Conflating the two leads to order errors when a buyer believes they are ordering a specific construction-and-colour combination but only one of the two is specified unambiguously.

If you are establishing a design number convention from scratch, a few practical rules produce consistently workable results:

• Keep it short. Design numbers under 10 characters are easier to read on stickers, easier to say aloud, and less prone to transcription errors. The longer the design number, the more likely a digit or character gets dropped.
• Avoid special characters. Hyphens in a design number (SH-2026-042) look clean on a screen but cause problems in spreadsheets, search fields, and URL parameters. If you must use a delimiter, use it consistently and only once.
• Use consistent prefixes. If you use category prefixes, define them upfront and stick to them. A reference document of valid prefixes prevents new team members from inventing their own.
• Do not encode too much. A design number that encodes category, year, season, series, and variant type (SH-2026-AW-01-V2) has become a sentence, not an identifier. Store category, year, and season as separate filterable fields. Keep the design number short and opaque.

SampleLedger enforces design number uniqueness per organisation at the database level. Two designs in the same organisation cannot have the same design number — the system prevents it at the point of entry, before a duplicate can propagate to stickers, spec sheets, or buyer records.

Auto-generation is available as the default for organisations that want a hands-off approach — the system assigns the next sequential number. Manual entry is supported for organisations with an existing numbering convention, with uniqueness validation still enforced.

Every design number is referenced on the sample's QR sticker and on the public QR detail page. A buyer who scans a sticker sees the design number immediately, alongside the full spec — EPI, PPI, GSM, GLM, blend, and colourway. Learn more on the fabric sample tracking features page.