Revenue by Product

Goal of the analysis:

The objective is to quantify and understand revenue contribution and growth by individual product (and product hierarchy) to inform portfolio strategy, pricing, resourcing, and roadmap decisions. Executives use this analysis to identify the core revenue engines, diagnose underperformers, manage concentration risk, track new product traction, and align investments with market opportunity. A robust view of revenue by product underpins decisions on SKU rationalization, channel focus, supply allocation, and product lifecycle management, and is foundational for quarterly business reviews and annual planning.

Data required:

• Transactional sales and invoicing data:
  • Invoice line items or sales order lines with product SKU, quantity, net unit price, discounts, taxes (separately), currency, invoice date, and invoice status.
  • Returns/credits and refund lines with references to original invoices.
  • For subscriptions/usage: recognized revenue by product and period, invoice schedules, and deferred revenue movements.
  • Systems: ERP (e.g., SAP, Oracle), billing (e.g., Zuora), ecommerce/PoS, CRM opportunity close data (e.g., Salesforce) for pipeline context.
• Product master and hierarchy:
  • SKU-to-product mapping, product families, categories, lifecycle stage (launch, growth, mature, end-of-life).
  • Bundle/kit definitions and allocation rules for revenue split across components.
  • Attributes: version, feature set, unit of measure.
  • Systems: PIM/PLM, ERP item master.
• Pricing and discounting data:
  • List price, contracted price, promotions, rebates, and off-invoice/on-invoice discounts by product and customer/segment.
  • Rebate accruals and settlement schedules (to compute net revenue).
• Channel, geography, and customer context:
  • Sales channel (direct, partner, retail, ecommerce), region/country, customer segment/industry, key accounts.
  • For partners: sell-in vs sell-through where available.
• Finance and accounting references:
  • Revenue recognition policy (ASC 606/IFRS 15), chart of accounts mapping, fiscal calendar, and FX rates for currency normalization.
  • General Ledger revenue totals for reconciliation/tie-out.
• Historical and benchmark data:
  • Multiple years of history to assess trends and seasonality.
  • Market size/growth estimates for context (external research) and internal targets/budgets.

Detailed step-by-step instruction on how to conduct the analysis:

1. Define scope and metric. Confirm whether the analysis uses gross sales, net revenue (after discounts and rebates), or GAAP/IFRS recognized revenue. Define the time window (monthly/quarterly) and whether to include returns and credits in-period or as adjustments to original periods.
2. Extract source data. Pull invoice/sales line items from ERP/billing; return/credit memos; product master; pricing/discount tables; channel and geography dimensions; FX rates. Typical tools: SQL/ETL, data lake/warehouse (Snowflake/BigQuery/Redshift), BI (Power BI/Tableau/Looker).
3. Clean and standardize. Deduplicate invoices, filter canceled/draft documents, standardize product IDs and units, ensure dates align to fiscal calendar, and tag lifecycle stage. Normalize currencies to a reporting currency using period-average or transaction-date FX rates as per policy.
4. Map product hierarchy. Join each SKU to product, family, and category. Validate that every line item maps; fix or flag orphans for data quality remediation.
5. Adjust for discounts, rebates, taxes, and returns. Compute net revenue per line:
   • Net unit price = list price − on-invoice discount − promotion.
   • Apply rebate accruals and off-invoice programs to derive net revenue (exclude taxes and shipping if policy dictates).
   • Subtract returns/credits; if returns are booked in a later period, decide whether to back-cast or present separately.
6. Handle bundles and allocations. Where products are sold in bundles, allocate revenue to components using defined rules (e.g., relative standalone selling price). For subscriptions with multi-element arrangements, use recognized revenue schedules by product.
7. Aggregate revenue by product and period. Create tables keyed by product, month/quarter, with measures: net revenue, quantity, ASP (average selling price), number of invoices/customers, returns rate.
8. Segment the view. Produce cuts by:
   • Channel (direct/indirect/ecommerce/retail), geography (region/country), customer segment/industry, and lifecycle stage.
   • New vs existing products (e.g., launched in last 12–24 months).
9. Compute growth and contribution metrics.
   • YoY and QoQ growth by product.
   • Revenue mix (% of total) and cumulative mix for Pareto analysis.
   • Optional: gross margin by product if COGS data is available, to contextualize revenue with profitability.
10. Run price-volume-mix decomposition. Break revenue change vs prior period into:
    • Volume effect (units change at constant price).
    • Price effect (ASP change at constant volume).
    • Mix effect (shift in product mix).
11. Assess seasonality and trend. Plot 24–36 months of revenue by product to identify seasonal patterns, cyclicality, and structural inflections (launches, promotions, supply constraints).
12. Identify concentration and long tail. Create a Pareto curve (cumulative revenue vs ranked products) to quantify concentration risk and the size of the tail; track how this shifts over time.
13. Investigate anomalies and cannibalization. Flag products with sudden revenue drops/spikes; check correlations and overlapping launches to infer potential cannibalization or substitution.
14. Reconcile to the GL. Tie aggregated revenue totals to the General Ledger by period and entity, documenting any timing differences or exclusion rules.
15. Synthesize insights and implications. Summarize top drivers, at-risk products, new product traction, channel/geography dynamics, and recommended actions. Validate hypotheses with sales/product leaders.

Format of the output of analysis:

• Executive summary slide with key insights, top 10 products by revenue and growth, and 2–3 decisions recommended.
• Revenue by product table with YoY/QoQ growth, mix %, returns rate, and optional gross margin.
• Pareto chart showing cumulative revenue contribution across products; treemap for portfolio mix visualization.
• Time-series line charts of revenue by top products; seasonal heatmap by month and product.
• Price-volume-mix waterfall showing drivers of change vs prior period/budget.
• Segmented views: channel, geography, and customer segment comparisons; bubble chart of revenue vs growth vs margin.
• Reconciliation appendix tying totals to GL and documenting methodologies (e.g., bundle allocations).

How to interpret results:

• High revenue, high growth: Core engines; sustain investment, protect supply, and consider price optimization.
• High revenue, low/negative growth: Potential maturity or competitive pressure; review pricing, innovation roadmap, and channel support.
• Low revenue, high growth: Emerging winners; ensure capacity, marketing support, and accelerate roadmap.
• Low revenue, low growth (long tail): Candidates for rationalization, bundling, or niche focus; confirm strategic role (e.g., entry product, attach driver).
• Concentration: A steep Pareto curve indicates dependency on few products; assess risk and develop diversification or hedge plans.
• Discount and return patterns: High discounting may mask demand issues or erode price; elevated returns may indicate quality/fit issues.
• Channel/geography differences: Strong variance can signal localization gaps, channel conflict, or untapped opportunity.
• Trend and seasonality: Stable or improving trends are healthy; volatility without clear drivers warrants deeper investigation.
• Benchmark lens: Compare to internal top quartile products and market growth; outperforming market indicates share gain, underperforming suggests competitiveness or execution issues.

Steps a company can take to improve on this measure:

• Portfolio strategy and lifecycle management:
  • Double down on high-growth products with capacity, channel priority, and roadmap acceleration.
  • Rationalize underperforming SKUs; consolidate variants and simplify assortments.
  • Stage-gate investments for new products; set explicit revenue milestones and kill criteria.
• Pricing and promotion:
  • Optimize list and net prices using elasticity insights; reduce unnecessary discounting.
  • Design targeted promotions for specific segments/channels; A/B test offers.
  • Introduce good-better-best structures and value-based bundles to lift mix.
• Go-to-market and channel execution:
  • Rebalance sales incentives toward strategic products; refine partner programs and MDF.
  • Improve availability and merchandising in high-potential geographies/channels.
  • Drive attach/cross-sell motions from anchor products; use playbooks and guided selling.
• Product and experience:
  • Address quality issues driving returns; enhance features aligned to high-value segments.
  • Localize offerings and content where regional adoption lags.
  • Accelerate replacements for aging products to preempt decline and cannibalization.
• Data, systems, and governance:
  • Establish a single product hierarchy and master data governance.
  • Automate revenue by product dashboards with reconciled data and clear definitions.
  • Institutionalize price-volume-mix and Pareto reviews in quarterly business reviews.
• Scenario guidance:
  • If Product A has high revenue but declining growth and rising discount rates, run a pricing/packaging refresh and invest in differentiation.
  • If long-tail SKUs consume capacity with minimal revenue, rationalize and redirect supply to high-demand products.
  • If new products show strong early growth but stockouts, prioritize supply allocation and expedite certifications.

Benchmark comparisons:

General benchmarks:

• Portfolio concentration often follows a Pareto pattern, where a relatively small share of products contributes a large share of revenue; monitor the top-product share and its movement over time.
• Healthy product portfolios typically show a pipeline of new products contributing a meaningful minority of revenue within 1–3 years of launch; set internal targets based on strategy and category dynamics.
• Compare product growth to overall company growth and to external market growth to infer share changes.

Segment- or industry-specific benchmarks:

• SaaS/Subscriptions: Track revenue by product modules alongside ARR/MRR; expect new modules to scale over 4–8 quarters with expansion revenue from existing customers.
• Consumer goods/retail: Seasonal products should be evaluated on like-for-like seasonal windows; measure contribution from new SKUs launched in the last 12–24 months.
• Industrials/high tech: Version transitions can cause temporary dips in legacy revenue; benchmark ramp curves for successor products.
• Channel-led businesses: Benchmark sell-in vs sell-through where available to avoid overstating product revenue on channel stuffing.

If robust external benchmarks are unavailable, build internal ones: compare products within a family, track top quartile products on growth and mix, set targets relative to market growth, and evaluate new product ramps against prior successful launches. Maintain a rolling 24–36 month view to establish seasonality-aware baselines.