One source of truth for your models, colours and sizes.
Dozens of colours and sizes per model, two to four collections a year, and every channel wanting its own size notation, image format and label text. Managed as model, colourway and article, with one GTIN per size-colour combination, and published automatically to webshop, marketplaces, retailers and wholesale.
Product fiche · automatic
liveThe same product sheet in five versions, the latest with whoever touched it last.
One Excel per collection, one per customer, one for the webshop, one for the marketplace. A new colour in an existing design means adding a row in each of those files, retyping the thread count and the care code, and hoping the EAN from the ERP also lands in the Excel for bol.
Sizes and colours that explode
One model, eight colours, seven sizes: 56 articles, each with its own GTIN, price and stock. In Excel that is 56 rows to redo with every change to the model.
Every channel its own size and image
Zalando wants 1:1.44 on pure white and a size chart with three consecutive sizes, About You 3:4 with Intrastat data, bol forbids 'skin colour' as a colour name. One rejected listing a week is the norm.
Returns that start in the data
Online apparel sees 30 to 50 percent returns, a third because of size. Body measurements per size, fit, stretch and the size worn by the model in the photo are data you don't have today.
Product data in order in the textile sector
A 35-page working guide for product and marketing managers at brands, producers and retailers in apparel, footwear and home textiles. No PIM theory, but what you actually do.
- A field model for textile you can adopt right away: model, colourway, article and channel version
- GTIN per variant, size systems and size charts, textile labelling, GS1 Digital Link and RFID, and the feed specifications of Zalando, About You, bol, Amazon and Google
- What awaits textile in the next three years: destruction ban, Retexbel, the product passport for apparel, REACH, PPE standards and green claims
- A one-month plan, from Excel inventory to a first channel fed automatically
- Excel works, until it doesn't
- The field model for the textile sector
- From model to size: GTIN, size charts and images per channel
- Label, passport and producer responsibility
- From one source to every channel
- Live in one month: what it costs and returns
Model, colour and size in one product tree, every channel its own version.
Three levels with inheritance
The model carries composition, fit, care, certificates and size chart; the colourway carries colour code and images; the article carries GTIN, size with size system and price and stock from the ERP. A new colour is one colourway to create.
Images per colour, with type and AI flag
Packshot on white, ghost mannequin, on-figure with model size, detail and video hang on the colourway, with ratio, background and the machine-readable AI marking that article 50 of the AI Act requires since August 2026.
Channel rules before export
Per channel a title structure, size notation, category, image format and mandatory fields. A missing size chart for Zalando, a customs code for About You or a generic claim in the text shows up in the readiness before the channel rejects.
Label and certificates as data
Fibre composition per component as a structured list, from which PimLayer generates the label text in NL, FR and DE. OEKO-TEX, GOTS or GRS only with certificate number, certifier and validity: otherwise it is not a claim.
What your product data must be able to do in textile.
A selection from the field model in the whitepaper, for brands and retailers in apparel, footwear and home textiles.
Identification and collection
Model number and name, colour code with colour family, article number and GTIN per size-colour combination, variant group (item_group_id) for Google, Meta and Zalando, collection, season, carry-over and active from-to per channel.
Size
Sales size, size system (EU, UK, US, IT, FR) and size type (alpha, numeric, age), body measurements or dimensions per size according to EN 13402 or Mondopoint, fit and stretch. For home textiles: tuck-in flap, fitted sheet depth and set contents.
Material
Fibre composition per component in percent from Annex I of Regulation 1007/2011, non-textile parts of animal origin, weave, thread count and weight, material of upper, lining and sole, recycled content, mono-material and elastane percentage.
Use and care
Care symbols according to ISO 3758 (GINETEX licence via ETITEX), repair information and spare parts, and the label text per language generated from the composition.
Compliance
REACH test reports per colour (Annex XVII 72, azo, nickel), PFAS-free, certificates with number and validity, environmental claims with evidence file, PPE category and standard for workwear, CN code and country of origin, EPR category for Retexbel, batch ID and DPP URL.
Commercial and assets
Title and description per channel and language (Zalando maximum 100 characters), target group, pattern and style, price with 30-day price history, stock and delivery window from the ERP, images per colour in 1:1.44, 3:4 and 1:1, and matching articles for cross-sell.
The complete field model, with level (model, colour, article, channel version), data type and the channel for which each field is mandatory, is in chapter 3 of the whitepaper.
Every channel its own translation of the same model.
Textile has no classification like ETIM, but a tight set of agreements about the variant. What each channel asks for, and what PimLayer exports per channel.
Live in one month, collection by collection.
No long IT project. This is the order from the whitepaper, as we apply it at Belgian textile brands.
Inventory and data design
Which Excels, which channels, which customers. Product tree with model, colourway and article, specification library, taxonomy (colour families, size systems) and validation rules, before you import a single row.
Field model and size charts
Your Excel columns mapped to the specifications, fibre composition converted into a structured list, one size chart per model, CN code and weight completed per article.
Images and channel versions
Image sets per colour with type, ratio and AI flag, title and description per channel, the channel rules of Zalando, bol and Google as validation, price and stock from the ERP.
First channel live
Your webshop or a marketplace fed automatically. Then you scale up, collection by collection and channel by channel, through to wholesale and the retailers.
Frequently asked questions from the textile sector
How does PimLayer manage model, colour and size?
As three levels in one product tree: the model carries the shared specifications (composition, fit, care, certificates, size chart), the colourway the colour code and the images, the article the GTIN, the size with size system and the price and stock from the ERP. Adding a new colour is creating one colourway; the sizes and their GTINs follow from the model's size chart.
Can PimLayer deliver the feeds for Zalando, About You, bol and Google?
Yes. Per channel you define a channel version and channel rules: title structure and length, size notation and size system, category, image format and background, mandatory fields. The platform checks the rules before export and shows in the readiness which articles are not yet ready for which channel.
What do I do today for the product passport and Retexbel?
Structure what you need to know anyway: the composition per component as a list, CN code and weight per article, certificates with number and validity, test reports per colour and a batch ID. Those are the fields the EPR contribution (eco-modulation) and the passport will ask for; whoever fills them now only has to export in 2028.
How does PimLayer handle the many images per colour?
PimLayer is a PIM and a DAM in one. Packshots, ghost mannequin, on-figure, detail, video and 3D renders hang on the right colourway, with type, ratio, background colour, model size and AI flag. Every channel automatically gets the set in its own format.
How long does an implementation take, and do I need IT?
You usually go live within a month, 27 days on average, with onboarding included and a first channel fed automatically. PimLayer is configured, not programmed; IT mainly comes in for the ERP link.
Ready to get your product data for textile under control?
Whitepaper textile sector
35 pages with the field model, the channel rules, the regulation up to 2029 and the step-by-step plan. Free as a PDF, in Dutch.
Send me the whitepaperRequest a demo
See PimLayer at work with your own collection, colours and sizes. 30 minutes, no obligations.
Book a demoFree product data assessment
Leave your work email and get an analysis of your product data with concrete quick wins.
Request your assessment