B2B and distribution
Industrial and trade catalogues were designed for someone who already knows the part number. The buyer who does not is filtering on thread size, voltage or tolerance, and those live in a PDF datasheet rather than in a field.
Which specs to map firstfrom one category export

The market
Where the fact already is
Nothing here is missing from the catalogue. It is missing from the schema, which is a different problem with a cheaper fix.
In the description, as prose
Voltage rating
Thread size
Tolerance class
In the filters, as a field
The last row is already a field, which is why nobody ever files a complaint about it.
What happens here
An engineer needs a valve rated to a specific pressure in a specific thread size. Your catalogue has eleven that fit. The website can show all of them in a list ordered by part number, and it cannot filter by either of the two things that decide the purchase.
So the engineer calls, or emails, or gives up and buys from whoever's site could answer it. The sales team answers the same specification question many times a week and treats it as service rather than as a catalogue defect, because the catalogue was never expected to answer it.
The specifications almost always exist. They are in the supplier datasheet that came with the range, in a PDF nobody mapped into a field. That makes this the sector where the gap between what you hold and what your site can use is widest, and usually the cheapest to close.
The spec is not missing. It is in a PDF, which is the same as missing to everyone except the person who already knows the part number.
Illustrative of this sector's shape. The measured figures are on the method page, with the command that reproduces them.
The situation
What a buyer here is trying to decide: Which part meets the specification I have to hit?
Specifications trapped in supplier PDFs and never mapped into the catalogue
Search that works for a part number and fails for a requirement
Hundreds of variants distinguished only by a suffix in the product code
Sales time spent answering specification questions the catalogue should answer
Red rows are the ones a purchase turns on and the catalogue mostly does not record. Those are the rows an audit surfaces and a coverage report buries.
| Value | |
|---|---|
| Voltage rating | 34% |
| Thread size | 47% |
| Tolerance class | 19% |
| Pack quantity | 91% |
Where it usually already lives: Usually a mapping job. The specification is in a supplier datasheet or a feed you already receive, and the audit separates the fields you can map this week from the ones that need real acquisition.
What happens
Three things, and only the first one needs anything from you.
A CSV or JSON export of a single category. Product name, description, category, price, and whatever attributes you already record.
Every missing attribute scored by how much recording it would change what a buyer in your sector can decide, with the affected products attached.
Most of the repair is work your own team can do. When it is done we recompute on the repaired catalogue and show you exactly what moved.
Questions from this sector
Pick the shelf where you most suspect buyers struggle. You get a ranked list, the affected products, and half an hour with whoever owns merchandising.
A fixed fee, no obligation, and if your catalogue is already fine we will say so.