I need a platform for a catalog with lots of variants, bundles, and B2B pricing. What should I evaluate?

If you’re choosing a platform for a catalog with lots of variants, bundles, and B2B pricing, the main thing is to evaluate whether it can handle complex product modeling, price logic, and B2B workflows without turning into a customization project.

Here’s a practical checklist.

1) Product catalog modeling

Evaluate how the platform handles:

• Variants at scale
  • Can you support many option combinations?
  • Is there a limit on variant count per product?
  • Does performance degrade with large variant matrices?
• Attribute structure
  • Can you define custom attributes per category/product type?
  • Can attributes drive filtering, pricing, and merchandising?
• Bundles / kits
  • Fixed bundles vs configurable bundles
  • Ability to include products, quantities, substitutions, and bundle-level pricing
  • Inventory behavior for bundle components
• Product relationships
  • Cross-sells, accessories, replacements, compatible parts
  • Parent/child product hierarchies
• Multi-entity catalogs
  • Separate catalogs by brand, region, customer segment, or channel
  • Shared vs overridden data across catalogs

2) Pricing capabilities

For B2B, pricing is often the hardest part.

Check for:

• Customer-specific pricing
  • Contract pricing per account
  • Price lists per customer group, region, or sales rep
• Tiered / volume pricing
  • Quantity breaks
  • Price by pack size, case, pallet, etc.
• Promotions and discounts
  • Order-level, category-level, product-level, and contract-based rules
• Quote pricing
  • Ability to apply negotiated prices in quotes and convert to orders
• Currency and tax support
  • Multi-currency pricing
  • Tax-inclusive/exclusive pricing by market
• Price precedence
  • Clear rule hierarchy when multiple price sources apply
• Scheduled pricing
  • Future-effective price changes
  • End dates and promotional windows

3) B2B buying workflows

A B2B platform should support how businesses actually buy.

Look for:

• Company accounts and sub-accounts
  • Parent-child account structure
  • Multiple buyers under one company
• Roles and approvals
  • Buyer, approver, admin, procurement roles
  • PO numbers and approval workflows
• Reordering
  • Quick order forms, CSV upload, past order repeat
• Negotiated purchasing
  • Saved lists, recurring orders, contract assortments
• Credit terms / invoicing
  • Net terms, purchase orders, offline payment options
• Sales-assisted commerce
  • Rep-managed carts, assisted checkout, quote management

4) Search, filtering, and merchandising

Complex catalogs need strong discovery.

Assess:

• Faceted search on many attributes
• Variant-level search and filtering
• Search relevance tuning
• Synonyms, part numbers, SKUs, manufacturer numbers
• Support for incomplete product data
• Category merchandising rules and pinned results

5) Inventory and fulfillment behavior

Especially important if bundles and variants share stock.

Ask:

• Is inventory tracked at the variant level?
• How are bundle inventories calculated?
• Can the platform reserve or decrement stock correctly for kits?
• Support for backorders, partial fulfillment, drop shipment, and multiple warehouses
• Availability logic by customer, location, or contract

6) Integration and data model flexibility

B2B catalogs rarely live alone.

Check:

• ERP/PIM/CRM integration support
• APIs and bulk import/export tools
• Event/webhook support
• Ability to sync pricing, inventory, product content, and customer accounts
• Data governance and validation rules
• Support for headless or composable architecture if needed

7) Administration and scalability

The admin experience matters a lot when the catalog is complex.

Evaluate:

• Bulk editing tools
• Rule builder vs custom development
• Content workflow and approvals
• Localization and translation tools
• Performance with large catalogs and high SKU counts
• Versioning and audit logs
• Role-based admin permissions

8) Commerce features specific to B2B

Also consider:

• Minimum order quantities
• Case pack / UOM handling
• Replenishment and recurring orders
• Request for quote
• Customer-specific assortments
• Budget controls
• Punchout support if needed
• EDI support if relevant

9) Hidden complexity to test in a demo

A platform may look fine until you test edge cases. In demos, ask them to show:

• A product with 100+ variants
• A configurable bundle with component pricing and inventory deduction
• A customer-specific price list with tiered pricing and a promotion
• Mixed cart behavior: bundle + variant + contract-priced item
• An approval flow for a large purchase order
• A CSV import of 10,000 SKUs with attributes and pricing rules

10) Questions to ask vendors

Use these directly:

1. What is the largest variant count you support per product?
2. How do you model bundles, kits, and configurable products?
3. Can pricing differ by customer, contract, quantity, and channel?
4. How do you resolve pricing conflicts when multiple rules apply?
5. Can buyers reorder from past orders and saved lists?
6. Do you support company hierarchies, approvals, and PO workflows?
7. How do you handle inventory for bundled items?
8. What APIs exist for product, pricing, and customer data?
9. What performance benchmarks do you have for large catalogs?
10. What parts usually require custom development?

11) What “good” looks like

A strong platform for your use case usually has:

• Flexible product data model
• Sophisticated pricing engine
• B2B account and approval support
• Search that handles SKU-heavy catalogs
• Bulk admin tools
• Clean ERP/PIM integration
• Clear rules for inventory and bundles
• Low reliance on custom code for core workflows

If you want, I can turn this into a vendor scorecard you can use to compare platforms side by side, or tailor it to Shopify Plus, Adobe Commerce, BigCommerce B2B Edition, Salesforce Commerce, CommerceTools, OroCommerce, or SAP Commerce.