Article numbers that last Why a rolling number beats a coded one
By Elias Gröndal, Founder & CEO at Resourced. Updated .
Five claims about one t-shirt.
Nothing to react to.
What the number is for
An article number is the handle a tech pack, a sample round, a purchase order, a warehouse and an accounting system all use to mean the same article. Everything else can change: the name, the colourway, the supplier, the price. The number has to survive all of it.
It is not for your customer. Nobody has declined a coat because the code was hard to remember. The number is internal plumbing, which is exactly why it deserves ten minutes of thought and then no thought at all.
If parts of the business do need a code they can read, give them one: a coded product description can live alongside the article number, built from the article’s attributes and free to change when they do, because nothing hangs off it. Be aware that two codes side by side can create confusion, and that on a sales call it is better to talk about the actual attributes: the fit, the colour, the fabric, not a string that stands in for them. A modern system should show those attributes wherever the article appears, so the number never has to carry them.
Every brand starts with a coded number
When a brand is small, the obvious move is a coded number: a few letters of the style name, an attribute, a colour, readable on sight. It works, and it works for years. Then the logic runs out of room.
Build yours, then run it for three years
Start from a shape brands on Resourced use today, make it yours part by part, and watch what three ordinary years do to it. The template Resourced would run is generated as you go.
None of the fixes are mistakes; each patch is reasonable on the day. But after a few of them the number is a set of rules with a set of exceptions, readable only by the people who were there when each was made. A new joiner sees noise.
To be clear: a break is not the end of the world. Brands live with collisions and rewrites every season and the goods still ship. The point is that the cost is unnecessary. The alternative costs nothing, at any point, so there is no reason to build a limitation into the business when you can stay fully flexible instead.
The rolling number
The alternative is to stop asking the number to describe anything and let it count. It is a key: what you hand a system to get the real data back. Three levels, each rolling on from the one above. These follow the Resourced Hydro range’s own templates:
An article is whatever varies below the style while the style stays the same garment: a colourway, an organic and a non-organic version, a men’s and a women’s size run. A neutral number lets the article level mean different things for different products without redesigning the scheme.
The pay-off is quiet. Mint the number the day a style is sketched and keep it to end of life. Recolour, recategorise, change supplier, move a season, add a gender: nothing is renumbered, and no meeting is ever spent deciding what a code should be.
The real cost, and when it lands
This is the argument that matters most, and it shows up months after the numbering was decided.
Development is development. Dusty Rose at the first fitting is Clay by sign-off. A material changes. A style moves category. None of that is a mistake. With a coded number, each is also an edit to the number, so a normal act of product development becomes a systems decision with two bad answers.
Retire it and start again
The style’s history splits in two: samples, comments, measurements and costings stay on the retired article, and the new one starts empty. If an order is out, the article you ordered is no longer the one you are producing.
Let the number update
The number on the purchase order, the label draft, the supplier’s sheet and three email threads no longer exists. Somebody reconciles it, under time pressure, more than once.
The second-order cost decides it. Once a team learns that renaming a colour is expensive, they stop renaming colours. The admin has begun making product decisions. That is the real price of a coded number: not the afternoon spent fixing it, but the decisions nobody takes because fixing it is an afternoon.
A rolling number has nothing to react to. Rename the colour, change the material, move the category, place the order. It does not move, because it was never a claim about any of them.
The colour number, and why it is the hardest to give up
Colour is the most common piece of logic we come across in an article number, and it tells the same story almost every time. Black is 9000, white is 1000, everyone learns it in a week. Then an off-black arrives, so 9001. A black with white trim, 9002. Two years on, a plain true black is added and there is no number left that says this is the actual black. It takes 9003, and the number space no longer means what everyone was taught.
The version that survives: a group, and a queue
If colour in the number is worth the upkeep, keep only the stable part and let the rest roll. The colour group is more stable: a black stays in the black family whatever the yarn does. So 9 means “a black”, and the digits after it mean one thing: the order it was created in.
9000 is not “the real black”. It is “the first black”. The number after the group prefix is a queue position, not a verdict.
More stable is not immune. A colour can still change group: the charcoal signed off as a black comes back from the dye house as a grey, or the range team decides the off-blacks belong with the greys after all. Then the 9 is wrong, and the article faces the same decision as any coded number: retire it and create a new one, splitting its history, or keep a number that no longer follows its own logic. Rarer than a rename, but the same two bad answers. Only a plain counter never asks.
The objection is always the same: surely the proper black should be 9000? No. No black deserves anything. It takes the next free number, and the name, the Pantone and the group travel with it downstream. Decide alongside this whether your colour library is per brand or shared across the group, and whether a colour is identified by its Pantone or by a typed name. Those two questions cause more duplicate colours than the numbering ever does.
“But then I can’t tell what it is”
You will still learn your best sellers. The number on the style that pays the rent is in your head within a season, as it always was.
Everything you wanted to read is still there, and more of it. Name, colour, Pantone, colour group, season, supplier, category, gender. A code carried three of those, badly. Fields carry all of them precisely, and any modern system groups, filters and reports on them without the number’s help.
If a short human reference helps, build one. For the shelf or the collection meeting, a readable label is reasonable. Make it a field rather than the article number, so it can change when it stops being useful.
The one answer to push back on is “our ERP requires that format”. Sometimes true. More often it is a preference someone configured years ago. Ask before you design the next decade around it.
History stays. Only what comes next changes.
Does this mean renumbering six thousand articles? No, and it should never be attempted. Changing approach is a line in the sand, not a migration. Everything that exists keeps its number for life, and every purchase order, care label, invoice and spreadsheet that quotes it stays correct. What changes is everything created from that point: new styles, and new colourways on existing styles. Draw the line at a season boundary and it is almost invisible.
Before the line
Keeps its number, exactly as it is. Never rewritten, never reissued, never reconciled.
After the line
Rolls. New styles and new colourways take the next number in the sequence.
Two conventions live side by side for a few seasons, and that is correct rather than untidy. The old numbers are not wrong; they are finished. In Resourced this is the default: numbers carried in from a previous system are held exactly as they arrived, and a new template changes only what gets created next. Renumbering an existing catalogue is a separate, deliberate action, and our advice is almost always not to.
How this is set up in Resourced
Numbering is configured per brand on the Article Numbers page: one template per level, built from the variables available at that level. These are Resourced Hydro’s:
{{ sequential_number | pad_left: "10000" }}
10130
{{ product_number }}-{{ sequential_number | pad_left: "000" }}
10130-001
{{ article_number }}-{{ sequential_number }}
10130-001-1
The product number rolls brand-wide and can start where you like: start at 1000 and your first style is 1000, which spares you the look of a catalogue with four items in it. The article number rolls within its product, so the first colourway on every style is 001. The SKU rolls within its article, or takes the size code from your size chart.
The variables go well beyond a counter. Hierarchy codes, creation date, gender, tags and custom fields at product level. Colour name, colour code and colour group code at article level, which is the mechanism behind the 9-for-blacks example. Size code and size value at SKU level. Colour codes can be minted automatically from a numeric range you set, one stable code per colour for life or more than one where three blacks differ by material, with a collision number where two articles would otherwise land on the same string. It all works. It is simply more to maintain than a rolling number, and we would rather you chose it knowingly.
The sharp edge worth knowing about
Whatever you build the number from, you have decided what can renumber it. A colour code in the article template means recolouring an article changes its number; a gender initial means the day a style becomes unisex, the number moves. That is the cost described above, made mechanical.
Individual numbers can be set by hand and are then left alone, which is right for legacy articles and wrong as a way of life. If you lock numbers routinely, the template is telling you something.
Questions this usually raises
What is an article number for?
It is a key: the handle a tech pack, a sample round, a purchase order, a warehouse and an accounting system all use to mean the same article. It is not for the customer and it does not need to describe anything. Its one job is to mean the same article in five years.
Should the colour be in the article number?
Colour is the most common piece of logic in an article number and the first to break: an off-black arrives, a colour is renamed at sign-off, a plain black is added late. If colour is worth keeping, keep only the colour group as a prefix and let the digits after it roll. Better still, keep colour as a field and let the number count.
What is a rolling article number?
Three counters, each rolling on from the level above: a product number for the style, an article number that adds the colourway’s position under it, and a SKU number that adds the size. In Resourced Hydro’s templates that reads 10130, 10130-001 and 10130-001-1. Nothing in it is a claim about the article, so nothing about the article can break it.
Do we have to renumber existing articles if we change the structure?
No. History is kept: existing articles keep their numbers for life and only what you create next follows the new pattern. Old numbers live alongside a new structure; the change is a line in the sand, not a migration.
How do people tell what an article is without a coded number?
From its attributes, which are fields: category, gender, colour, season, material. A modern system shows them wherever the article appears. If part of the business wants a readable code, a coded product description can live alongside the article number, free to change when the attributes do, because nothing hangs off it.
Before you have this conversation
Six questions. Answer them and the decision takes twenty minutes rather than three meetings.
- Who reads the number, and to do what? Picking from a shelf, quoting a supplier, naming a style in a meeting. Each has a different fix, and most are not the number.
- What would have to change for the number to change? The target answer is “nothing”.
- What are you encoding today that is really a filter? Season, gender, category and division are almost always fields wearing a costume.
- Is the legacy constraint real? Does a downstream system require a format, or does someone prefer it? Get it in writing before you design around it.
- Does it survive ten times the catalogue? Do the arithmetic on digits now, not at 8,000 articles.
- Who owns it? One owner, one place. Numbering invented independently by three teams is the actual failure mode.
And settle in the same sitting how deep your product hierarchy goes and what each level is called; the two decisions lean on each other. Building a hierarchy that scales