Most distributors do not have one product catalogue. They have five, and nobody owns the relationship between them. The ERP holds the list finance and the trade counter trust. The website holds a subset of it with better photography. A spreadsheet on somebody’s desktop holds whatever was last uploaded to a marketplace. Product catalogue management is the work of making those versions agree without maintaining each one by hand.
What product catalogue management actually means
Start with what it is not. It is not a piece of software. It is a set of decisions: what a product record contains, where it is authored, who approves it, and what each channel sees. Software is how you execute those decisions at 60,000 SKUs.
Your ERP already manages a catalogue of a sort. It holds part numbers, prices, pack quantities, stock and units of measure. That is the commercial spine and it is usually accurate. What it does not hold is everything the customer buys on. Thirty attributes they filter by. Four images. The datasheet PDF. The safety documentation. The description explaining why this valve and not the cheaper one. In most distributors those fields live nowhere in particular.
That gap is the whole problem. The ERP is the system of record for the transaction. Nothing is the system of record for the product.
The five places your product catalogue has to appear
Every distributor we work with publishes into at least four of these, usually five. Each one wants the same products described differently.
The ERP and the trade counter
Short descriptions, part numbers, pack sizes, price bands. Counter staff search by part number or by the phrase a customer says on the phone. The field that matters most here is the one everyone ignores. That is the searchable short description. It is often twenty characters of abbreviation inherited from a system replaced in 2009.
The website
Full attributes, faceted filtering, images, comparison tables, cross-sells. This is the only channel where the depth of your attribute model is visible to the customer. If your filters offer four options where the customer needed twelve, that is a catalogue problem showing up as a conversion problem.
Procurement systems and punchout
Large customers do not visit your website. They raise a requisition inside Coupa, SAP Ariba or Oracle. From there they either punch out to your site or consume a hosted catalogue file. Both routes have their own field requirements. Both fail silently when a unit of measure is wrong.
Marketplaces and feeds
Amazon Business, Google Shopping, trade platforms and sector data pools each have their own required attributes, image rules and category mappings. This is where a thin catalogue gets rejected rather than merely ignored. The record that passes on your own website can fail validation on marketplaces for one missing attribute.
The printed or PDF catalogue
It is not dead in distribution. Merchants, wholesalers and industrial suppliers still print, and the print run is the one deadline that forces the data to be finished. Print is also the strictest consumer of your data, because a missing dimension leaves a visible hole on the page.
A worked example: 62,000 SKUs and 380 suppliers
The following is a composite of distributor catalogues we have audited rather than one named client. The shape repeats often enough to be useful.
A distributor carries 62,000 active SKUs from 380 suppliers. Product data arrives in roughly forty formats: supplier portals, PDFs, price lists, ETIM files, and a lot of email attachments. Fourteen people touch product data as part of their week. None of them do it as their whole job.
The audit usually finds three numbers. Around eight to twelve per cent of SKUs have a complete attribute set for their category. Somewhere between two and five per cent are duplicates, created when a supplier reissued a part number in a new format. And the top 500 SKUs by revenue are in decent shape, because someone fixed them manually for a campaign two years ago.
That last number is the useful one. It tells you the team can produce good records. It also tells you the process cannot repeat it. So the fix is not a data cleanse. The fix is deciding what “complete” means per category, then making the supplier intake produce it. We go through that pattern in more depth in our piece on product data for industrial distributors.
Build one product catalogue, publish many
The operating principle is simple and almost nobody follows it. Author once, in one place, at the richest level any channel needs. Then publish a reduced view to each channel.
In practice that means the master record holds every attribute, every image, every document and every description variant. The website view takes all of it. The punchout view takes part number, short description, price, unit of measure and a category code. The marketplace view takes the attributes that marketplace validates against, mapped to its category tree. The print view takes a fixed subset chosen by the category manager.
Nobody edits the channel views. If a marketplace rejects a value, you fix the master and republish. The moment someone edits the export file to get a batch through, you have six catalogues again and no way to tell which is right.
Electronic catalogues are a commercial problem, not a technical one
Distributors underestimate this one consistently. Electronic catalogue exchange is how large accounts buy, and the formats are old, specific and unforgiving.
BMEcat is the XML standard used across European industrial, electrical and building distribution. It exists in versions 1.2 and 2005, and it is frequently paired with an ETIM classification. cXML PunchOut was created by Ariba in 1999 and is now owned by SAP. It lets a buyer browse your site from inside their own procurement system. SAP’s OCI does a similar job inside SAP procurement environments.
The technical work is not the hard part. The hard part is commercial. A single large customer can demand a catalogue format nobody in your business has seen. The deadline is two weeks and it is attached to a contract. If your data sits in one structured place, that is a mapping exercise. If it sits in the ERP plus three spreadsheets, it is a month of somebody’s life. Getting the classification layer right in advance is what turns the second situation into the first.
Four things that break a distributor product catalogue
Supplier reissues. A supplier changes its part numbering and sends the range again. Without a match on manufacturer part number, you now stock the same item twice, with different descriptions and different prices.
Units of measure. Sold per metre, priced per 100, packed in boxes of 25. Get this wrong in a punchout feed and a customer orders a hundred times what they wanted. We have seen it happen, and the credit note is the least of it.
Free text where a value list belongs. Thirty-one spellings of “stainless steel” across a catalogue is normal. Every one of them breaks a filter. This is an attribute model issue, not a typing issue.
Images that were never specified. Supplier images arrive at whatever size the supplier felt like. Marketplaces reject them, print cannot use them, and the website scales them badly. Specify minimum dimensions in the supplier agreement or accept the rework forever.
Who owns the product catalogue
The ownership question kills more catalogue programmes than the technology does. In B2B distribution the honest answer has four parts.
Commercial owns range: what is listed, what is discontinued, what is promoted. The product data team owns structure: categories, attributes, value lists, completeness rules. Marketing owns tone and imagery. IT owns the pipes to the ERP and the website.
One person has to arbitrate when those four disagree. They need to be senior enough to refuse a category manager who wants a one-off attribute for a single supplier. Without that role, the attribute model grows by accretion until nothing filters properly.
Supplier onboarding sits underneath all of it. If new products enter the catalogue incomplete, everything downstream is remediation. The repeatable version is in our guide to supplier onboarding for B2B distributors. We also run it as a service through supplier data onboarding.
Key takeaways
- A distributor product catalogue is one master record published as several channel views, not several catalogues kept in step by hand.
- The ERP is the system of record for the transaction. It is not the system of record for the product.
- Define completeness per category before you clean anything. Cleaning without a target produces work nobody can sign off.
- Punchout and electronic catalogue formats are contract requirements from large accounts, not IT projects. Treat them commercially.
- Free text where a value list belongs is the single most common cause of broken filters and rejected feeds.
- Somebody senior has to own the attribute model, or it grows until it stops working.
Where to start
If you are somewhere in this, the first useful step is small. Take your top 200 SKUs by revenue and one category you know is messy. Write down what a complete record looks like for that category, then measure how many of those 200 pass. That number decides everything else.
We do that exercise with distributors as a thirty minute conversation and a sample audit. No slides. Book a discovery call and bring a category export.