How do we manage thousands of SKUs when our product data sits in many spreadsheets?
Short answer: Product catalog management means keeping one trusted record for every item you sell, with its code, specs, images, documents and price levels, and sending that record to your website, quotes and customers. For thousands of SKUs (stock keeping units, your own item codes), pick one owner for each field, fix the field list, clean the data once, and make every other system read from that single record. A product information management tool, called a PIM, does this as software. A smaller catalog layer built on your ERP (enterprise resource planning, the system that runs stock and orders) can do it too.
Your product data lives in many spreadsheets, and you want thousands of SKUs in one place that people can trust.
I'm Ranjit, and I run Blur Studio: 15+ years building software, 120 apps taken live, and clients who have gone on to raise $10M+. I build AI systems and processes that help businesses do a lot more with a lot less time. I also work differently from most of what else is out there, more on that further down this page. Say hello.
What a product catalog is, and what managing it means
A product catalog is the full set of facts about what you sell. For each item it holds the part number, name, description, size, material, ratings, images, data sheets, category, and the items it goes with. It is not the price list, and it is not stock. It is the product story that a buyer needs in order to pick the right part. For more detail, see a spec sheet template.
Catalog management is the daily work of keeping that record correct and complete, and getting it to the places that need it. For a distributor or manufacturer with thousands of SKUs, that work is where time quietly leaks. One person fixes a spec in a sheet, the website still shows the old one, and a quote goes out with a third.
Where the mess usually comes from
- Supplier files. Every supplier sends data in its own shape: a PDF, a sheet with merged cells, a portal download.
- The ERP holds the minimum. Accounting and order systems store a short name, a unit of measure and a price. They were not built for twenty specs and six images per item.
- Copies. The web team, the sales team and the warehouse each keep their own version.
- No owner. Nobody is named as the person who decides what a field means or who approves a change.
The fields to hold for each SKU
| Group | Fields | Rule I use |
|---|---|---|
| Identity | SKU, supplier part number, barcode, brand, status | The SKU never changes and is never reused |
| Description | Short name, long description, search words | One short name used everywhere |
| Specs | Size, weight, material, rating, standards, compatible models | Each spec is its own field, not a sentence |
| Units | Unit of measure, pack quantity, minimum order quantity, lead time | Always state the unit beside a number |
| Files | Images, data sheets, certificates, install guides | Store the file once, link it many times |
| Structure | Category, variants, related and replacement items | Variants share a parent record |
| Commercial | List price, price levels, cost, tax class | Price lives in one place; the catalog reads it |
The one that trips people up is variants: the sizes, colors or lengths of one product. A bolt that comes in 12 sizes is one parent product with 12 child SKUs, not 12 unrelated records. If you set it up as 12 separate records, a change to the description has to be made 12 times.
How to bring thousands of SKUs under control
- Name an owner for the catalog and for each field. One person decides what "length" means and in which unit. Without this, nothing else holds.
- Fix the field list. Use the table above and cut it down to what buyers actually search and compare on. Fifteen fields kept clean beat sixty that are half empty.
- Pick the master record. Decide where the truth lives. Usually the ERP owns SKU, cost, stock and price, and the catalog owns everything descriptive. Write that split down.
- Gather and de-duplicate. Put every spreadsheet into one working file. Match rows by supplier part number and barcode. Expect duplicates and conflicting specs. Resolve them by product line, starting with the items that sell most.
- Set required fields by category. A fastener needs thread size and material. A pump needs flow rate and voltage. A product that lacks a required field is marked incomplete and does not go live.
- Load into one system. That can be a PIM, a database, or a catalog layer next to your ERP. Whichever it is, it should accept bulk imports and show a list of what is missing.
- Connect the readers. The website, the quote tool and the customer portal should read from the catalog. They should never hold their own typed copy.
- Add a change routine. New items and spec changes go through one review step, and every change records who made it and when.
A worked example with made-up figures
A distributor with 8,000 SKUs keeps specs in six sheets, one per supplier family. A quick audit of a sample of 200 items finds that 60 have a spec that differs between the website and the sheet that sales uses. The owner assigns one person, picks a field list of 18 fields, and loads the top 1,500 selling items first. Items that miss a required field are flagged instead of published.
These figures are invented, but the pattern is real: start with the items that earn the most, measure the gaps, and treat completeness as a number you watch. Good numbers to track are the share of products with every required field filled and the days from a new item arriving to going live.
Tools for catalog management
You have three broad choices.
- A spreadsheet or database you control. Fine up to a few thousand SKUs with one editor, as long as the header row is fixed and required fields are enforced.
- A PIM (product information management) tool. Software built for this job, with attribute sets, variants, approval steps, completeness scores and feeds to channels. Plytix, for example, describes its PIM as a system of record that stores, enriches and distributes product data across channels. Others are Pimcore (an open core PIM and digital platform), Akeneo (a PIM sold as Product Cloud), inriver (a PIM for manufacturers and brands), Salsify (a product experience platform for brands that sell through retailers) and Pimberly (a PIM and asset tool with customer and vendor portals). My guide to product information management software for distributors compares them, and PIM pricing shows what they cost.
- A catalog layer built on top of your ERP. It reads SKU, stock and price from the ERP, holds the extra specs and files itself, and feeds quotes and a portal.
If you are comparing options, ask what the ERP already does. A system such as an inventory management system tracks stock and locations well but rarely holds rich specs, and a custom ERP can be designed to hold them from the start. The tool matters less than the rules above. A PIM with no owner fills with the same mess as the spreadsheets.
Common failure points
- Loading messy data into a new tool. The mess moves; it does not clear. Clean by product line first.
- Too many fields. People stop filling them in.
- Two masters. If both the ERP and the catalog can edit price, they will disagree within a month.
- No go-live rule. Without required fields, incomplete items reach customers.
- Treating it as a one-off project. New items arrive every week. The routine is the real system.
How I'd approach this
I would not buy a tool first. I would spend two weeks on the field list, the owner and the split between ERP and catalog. Then I would clean the top-selling items and see how bad it really is.
For a small team with a few thousand to a few tens of thousands of SKUs, one ERP and no marketplace team, I lean toward a lighter catalog that sits next to the ERP rather than a full PIM. The part that pays off is not the catalog alone. It is joining the catalog, the quotes and the customer portal into one system, so a spec fixed once shows up in a quote and on the customer's screen. That is what I build at Blur Studio, on top of the ERP you already run, and you own the result.
If you sell through many channels in many languages and have staff whose full job is product data, price a real PIM instead. Either way, the clean data you produce in the first two weeks moves with you.
Questions people ask
What is product catalog management?
It is keeping one trusted record for each product you sell, with specs, images, documents and categories, and sending that record to your website, quotes and customers. The goal is that a fix made once shows up everywhere.
What is the difference between a product catalog and an ERP item list?
The ERP item list holds what accounting and orders need: code, short name, unit, cost and price. The catalog holds what a buyer needs to choose: specs, long descriptions, images and data sheets. They should share the same SKU and stay in sync. See custom ERP for how some businesses fold both into one system.
Do I need product catalog management software?
Not always. A well-kept table works for a few hundred products and one editor. Software starts to pay off when several people edit, when you sell through more than a couple of channels, or when you have thousands of SKUs with many specs. See PIM software for distributors.
How many fields should each product have?
Only as many as buyers search and compare on, often 15 to 25 per category. Fewer fields kept complete are worth more than many half-empty ones. Make the important ones required before a product can go live.
Where should price live, the catalog or the ERP?
In one place only. Most distributors keep cost, stock and price in the ERP and let the catalog read them. Two editable copies of price will disagree. A live price list that reads from the ERP keeps customer prices right; see price list template for the structure.
More in this topic: B2B: product catalogs and PIM (8 guides) →