Every SaaS pricing decision — from initial packaging to mid-market expansion to enterprise customization — ultimately depends on how your product catalog is structured. A well-designed catalog makes pricing experimentation effortless. A poorly designed one turns every packaging change into an engineering project and every custom deal into a billing nightmare.
The Product Catalog Hierarchy
A flexible SaaS product catalog follows a four-level hierarchy that separates concerns and enables maximum pricing agility:
Level 1: Products
Products represent the highest-level units of your offering — the things customers think of when they describe what they're buying. "Analytics Platform," "Marketing Automation Suite," "Developer Tools." Products should map to how customers understand your offering, not how your engineering teams have organized their codebase.
Level 2: Plans
Plans represent the packaging of a product at different price points and feature levels. "Starter," "Professional," "Enterprise." Each plan defines which features are included, what usage limits apply, and what the base pricing structure looks like. Plans should be designed to create a clear upgrade path that aligns with customer value realization.
Level 3: Entitlements
Entitlements are the specific capabilities and limits that a plan grants. "Up to 10 users," "500 API calls per day," "Advanced reporting enabled," "Custom SSO." Entitlements should be granular enough to support flexible packaging but not so granular that plan comparison becomes overwhelming.
Level 4: Price Points
Price points define the monetary value attached to each plan, including the pricing model (flat fee, per-seat, usage-based, tiered), billing frequency (monthly, annual, multi-year), and currency-specific pricing. Separating price points from plans allows you to experiment with pricing without restructuring your entire catalog.
Common Catalog Anti-Patterns
The Monolith Catalog — Everything is one product with dozens of plans, each containing a unique combination of features. This becomes unmanageable as your offering grows and makes it impossible to sell products independently.
The SKU Explosion — Every possible combination of features, usage tiers, and add-ons gets its own SKU. A catalog with 500 SKUs is a billing nightmare waiting to happen.
The Engineering-Driven Structure — Products and features map to internal microservices rather than customer-facing value propositions. Customers shouldn't need to understand your architecture to understand your pricing.
The Hardcoded Prices — Pricing baked into catalog definitions rather than maintained as a separate, configurable layer. Every price change requires a catalog update, making experimentation slow and risky.
Building for Evolution
The most important principle for product catalog design is anticipating change. Your pricing will evolve. Your packaging will evolve. Your go-to-market strategy will evolve. A catalog that's easy to restructure is infinitely more valuable than one that's perfectly optimized for today's pricing model.
Design your catalog with separation of concerns: products represent value, plans represent packaging, entitlements represent capabilities, and price points represent monetization. When any of these dimensions needs to change, the others remain stable.
PeakCommerce's Commerce Hub provides a catalog management system built on these principles, with version-controlled catalog changes, impact analysis for pricing modifications, and automated migration tooling for existing subscriptions when catalog structures evolve.