How to organize an industrial catalog to simplify commercial inquiries

When the buyer can’t find it, they ask

The industrial buyer does not browse for pleasure: they look for a reference suitable for a specific application, with a standard, a presentation and availability. If the catalog does not provide that information, they write to WhatsApp with an open question ("do you have bearing grease?") and your salesperson starts from scratch. Multiply that by dozens of inquiries per day and you have a team acting as a search engine.

A well-organized catalog does not eliminate conversations; it makes them start better.

The five layers of an industrial catalog

Families: think like your buyer

Families should reflect how your client searches, not how your warehouse is organized. Ask your salespeople which are the ten most common inquiries and you will see which words buyers use. If they say "high-temperature greases," that can be a family or a filter, even if internally you have a different code.

Product pages: the minimum for someone to decide

Recommended fields

• Commercial name and internal reference.
• Brief description: what it is and what it is for, in two or three sentences.
• Typical applications.
• Technical specifications in a table, with units.
• Standards or certifications, only if current and documentable.
• Available presentations.
• Downloadable documents: technical data sheet, safety data sheet when applicable.
• Quote button with the reference already included.

For search engines, Google documents how to mark products with structured data based on the schema.org vocabulary. This helps the information be better understood, but it does not guarantee featured display nor ranking.

Filters without creating a maze

Filters help when the catalog has many references within a family. Choose a few attributes that truly differentiate products and use the same values across all product pages: if in one page you write "1 gal" and in another "gallon", the filter fails. Google has a specific guide on how to handle faceted navigation so it does not generate thousands of unnecessary URLs; your technical team should consider it.

The quote request

The quote button must carry context: the reference, the presentation and, if possible, the originating page. That way the salesperson knows what they are being asked about from the first message. If you use WhatsApp, the prefilled message can include the reference; if you use a form, ask only the data your team actually uses to quote.

Procedure

1. Export your product list with reference, name and current family.
2. Review with your salespeople the most frequent inquiries and the words customers use.
3. Define families and applications based on those words.
4. Choose between three and six filters per family and normalize their values.
5. Complete the product page template for the most consulted references first.
6. Define which data the quote request carries and who receives it.
7. Publish in phases: better 50 complete pages than 500 empty ones.

A real case for reference

The Petrogrease case, published by RealStack, is an industrial catalog with quoting via WhatsApp and the source recorded in each request. The published figures are: "Observed results — August 2 to September 30, 2026: 215 recorded requests; 117 requests from Google; 11 recorded payments for COP 15.255.000; 4 Google-origin requests recorded as closed; 161 product pages published." According to the case itself, these correspond to Petrogrease's recorded operation in that period and do not represent a guarantee of results for other businesses. They are results for that case and period; they do not indicate what will happen for another catalog.

Limits

This guide does not replace a technical review of your inventory nor validation of standards and certifications: publish only those you can document. It also does not guarantee a volume of inquiries.

Criteria to decide the structure

Filters deserve special attention: each combination can generate a distinct URL, and Google warns that poorly managed faceted navigation can create many near-duplicate pages. Use few filters — those your salespeople actually use.

Complete synthetic example

Synthetic example. A fictitious distributor of industrial hoses has 400 references in a price list. Their salespeople always ask the same things: fluid, pressure, temperature and diameter. The company organizes the catalog into five families by fluid type, defines a product page with those four attributes plus presentation and applicable standard, and enables filters only for pressure and diameter.

The quote button on each product page opens WhatsApp with a message that includes the reference. The salesperson receives the inquiry with the product identified and only asks for quantity and city. Example invented; does not represent outcomes.

How to use the product page template

1. Fill one row per reference, starting with the twenty most consulted.
2. Always use the same units.
3. Write the application in the buyer's language.
4. Leave blank what you cannot document; do not invent standards or certifications.
5. Review the template with a sales advisor before uploading it.

Questions to validate the catalog with your team

• Could a new salesperson recommend the correct reference using only the product page?
• Are the family names those used by the buyer or internal ones?
• What question do your salespeople repeat in every quote that is not on the product page?
• Which references are most consulted and which never are?

Diagnosis before starting

• Take ten recent quotes and note what the salesperson asked before responding.
• Check whether your reference list has consistent units and names.
• Ask two customers how they search for what they buy from you.

Signals that it works or not

• Good signal: requests arrive with the reference identified.
• Bad signal: the salesperson keeps asking the same data.
• Measure it yourself: in ten requests, count how many required an additional question.

A second example, in contrast

Synthetic example. A fictitious manufacturer of custom electrical panels has only twelve product lines, all configurable. They do not need filters: they create a page per application (mining, buildings, agribusiness) with sample drawings and a quote request that asks for voltage, current and intended use. Unlike the distributor in the first example, their catalog grows in depth rather than in quantity. Example invented.

What to do when something fails

• If buyers keep asking the same thing, that data is missing from the product page: add it.
• If a filter is hardly used, remove it.
• If quote requests arrive without a reference, verify that each product page's button includes it.

Common mistakes

• Organizing families using internal codes instead of buyer language.
• Publishing product pages without specifications or applications.
• Using different values for the same attribute.
• Quote buttons that do not indicate which product they come from.
• Publishing the entire inventory at once with incomplete product pages.

Checklist

• Families reflect how the buyer searches.
• Each product page has specifications with units.
• Filters are few and useful.
• Quotes arrive with the reference identified.
• Published standards or certifications have supporting documentation.