Double Product Hierarchy in B2B Catalogs

B2B product catalogs often hold thousands of SKUs that differ only in technical details. Take a company selling tool holders for CNC milling machines. Buyers look for holders by spindle mount, so the website needs a separate category for each mount type.

The product team sees all of them as one product type with the same attributes, prices and rules.

One structure cannot serve both needs. This is why a B2B catalog needs two hierarchies: one for buyers and search engines, and one for the people who manage the products.

On the website, the tool holders from our example appear in five categories, one per spindle mount: SK DIN 69871, MAS-BT, SK DIN 2080, HSK and PSC. For the product team they are one product type, tool holders for CNC milling. An ER32 collet chuck exists in all five mounts, but technically it is the same product with the same set of attributes.

• The front-end hierarchy is built for buyers and search engines. It is a tree of categories, as deep as your market needs.
• The internal product type is built for the product team. It is flat: every item belongs to exactly one type, grouped by technical similarity, like hammers with hammers and screwdrivers with screwdrivers.

Most platforms built for B2C give you only one structure, so the website and the back office end up fighting over it. With two separate hierarchies, the website can go as deep as marketing wants while the product data stays simple.

The category tree on your website serves two goals.

• User experience. Marketing and sales teams can argue for years about the right structure: a few broad categories with powerful filters, or many detailed categories with simple filters. There is no universal answer, so the platform should allow both.
• Search and AI visibility. Search engines and AI assistants reward pages with real content. Every extra category can target its own search query, but it also needs its own text, not an empty list of products.

The same product can sit at very different depths. With a short structure, the tool holder lives at the second level: catalog / tool holders / product. With a deep one, it sits at the fourth: catalog / clamping systems / tool holders for milling / SK DIN 69871 / product. Both approaches work. The choice is yours, and it should not depend on how your product data is organised.

The internal product type keeps your data consistent and compatible with your ERP, CRM and other systems. In the back office it drives most of the business logic:

• Attributes and filters. Each product type has its own set of attributes, and every product stores its values. On the website this becomes filters: a buyer picks three parameters and narrows hundreds of items down to a few.
• Discount groups. One discount applies to all products of a given type and brand.
• Pricing and margins. Different product types can have different discount structures and target margins, depending on competition.
• Logistics and admin rules. Packaging, shipping and lead time rules are set per type.
• Sales and purchase reports. Profitability is tracked by product type, not by website category.

In most B2B companies the product structure already exists in the ERP or in a master spreadsheet, and changing it just to fit a website is expensive and risky. With a double hierarchy you don't have to. Atlaya keeps the internal product types exactly as your product team needs them and builds the customer-facing category tree on top, as deep or as flat as your market requires. Filters, prices, discounts and integrations work from the product types, so the website structure can change without touching your data.

This is how the catalog of cncmarket.ca works: thousands of SKUs, from cutting inserts to CNC machines, managed by one product owner. See what is inside the platform.