Skip to Main Content

| 8 minute read

B2B catalogs aren't D2C catalogs: a practitioner's guide to segment-aware commerce

written by Valerie Levanduski

Key Takeaways

  • The core difference: A D2C catalog is mostly a presentation problem, while a B2B catalog is mostly a governance problem: who can see which products, at which price, under which agreement.
  • Pricing drives catalog sprawl: In B2B, catalogs multiply because negotiated terms do, not because product counts grow. Decoupling price from product, stacking account-specific overrides on a base price book, and scheduling price changes keep that sprawl in check.
  • Segment by buyer vs. by context: B2B assortment and price visibility are gated by account, contract, or dealer tier. D2C catalogs vary by market, channel, or broad segment for mostly anonymous shoppers.
  • Data and buyers differ too: B2B product data runs deep (parts, models, accessories) and supports large repeat orders, multiple users, and quotes. D2C data runs wide, built for variants, bundles, and fast checkout.
  • Most businesses need both: The key design decision is the store boundary. Decide it using account sharing, order visibility, business-unit ownership, and whether product data is shared.

Not all catalogs are created equal

B2B commerce and D2C teams both say "catalog," but they're describing different problems. A D2C catalog is mostly a presentation problem: how to show the right products, prices, and bundles across channels and markets. A B2B catalog is mostly a governance problem: who is allowed to see what, at which price, under which agreement.

We see this play out across our sales and customer conversations, from manufacturers selling to tiered dealer networks to distributors that also run retail storefronts. Treating a B2B catalog like a bigger D2C catalog leads to the same failure every time: duplicated catalogs, price lists nobody can maintain, and workarounds that break the first time the business changes its terms.

This guide covers where the two models actually differ, what that means for how you structure products, pricing, and catalogs, and how to run both from one commerce stack without the complexity compounding.

1. In B2B, the catalog multiplies because pricing does

D2C pricing varies on a handful of dimensions: list price, sale price, maybe a member or staff tier. B2B pricing varies by relationship. Each account can carry negotiated terms, contract pricing, volume tiers, and channel-specific rates.

The numbers get large fast. One global equipment manufacturer we spoke with manages tens of thousands of price books, because historically each dealer could have individualized pricing. A building-materials distributor runs separate price books for list, wholesale, government, contractor, and distributor buyers. A hardware group in Latin America needs price books that change with contract status, plus quotes issued at full price with discounts applied at fulfillment for tax reasons.

In each case, the catalog sprawl starts with pricing and entitlement. Product count is rarely the driver. If your platform ties price to product, every new agreement means a new copy of the catalog.

2. Aim for fewer, layered price structures

When you evaluate a platform for this, ask how it helps you simplify pricing over time.

The manufacturer with tens of thousands of price books is consolidating them into a trade-terms model: one price list per market, with tiered discounts layered on top by dealer level. A book publisher described the same goal from the other side. It wants one global catalog, served differently by territory or business unit, instead of overlapping copies of the same data.

The structure that supports this has three parts:

  • Decouple price from product. Price books should live independently of products, so a price-only change is a price-only update. One prospect's current process re-sends the full catalog for every price change. That's the cost of coupling.
  • Layer overrides on a base price book. In Elastic Path, price book stacking lets an account-specific book hold only the overrides, with up to five books resolved in priority order. If a VIP or contract buyer gets special pricing on 20 of 100 products, you maintain 20 prices, and the other 80 fall back to list.
  • Make time a dimension. Contract prices change on renewal dates, and seasonal assortments change on calendar dates. Scheduling prices and catalog rules in advance beats a midnight publish.

Together, these let a B2B team shrink its pricing footprint as terms change, without rebuilding catalogs.

3. B2B segments by buyer; D2C segments by context

Both models segment the catalog, but they key off different things.

In B2B, assortment is gated by who the buyer is. One manufacturer we worked with shows their customer only the product line it actually buys, so its buyers don't search parts they'll never order. A power-equipment maker serves three dealer tiers with different assortments. Anonymous visitors often see no price at all until they log in.

In D2C, the shopper is usually anonymous, and the catalog varies by context instead: which market they're in, which channel they came from, or whether they belong to a broad segment like VIP or staff. A consumer brand rolling into new countries needs catalog segmentation by geography. A retailer may want app-only pricing to drive mobile adoption.

Dimension

B2B

D2C

What drives variation

Account, contract, dealer tier

Market, channel, broad segment

Assortment

Restricted per account or tier

Mostly shared, varies by market

Price visibility

Often gated behind login

Public list and sale prices

Number of catalogs

Can grow with accounts

Grows with markets and channels

The mechanism can be the same. Elastic Path catalog rules resolve which catalog a request gets based on account, account tag, channel, context tag, or date. What changes is which inputs your business relies on, and how many combinations you let accumulate.

4. B2B product data runs deep; D2C runs wide

B2B catalogs are dominated by relationships between products. One equipment manufacturer carries several hundred thousand SKUs, most of them spare parts. Its data model separates marketing products, product models, and article numbers. Technical documentation attaches at the model level, pricing always at the article level, and accessory and spare-part relationships can attach at any of the three. A building-products distributor told us technical specifications matter more than imagery for windows, doors, and chemicals.

D2C catalogs are dominated by presentation and combinations. A furniture retailer's sofa configurator, with over a thousand fabric options, created a new SKU for every configuration. A publisher wanted dynamic bundles that price components differently inside the bundle than outside it, to move slow inventory.

The practical implication: in B2B, design your hierarchy and relationship model first, then layer pricing at the level where the ERP prices. In D2C, design for variation, bundling, and merchandising flexibility, and assume the business will invent new product shapes. Flexible templates and attributes, which Elastic Path supports with multiple templates per product, matter in both cases for different reasons.

5. The catalog has to serve a different kind of buyer

B2B orders don't look like D2C orders. One dealer network we spoke with averages more than 30 line items per order, with occasional orders over 800 lines. B2B buyers reorder, buy on behalf of an organization, and often have a sales rep placing or adjusting orders for them.

That changes what the catalog needs to support at the point of purchase:

  • Multiple users per account, with roles that control who can see pricing, place orders, or approve them
  • Sales reps who can access several accounts and see each account's pricing and catalog
  • Purchase history on the product page, so a buyer can confirm what they ordered last time
  • Quotes, and split shipments to multiple locations from a single order

D2C buyers mostly need the opposite: fast discovery, clear promotions, and a checkout with as little friction as possible. A catalog built only for one of these buyers will underserve the other.

6. Most businesses need both, so decide where the boundary sits

Pure B2B or pure D2C is increasingly rare among the companies we talk to. A hardware group operates retail stores and a distribution business, and distribution is the larger one. A digital-products marketplace sells to consumers and companies from the same site but can't vary pricing by company on its current platform. Several manufacturers run B2B2C models, where the brand owns the master catalog and curates it for dealers who run their own storefronts.

That makes store structure the central design decision: how many stores you run, and what you share across them. In Elastic Path, products and pricing can live at the organization level and be shared to every store, while each store curates its own catalogs. Within one store, a D2C catalog and many B2B catalogs can serve the same storefront.

A few questions settle where the boundary belongs:

  • Should accounts be shared? If a buyer registered in one region shouldn't be able to log in to another, use separate stores.
  • Should orders be visible together? One store sees every order placed in it. If regional teams shouldn't wade through each other's orders, split them.
  • Is it one business unit or several? Separate operating units usually want separate stores. One team running several markets usually doesn't.
  • Is the product data the same? Shared products belong at the organization level. Genuinely different product lines can justify their own store.

A practitioner's checklist for segment-aware catalogs

Before you design or migrate a catalog that serves both B2B and D2C buyers, work through these:

  1. List every dimension your pricing varies on today, then mark which ones the business wants to keep.
  2. Count how many price lists exist only to hold a few overrides. Those are candidates for stacking.
  3. Decide which inputs choose a catalog: account, tier, market, channel, date. Keep the list short.
  4. Map your product relationships before your hierarchy: parts, accessories, models, variants.
  5. Confirm where the system of record prices each item, and price at that level.
  6. Decide which buyers see prices anonymously and which log in first.
  7. Draw the store boundary using account sharing, order visibility, and business-unit ownership.
  8. Plan for price-only and scheduled updates, so pricing changes don't trigger full catalog loads.

Segment-aware commerce means one set of product data serving every buyer correctly, with pricing and visibility layered on top. D2C teams get there by adding context. B2B teams get there by removing duplication. The right platform makes both of those routine work for the teams that run the catalog.

Get Started with Elastic Path

Schedule a demo to see how Elastic Path delivers unified commerce for leading global brands.