Skip to Main Content

A Mental Model for B2B Product Catalogs

By Matt Everson

Principal at Astuteo

March 9, 2026
Isd product warehouse

Originally developed by Astuteo for our B2B manufacturer clients, this six-category schema is designed to maintain robust product organization while adapting to always-changing sales priorities. Whether you're restructuring an existing content model in your CMS or designing a new product database schema in your CRM, this framework provides a foundation for strategic planning, technical implementation, and revenue optimization.

The Challenge of B2B Product Organization

When it comes to content management, organizing a B2B manufacturing product catalog for long-term marketing success depends on your website's ability to accommodate changes in strategy, explore UX improvements, and work iteratively in new directions. But that process rarely goes as planned:

  • Internal stakeholders often have competing priorities and different perspectives on product positioning
  • Business requirements shift with market conditions, competition, and revenue targets
  • Key leadership is hired and fired, with new leaders given mandates for change
  • Products come and go, with solutions repackaged for different sales plays
  • Market disruptions and unforeseen challenges demand rapid adaptation

With so many unknowns to navigate, it's imperative that each product in your digital catalog remains as marketable, relational, and actionable as possible:

Marketable
Each product needs to stand on its own. Whether it's being featured at a tradeshow or highlighted in a campaign, it needs an independent digital presence that isn't locked into a broader schema or solution.
Relational
Products should have flexible connections. A support product or accessory might relate to multiple flagship products. Solutions aren't fixed packages, but adjustable collections that can be reconfigured if needed.
Actionable
Every component should be independently quotable, even when the immediate business need isn't there. This future-proofs your content model and ensures you can adapt to any future sales scenario.

A carefully considered B2B product schema supports this cause, while an overly simplistic or poorly opinionated one will forever be a headache.

The framework outlined here breaks B2B products and related marketing strategies into six categories. Together these form a malleable collection of product types that offer a strong starting point for team alignment and planning.

Type 1: Solutions

A solution is a collection of your products and services designed to solve a customer problem. This is commonly a simple grouping, with additional content or functionality attached to the Solution object. Given the highly custom nature of B2B selling and the prevalence of solution-based sales strategies, it's one of the most important concepts in B2B marketing – involving long sales cycles, high-touch experiences, and multiple stakeholders.

Type 2: Flagship Products

This is a feature product, usually customizable, or a line of similar products marketed as a whole. Niche companies are often built around a single flagship product, while a mid-market manufacturer may have as many as a dozen. Often expensive, the purchasing process is still complicated, but more frequently initiated by the customer. Brand building, product evangelism, display advertising, and customer reviews are all pivotal components in flagship product marketing.

Type 3: Standard Products

For lack of a good label, this is a default product. It may be an off-the-shelf item, a model within a product line, or other non-customizable good. Purchases are typically made by individuals (not groups) making the sales cycle shorter, or even compulsive, due to lower cost and less commitment. As non-customizable products, specifications matter more in marketing – category groups, faceted navigation, filtering, and technical relatability are key UX imperatives. By the same token, search engine optimization (SEO) offers an opportunity at this level given the many different technical features that can lead to a product being desired and discovered.

Type 4: Accessories

This concept includes accessories, add-ons, or extensions – any item designed to work in conjunction with a parent product. As such, they are rarely purchased alone, but offer optionality that makes standard products more attractive. As properties go, accessories typically follow the same format as standard products but require extra context. They might be hidden from top-level product listings, presented as part of a configurable whole, or incorporated as upsell options during checkout. How these can appeal to individual desires (e.g. personal status, time-savings, convenience) is also something to consider.

Type 5: Consumables

Consumables include any part or product that is continuously used up during the operation of its parent product. They live alongside Support Products in the broader schema, but are differentiated by regularity and need. Like cutting inserts or filter cartridges, they are required for operation and consumed at a regular pace. A "set it and forget it" approach to sales is ideal (e.g. intelligent restocking, subscription service plans, fixed budget allocations), but routine check-ins by way of sales routes or email marketing automation are also common.

Type 6: Support Products

Support Products is a broad category that encompasses replacement parts, productized services, or subscriptions needed to maintain a product or system. Examples include extended warranties, annual calibration services, routine cleaning, or other scheduled maintenance. Customer care is the over-arching principle of this category and "peace of mind" is what customers are actually buying. Beyond the initial customer education and upselling opportunities, discoverability is key (i.e. site search, SEO) for both replacement parts and service solutions – backstopped by responsive, high-quality customer care.

# B2B Product Schema

A mental model for organizing industrial and manufacturing product catalogs into six product types.

## Core Principles

Every product in a B2B catalog should be **marketable**, **relational**, and **actionable**.

- **Marketable**: Each product stands on its own with an independent digital presence — not locked into a broader schema or solution grouping.
- **Relational**: Products have flexible connections. An accessory might relate to multiple flagship products. Solutions are adjustable collections, not fixed packages.
- **Actionable**: Every product is independently quotable, even if there's no immediate business need. This future-proofs the content model.

## The Six Product Types

### Type 1: Solutions

A collection of products and services grouped to solve a customer problem. Solutions are flexible containers with additional content or functionality attached — not products themselves. Long sales cycles, high-touch experiences, multiple stakeholders.

### Type 2: Flagship Products

A feature product (usually customizable) or a line of similar products marketed as a whole. A niche company may have one; a mid-market manufacturer may have a dozen. Expensive, complicated purchasing process, typically customer-initiated. Marketing levers: brand building, product evangelism, display advertising, customer reviews.

### Type 3: Standard Products

An off-the-shelf item, a model within a product line, or other non-customizable good. Purchased by individuals (not groups), shorter sales cycle, lower cost. Specifications matter most — category groups, faceted navigation, filtering, and technical comparability are essential UX elements. Strong SEO opportunity due to the volume of discoverable technical features.

### Type 4: Accessories

Add-ons, extensions, or items designed to work with a parent product. Rarely purchased alone. Follow the same format as standard products but need extra context — may be hidden from top-level listings, presented as part of a configurable whole, or shown as upsell options. Consider how they appeal to individual desires (status, time-savings, convenience).

### Type 5: Consumables

Parts or products continuously used up during operation of a parent product. Differentiated from support products by regularity and necessity — like cutting inserts or filter cartridges. Required for operation, consumed at a predictable pace. Ideal sales approach: intelligent restocking, subscription plans, fixed budget allocations. Routine check-ins via sales routes or email automation are also common.

### Type 6: Support Products

Replacement parts, productized services, or subscriptions needed to maintain a product or system. Examples: extended warranties, annual calibration services, routine cleaning, scheduled maintenance. Customer care is the overarching principle — customers are buying peace of mind. Discoverability (site search, SEO) is critical for both parts and services.

## Working With This Schema

- **Classify first.** Before designing CMS fields, navigation, or page templates, classify every product into one of the six types. If something doesn't fit, that tension usually reveals a structural problem worth solving.
- **Respect independence.** Each product should be representable on its own, even if it's typically sold as part of a solution or alongside a flagship product.
- **Design relationships, not hierarchies.** Products relate to each other in multiple directions. An accessory might connect to three flagship products. A consumable might be shared across an entire product line. Avoid rigid parent-child trees.
- **Keep solutions flexible.** Solutions should be editable groupings, not hardcoded packages. The business will repackage them — the schema should make that easy.
- **Make everything quotable.** Even if a product isn't currently sold individually, build the schema so it could be. Business needs change faster than CMS architectures.
- **Let type inform UX.** Standard products and support products need strong search and filtering. Flagship products need brand storytelling. Consumables need reordering flows.

A thoughtfully structured product schema pays dividends far beyond organization. It extends the lifespan of your CMS and CRM investments, reduces technical debt, and helps your digital product catalog adapt to change, without costly overhauls, as your organization evolves.

When your products are well-classified, you can say yes to almost anything without breaking your system. New leadership wants to repackage products around a vertical market? That's just a new solution. Sales needs a dedicated landing page for a key account? Your flagship product template already supports it. Without that structure, every unexpected request becomes a hack, and templates are asked to do things they were never designed for. Good product classification puts marketing in position to play the good guy every time.

Start from the bottom up. Classify your individual purchasable products as standard, accessory, consumable, or support. Then identify your flagship products, which may represent a whole product line rather than a single SKU. Products that don't fit cleanly will surface disagreements about how they're sold and marketed, which is the right conversation for your team to have. Build your solutions last, since they're marketing groupings that reference the products you've already classified.

The difference comes down to marketing and presentation. A standard product typically uses a repeatable e-commerce template – the same layout across hundreds or thousands of SKUs. A flagship product is one deserving of a dedicated marketing experience, with room for interactive tools, videos, and brand storytelling. Where a standard product page is designed for checkout, a flagship product page often encompasses a range of models or trims, but focuses on what the product does and why it matters, rather than the specifics of the version you'll end up buying.

Not quite. A kit or bundle is a fixed grouping of products with its own SKU that lives in your catalog like any other purchasable item. A solution is a marketing concept. Both are collections of other products, but the parts of a repair kit rarely change, while a solution can be created whenever the need arises – for an industry-specific tradeshow, a seasonal campaign, or even a single high-value customer.

Not a specific CMS, but it does require a certain kind of CMS. This framework is fundamentally about how you structure your content model – custom fields, relationships between products, and reusable content types. This rules out marketing page builders like Squarespace or Wix, where each product is basically a standalone page. But it leaves plenty of capable systems to choose from. Craft CMS, Sanity, and Drupal are all examples of platforms that excel at structured content modeling.

Industry Roles

CMS

Colors