BSS/OSS Academy
πŸ“
Section 2.1

Product Offering vs Specification

The difference between what you sell (Offering) and what it is (Specification), and why both exist.

Every product in a catalog-driven architecture has two representations: the Product Offering (what you sell) and the Product Specification (what it is). The same underlying product can be sold in multiple ways β€” different names, prices, channels β€” all pointing to the same specification underneath.

Product Offering vs Product Specification β€” many offerings can reference one specification

Offerings

SuperFibre 100 Home

Product Offering

SuperFibre 200 Home

Product Offering

Business Fibre 200

Product Offering

references
Specification

Fixed Broadband Access

Product Specification

downloadSpeeduploadSpeeddataQuota
realised by
Services

CFS: Internet Access

Customer Facing Service

CFS: WiFi Management

Customer Facing Service

Figure 2.1 β€” Multiple offerings reference the same specification
Product Offering (PO)
What you sell. Name, pricing, channel, eligibility, bundling. Owned by Product Management β€” high change velocity.
Product Specification (PS)
What it is. Characteristics, CFS linkage, composition rules. Owned by Product Architecture β€” low change velocity.

The relationship is many-to-one: multiple offerings reference the same specification. In bundles, a single offering can reference multiple specifications. This separation means product managers can launch new offerings without technical changes, and spec changes propagate to all referencing offerings automatically.

Bundles
A Bundle Product Offering groups multiple offerings together β€” e.g. "Home Triple Play" (Internet + TV + Voice). Each component references its own specification. Components can be mandatory, optional, or part of a choice group (pick 1 of N).

Key Takeaways

  • Product Offering = commercial wrapper (name, price, channel)
  • Product Specification = structural definition (characteristics, CFS linkage)
  • Multiple offerings can reference the same specification β€” enabling reuse
  • Separating them enables independent lifecycle management