B2B Customer-Specific Catalogs: How to Show Each Account the Right Products
How to build B2B customer-specific catalogs: account assortments, contract prices, availability, entitlements, segmentation, search and architecture.
Quick answer
Customer-specific catalogs show each B2B account the products, prices and availability it is entitled to. Assign catalogs and price lists to companies, locations or segments; define precedence when several apply; resolve entitlements in one service; and apply them everywhere products appear: navigation, search, product pages, cart, quick order, punchout and APIs. Manage complexity with base catalogs, segments, inheritance, start and end dates, clear ownership and regular clean-up.
Where This Fits
Catalog structure is covered in B2B product catalogs and pricing display in B2B pricing. Product data foundations are in PIM and product data architecture. Accounts are covered in B2B account management.
What a Customer Catalog Contains
| Element | Examples |
|---|---|
| Assortment | Approved products, private-label items, regional ranges |
| Prices | Contract prices, tiered and volume prices, currency |
| Order rules | Minimums, pack sizes, allowed units |
| Availability | Allocated stock, preferred warehouse, lead times |
| Content | Customer part numbers, specific documents |
| Dates | Contract start and end |
Assignment and Precedence
Catalogs can be assigned at several levels. A common model: a base catalog for all trade customers, segment catalogs (by industry or region), company-specific additions and location-specific restrictions. Define precedence explicitly, such as most specific wins for prices and intersection for restrictions, and document it so sales and support teams understand what buyers see.
Segmentation
Not every customer needs a unique catalog. Segments (dealer tiers, industries, regions) cover most cases with fewer catalogs to maintain. Reserve company-specific catalogs for contract customers with genuinely different assortments or prices.
Architecture
Resolve entitlements in one place: the commerce platform's B2B features or a dedicated pricing and catalog service. Given a user and location, it returns the allowed products, prices and rules. Every channel calls it or uses its precomputed results, so the storefront, search, cart, quick order, punchout and APIs never disagree.
Managing contract catalogs by hand?
ZSpace can design an entitlement model and service that applies customer catalogs and prices consistently across every channel.
Search and Navigation
Search is where customer catalogs often leak. Either index products per catalog, or index once and filter by entitlement at query time, and always show the buyer's price. Navigation should hide empty categories for the buyer. Customer part numbers should be searchable. See B2B search.
Product Pages, Cart and Quick Order
Product pages show the buyer's price, units and order rules. The cart revalidates entitlements and prices at checkout, especially for saved carts and lists created before a contract changed. Quick order and CSV upload must reject products outside the catalog with a clear reason. See B2B quick order.
Data Sources
Contract assortments and prices often originate in the ERP or a CPQ system. Sync them on change, with start and end dates, and alert when a contract is about to expire. Product content comes from the PIM; customer-specific part numbers and documents need a home too. See ERP integration.
Governance
- Named owner for each catalog and price list
- Base catalog plus segments before company-specific catalogs
- Start and end dates on contract catalogs
- Regular review of unused or overlapping catalogs
- Preview: see the store as a given customer
- Audit of changes
Worked Example
An illustrative scenario, not a client case: an industrial supplier manages hundreds of company-specific catalogs, many nearly identical. Search sometimes shows restricted products to the wrong customers. The team introduces a base trade catalog, a few segment catalogs and company-specific additions, resolves entitlements in one service and filters search at query time. Staff can preview the store as any customer, and the number of catalogs to maintain falls sharply.
Common Mistakes
- Restricted products visible in search or orderable via quick order
- Saved carts with expired contract prices
- A unique catalog for every customer
- Precedence rules nobody can explain
- APIs and punchout ignoring entitlements
- No way for staff to preview a customer's view
Ready to give every account the right catalog?
Talk to ZSpace about B2B catalog and pricing architecture, Shopify B2B catalogs and contract data automation.
Conclusion
Customer-specific catalogs work when entitlements are resolved once and applied everywhere, segments keep catalogs manageable and contract data stays in sync. Related: PIM, product data architecture and B2B platform architecture.
Common questions
A set of products, prices and rules assigned to a particular B2B customer, group or location, so each buyer sees only what they are allowed and agreed to buy, at their prices.