Product master data: the unglamorous key to digital fashion
Style numbers, colour codes, size scales and identifiers decide whether showrooms, portals, feeds and invoices work. A practical guide to getting product master data right.
KEY TAKEAWAYS Summary by the editors
- Product master data is the core set of identifiers and attributes that define each style, colourway and size across all systems.
- Most digital problems in fashion, from wrong stock in a B2B portal to rejected retailer orders, trace back to inconsistent master data.
- Clear conventions for style numbers, colour codes, size scales and identifiers should be agreed before collections are created, not fixed afterwards.
- Data quality needs named owners, measurable completeness rules and checks at each handover in the season calendar.
- Improving master data is a continuous process that pays off in every channel, especially wholesale.
A buyer orders a style in navy through a B2B portal. The ERP knows it as dark blue, the retailer's system expects a different colour code, and the size labelled 40 on the order is 10 in another market's scale. Nothing is technically broken, yet the order needs manual correction and the delivery slips. This is a product master data problem, and it is one of the most common hidden costs in fashion.
What is product master data?
Master data is the stable, core information that defines products and is shared across processes. It is different from transactional data, such as orders and stock movements, and from rich content, such as descriptions and images. In fashion, product master data typically includes:
- Style number and its structure, including any embedded season or category codes.
- Colour codes and colour names, plus colour families for filtering.
- Size scales and conversions between markets, such as European, UK, US and international letter sizes.
- Product identifiers such as GTINs for every colour and size combination.
- Classification: season, collection, category, gender and product group.
- Core attributes: composition, country of origin, customs tariff codes and care instructions.
- Commercial attributes: prices by market, delivery windows and status such as carry-over or discontinued.
Why does master data matter so much in fashion?
Fashion multiplies data. A single style can become many SKUs, each needing correct identifiers, and a new collection arrives every season, often with deliveries in between. Every channel, from a digital showroom to a retailer's EDI system, depends on these records. A small error in a parent style, such as a wrong composition or size scale, is copied into every colourway and size and then into every channel.
The consequences are concrete: buyers see incomplete or contradictory information, retailer integrations reject orders, warehouses receive cartons that do not match dispatch notices, and customs or labelling errors create compliance risk. Teams spend time on correction rather than selling.
Which conventions should be agreed first?
The most valuable decisions are the ones taken before any collection is created. Changing conventions later means mapping old and new codes for seasons to come. Priorities typically include:
- Style numbering: a stable logic that does not change when a style is carried over into another season.
- Colour master: one list of colour codes and names, with rules for how new colours are added.
- Size scales: defined scales per category, with documented conversions for each market.
- Identifiers: a process for assigning GTINs at the right moment, usually when a colour and size combination is approved for selling.
- Mandatory fields: a list of attributes that must be complete before a style can move into selling channels.
How do you organise data quality as a team?
Data quality is an organisational problem as much as a technical one. It works when responsibilities and checkpoints are explicit. A practical model has three elements.
First, ownership: each attribute group has a named owner, for example product development for composition and measurements, merchandising for classification and colour names, and sales operations or finance for prices. Second, completeness rules: each channel has a defined set of required fields, so readiness can be measured rather than assumed. Third, checkpoints: the season calendar includes dated data milestones, such as master data complete before salesman samples are photographed, and content complete before the selling period opens.
- Run a completeness report per collection and channel at each milestone.
- Track recurring errors and fix their cause, such as a confusing input screen or a missing rule.
- Limit the number of people who can create new colour codes or size scales.
- Review conventions once a year with all system owners.
Where should a brand start?
A full data clean-up is rarely realistic in one go. A better approach is to start with the current and next season, where errors cost money now, and apply the agreed conventions consistently from there. Older data can be cleaned when carry-over styles are reused or when a system migration requires it.
Systems can help, but only once the rules are clear. Validation in the PLM or PIM can block a style from moving forward with a missing composition or an unknown colour code, and integrations can reject records that break the agreed conventions. Automated checks make good practice the easy path rather than an extra task.
Measuring progress keeps the effort honest. Simple indicators such as the share of styles complete at each milestone, the number of order corrections caused by data errors, or the time from style approval to availability in selling channels show whether the work is paying off. Master data will never be glamorous, but it is the foundation on which every digital selling tool depends.
Frequently asked questions
What is the difference between master data and product content?
Master data is the core, stable information that identifies and classifies a product, such as style number, colour code, size scale and identifiers. Product content is the richer material used to sell it, such as descriptions, images and marketing copy, usually managed in a PIM.
Who should own product master data?
Ownership is usually split by attribute group, with product development, merchandising, sales operations and finance each owning their part. A central data owner or team should coordinate conventions and resolve conflicts.
Why does every size need its own identifier?
Retailers, warehouses and integrations track stock, orders and deliveries at the level of each colour and size combination. A unique identifier such as a GTIN for each one allows systems to exchange orders, dispatch notices and invoices without ambiguity.
One edition every weekday morning. Read in five minutes. Free for industry professionals.
