Product Catalogue Management: Process, Roles, Metrics and Tools

Catalogue management is the ongoing work of getting products into a catalogue and keeping every record complete and correct. It also covers publishing each record to its channels and retiring it cleanly at the end of its life. Product catalogue management covers six stages: intake, structure, enrichment, governance, publishing and retirement. Done well, nobody notices it. Done badly, it is why filters return nothing, why marketplace listings get rejected and why capable people spend every week inside a 200-column spreadsheet.

What is catalogue management?

Catalogue management is the operating discipline behind a product catalogue. It decides how new products arrive, where they are classified and which attributes they need. It also sets who approves them, which channels receive them and when they come off sale. The goal is a catalogue where every record is complete enough to be found, compared and bought on every channel it appears on.

American sources spell it catalog management. Either way, it is wider than any single system. A PIM, an ERP and an ecommerce platform each hold part of the catalogue. Catalogue management is the process that keeps them agreeing with each other.

One distinction matters early. Most catalogue management advice assumes product data already exists in reasonable shape and just needs organising. For most retailers and distributors it does not. Supplier data arrives as PDFs, price files and half-filled templates. The hardest part of the job sits upstream, before there is anything worth managing.

The six stages of product catalogue management

1. Intake

Supplier data arrives: a range spreadsheet, a price file, a folder of datasheets, sometimes a BMEcat or ETIM file. Intake captures it, matches it to existing records by GTIN or manufacturer part number and flags genuine new lines. The common failure is treating intake as copy and paste, so every supplier's quirks land directly in the catalogue.

2. Structure

Each product is classified into the master taxonomy, which decides the attributes it needs. A cordless combi drill needs voltage, chuck size and maximum torque. A consumer unit needs number of ways and main switch rating. If classification is wrong, every later stage works against the wrong checklist. The guide to product taxonomy covers how to design that tree.

3. Enrichment

Missing attributes are filled from datasheets, images and supplier sites. Values are normalised so "12V", "12 volts" and "12 Volt" become one value. Titles, descriptions and media are added. This is where most of the effort goes, and where product catalogue enrichment software does the bulk extraction and classification work.

4. Governance

Records are checked against rules before they go live. Required attributes are present, values come from the allowed list, the GTIN check digit is valid and the images meet channel specifications. Governance also covers ownership: who can change a category, who approves a new line, who signs off a price change.

5. Publishing

Approved records go to each channel in its own shape. The website needs one set of fields, Google Merchant Center another and an Amazon or Mirakl marketplace a third. Publishing includes tracking rejections and fixing them at source, not in the channel.

6. Retirement

Discontinued products need an end state: a replacement suggestion, a redirect for the product page, removal from feeds and an archived record for returns and warranty queries. Catalogues that skip retirement fill up with dead SKUs that skew completeness and confuse search.

Who does what in catalogue management

Titles vary between businesses, but the same five roles appear in almost every catalogue team.

• Category or range manager. Owns which products are listed, approves new lines and sets priorities for enrichment.
• Product data or catalogue manager. Owns the taxonomy, attribute schema, data rules and the weekly operating rhythm.
• Data executives or content team. Do the hands-on intake, enrichment and fixing, increasingly as reviewers of automated output.
• Ecommerce or channel manager. Owns publishing, channel requirements and rejection rates.
• Supplier. Provides source data and answers queries. Good catalogue management gets more from suppliers without depending on them.

The handoffs between these roles are where time disappears. A new range can sit for a week waiting for a category decision nobody knew was needed.

A weekly catalogue management rhythm

Catalogues decay continuously, so the work runs on a cadence rather than as projects. A workable week for a mid-sized retailer or distributor looks like this.

• Monday: intake triage. Review everything that arrived from suppliers last week. Classify, de-duplicate and set a target live date for each range.
• Tuesday to Wednesday: enrichment and review. Run extraction and attribute fill on new ranges. Reviewers check low-confidence values rather than keying every field.
• Thursday: governance and approval. Range managers approve records that pass validation. Failures go back with a specific reason.
• Friday: publishing and metrics. Push approved records to channels, clear rejections and review the week's numbers by category.

Alongside the weekly cycle, a monthly slot covers taxonomy changes, discontinued lines and the worst-performing categories by completeness.

Catalogue management metrics that matter

Completeness. The share of required attributes filled with valid values, measured per category and per channel. It predicts whether filters and comparison work. Bowens Australia took its PIM completeness from 30% to 94%, as set out in the Bowens Australia case study.

Time to live. The elapsed time from supplier data arriving to a sellable record live on a channel. It measures the whole pipeline, not one step. Track the median and the slowest ten per cent of ranges, because the slow ones show where handoffs break.

Error rate. The share of records failing validation or being rejected by a channel. Track it by channel and by cause: missing GTIN, invalid value, image specification and so on.

Manual touch rate. The share of records someone edited by hand. A rising touch rate means the process is consuming the team rather than scaling.

Where catalogue management fails

• Private spreadsheets. When people stop trusting the catalogue, they keep their own copies. Within a year there are five versions of the truth.
• Supplier structure as catalogue structure. Importing each supplier's categories and column names imports their inconsistencies as architecture.
• No single owner of the schema. Attributes get added by whoever needs one, so the same property ends up in three fields.
• Fixing data in the channel. Editing a rejected listing directly in Amazon or Shopify fixes it once. The next feed overwrites the fix.
• Enrichment as a project. A one-off clean-up lifts completeness for a quarter. Without enrichment at intake, new ranges pull it straight back down.
• No retirement process. Dead SKUs stay live in feeds, drag completeness scores down and return in site search.

Catalogue management tools

No single tool covers every stage. It helps to be honest about what each kind does well.

Spreadsheets. Fine below a few thousand SKUs with stable suppliers. They break on version control, validation and attribute sets that differ by category. A 200-column sheet where most columns are blank for most rows is the usual sign. The guide to managing large SKU catalogues without drowning in spreadsheets covers the transition.

PIM. The system of record for product data. A PIM such as Akeneo or Plytix stores records, enforces the attribute schema, manages workflow and syndicates to channels. It governs and distributes data well. It does not create missing data on its own. SKULaunch includes a built-in PIM layer for teams without a separate system of record, and also feeds external PIMs.

Ecommerce platform catalogue. Shopify, Magento and BigCommerce all hold their own product catalogue. For a small, single-channel range this can be the only catalogue. For larger ranges it is better treated as a destination.

Upstream enrichment. Extraction, classification, normalisation and content generation applied to supplier data before it reaches the system of record. This is the layer that addresses completeness at source. Mole Valley Farmers enriched 35,000 SKUs in three weeks this way, as the Mole Valley Farmers case study describes.

A practical rule: if data is clean and the problem is organising and distributing it, start with a PIM. If data arrives incomplete, no amount of downstream management fixes what was never captured, so start with catalogue enrichment.

Catalogue management FAQs

What is catalogue management?

Catalogue management is the process of bringing products into a catalogue and keeping every record complete and accurate. It also covers publishing records to each sales channel and retiring them when they are discontinued. It covers intake, classification, enrichment, governance, publishing and retirement. The aim is a catalogue where every product can be found, compared and bought on every channel it is listed on.

What is the difference between catalogue management and PIM?

A PIM is a system: software that stores product records, enforces an attribute schema and sends data to channels. Catalogue management is the operating process around it, including supplier intake, enrichment, approvals and retirement. A business can run catalogue management with a PIM, an ecommerce platform's own catalogue or spreadsheets. Spreadsheets stop scaling past a few thousand SKUs.

What does a catalogue manager do?

A catalogue manager owns the structure and rules of the product catalogue. That usually means the taxonomy, the attribute schema, validation rules and the weekly process that moves supplier data to live records. They track completeness, time to live and error rates by category, and decide where enrichment effort goes. In smaller businesses the role often sits with the ecommerce manager.

How do you measure catalogue management?

Four measures cover most of it. Completeness shows the share of required attributes filled, by category and channel. Time to live shows how long supplier data takes to become a sellable record. Error rate shows the share of records failing validation or channel checks. Manual touch rate shows how many records needed hand editing, which reveals whether the process scales.

Do I need catalogue management software?

Below a few thousand SKUs with a handful of stable suppliers, a disciplined spreadsheet and the ecommerce platform's own catalogue can work. Past that, completeness drops and listing times stretch. Choose software by where the catalogue breaks: a PIM if the problem is governance and distribution, an enrichment tool if the problem is incomplete supplier data.

Key takeaways

• Catalogue management runs end to end: intake, structure, enrichment, governance, publishing and retirement.
• Five roles appear in most teams, and most lost time sits in the handoffs between them.
• Run it on a weekly rhythm, not as annual clean-up projects.
• Track completeness, time to live, error rate and manual touch rate by category and channel.
• Spreadsheets, PIMs and upstream enrichment each cover different stages. Pick tools by where the catalogue actually breaks.

See it in practice: measure product data completeness by category and channel, consolidate ERP, PIM and supplier data into one product record and move the catalogue off spreadsheets.