At a glance
Single source of truth for everything sold: offers, prices, rules and versions.
Key data
Receives from
- Product & marketing teams
Sends to
- CPQ
- Cart
- Rating
- Billing
- Channels
How it works
The main steps, end to end.
- 1Design the offer on reusable building blocks
- 2Configure prices, rules and eligibility
- 3Version and test the offer
- 4Publish to channels on the effective date
- 5Retire and migrate when the offer ends
Core Capabilities
What the Enterprise Product Catalog provides — offerings, pricing, discounting, versioning, lifecycle management and more
Product Offerings
- Defines all sellable products: plans, devices, accessories, add-ons, bundles
- Each offering has a lifecycle status: Active, Inactive, Retired
- Product characteristics stored: color, memory, brand, display, weight
- Category associations drive filter and navigation in self-care portals
- Supports product family grouping for related variant display
Pricing & Revenue Codes
- Stores recurring, one-time and usage-based prices per offering
- Multiple price entries per offering for date-range-based price transitions
- Revenue codes mapped per price entry for billing integration
- Supports condition set pricing (e.g. device tier-based warranty pricing)
- Tax category configured per price entry
Characteristic Filtering
- Exposes characteristic value counts for filter UI construction
- Filter by: brand, color, memory, OS, device type and custom attributes
- Category-scoped filtering returns counts only for relevant products
- Used by self-care, assisted and POS channel portals for offer discovery
Rule Management
- Configurable eligibility and compatibility rules per offering
- Rules engine evaluates plan-to-device, plan-to-add-on compatibility
- Channel-specific visibility rules — not all products shown in all channels
- Add-on eligibility rules: which add-ons are available on which plans
Product Registry
- Tracks offering versions and effective date ranges
- Supports product sunset: deactivation with migration path
- Product approval workflow: Draft → Review → Published → Retired
- Audit trail of product changes for regulatory compliance
Bundle Management
- Defines product bundles: plan + device + add-on composites
- Bundle pricing overrides individual component prices
- Bundle eligibility rules applied at CPQ configuration stage
- Supports partial bundle selection where components are individually optional
Storage & Persistence
How and where the Enterprise Product Catalog stores its data
Relational Database
- Product offering definitions and lifecycle state
- Pricing entries with date-range validity and revenue codes
- Characteristic definitions and permitted value sets
- Category hierarchy and offering-category associations
- Bundle compositions and pricing overrides
Document Data Store
- Eligibility and compatibility rule documents
- Offer relationship documents: upgrade/downgrade/cross-sell paths
- Channel visibility rules per offering
- Immutable version history records per offering change
Search Index
- Characteristic value count queries for filter panel construction
- Full catalog text search for offer discovery
- Category-scoped product listing queries
- Used by CPQ, self-care and assisted channel portals
Design Principles
Key architectural decisions behind the Enterprise Product Catalog
Single Catalog for All Channels
Every channel — self-care portal, assisted sales, in-store POS — reads from the same product catalog. There is no channel-specific product database. Channel visibility is controlled by catalog rules, not separate data silos.
Price History via Date Ranges
Each price entry has a start date and end date. A product can have multiple historical price entries in the catalog simultaneously. The correct price is selected at quote time based on the transaction date — supporting retroactive pricing corrections and future price changes.
Characteristic-first Design
Products are defined by their characteristics — not by flat attributes. This allows any characteristic (brand, color, memory) to be used for filtering, reporting and CPQ configuration without schema changes, making the catalog extensible for new product types.
Discounting
- Associates discount rules directly with product offerings in the catalog
- Discount types: percentage off recurring fee, fixed amount reduction, free trial period
- Validity window: discount applies only within configured start and end dates
- Eligibility conditions: new subscribers only, upgrade only, specific channel
- Stacking rules: which catalog-level discounts can combine with cart discounts
- Discount inheritance in bundles: component vs bundle-level discount resolution
- Promotional pricing flag: distinguishes introductory price from standard price
Lifecycle Management
- Draft — offering created, not yet visible to any channel
- In Review — offering pending approval from product or commercial team
- Published / Active — offering live and sellable across configured channels
- Deprecated — offering no longer sold to new subscribers but active for existing
- Retired — offering fully decommissioned; no new or existing subscribers
- Lifecycle transitions require authorised approver action — no self-approval
- Deprecation triggers migration path assignment for existing subscribers
- Retired offerings retained in catalog for historical reporting and billing
Versioning
- Every change to an offering creates a new immutable version record
- Version fields tracked: name, description, price, characteristics, rules, status
- Effective date range per version: which version was live when
- Version comparison: side-by-side diff between any two versions
- Rollback capability: revert offering to a previous version with approval
- Change author and timestamp recorded on every version
- Audit-safe: past versions cannot be deleted — retained for compliance
- Order and billing references to historic versions remain valid permanently
Offer Relationships
- Defines upgrade paths: which plans a subscriber can upgrade to from their current plan
- Downgrade paths: permitted plan downgrades with associated eligibility conditions
- Cross-sell relationships: which add-ons and devices are recommended with a given plan
- Requires / Conflicts relationships: mandatory or incompatible offering combinations
- Migration paths: where existing subscribers on deprecated offerings are guided
- Relationship direction: unidirectional vs bidirectional
- Surfaced in CPQ for guided selling and Order Capture for change order validation
Category Management
- Hierarchical category tree: top-level categories with nested sub-categories
- Category types: Smartphones, Tablets, Watches, Accessories, Plans, Add-ons
- Offering-to-category association: one offering can belong to multiple categories
- Category display order and weight for sort order in channel portals
- Category-level eligibility: restrict entire categories to specific channels or segments
- Category metadata: icon, description, promotional banner association
- Drives filter panel construction in self-care and assisted ordering portals
Characteristic Management
- Defines the full set of characteristics available across the catalog (Color, Memory, Brand, OS etc.)
- Characteristic value sets: permitted values per characteristic with display labels
- Value validation: prevents non-standard values being assigned to offerings
- Configurable: mandatory vs optional per product specification
- Localised labels: characteristic names and values in multiple languages
- Characteristic groups: organise attributes into logical display sections
- Custom characteristics: extendable for new product types without schema changes
Detect conflicting rules, prices or eligibility before an offer goes live.
Generative AI drafts offer descriptions and test scenarios from a product brief.
More in 30 AI & ML use cases and AIOps for BSS.