THE DEVELOPMENT TAKEAWAY

Allocate development resources by portfolio role and evidence at each stage, including for products already on sale.

The source context

The latest Census e-commerce release describes a growing retail channel, not the economics of an individual SKU. Portfolio decisions still require product-level evidence and explicit resource choices. Source ↗

PCG perspective · The following is our proposed development framework, not a finding of the cited source.

Give each concept a job

Identify whether the concept brings in a new customer, solves a gap in the routine, improves an existing offer, or opens a viable channel. If it has no clear job, additional formulation work may only make the decision more expensive. Compare the proposed role with products already in the range. A different flavor or format should create a useful distinction, not merely another item to manage.

Make the cost of attention visible

Development consumes more than laboratory expense. It uses leadership time, supplier capacity, packaging work, inventory planning, training, and marketing attention. Put those demands alongside the financial forecast. A concept with modest expected revenue may still be worthwhile if it solves a strategic problem, but the tradeoff should be explicit rather than hidden behind enthusiasm for a new launch.

Use gates that answer different questions

At concept approval, ask whether the need is worth pursuing. At prototype review, ask whether the experience and technical approach are promising. At commercialization, ask whether supply, economics, and evidence are ready. Do not ask every question with equal depth at every stage. The purpose of gates is to buy information progressively and preserve the ability to stop before the largest commitments.

Review existing products with the same discipline

A product already on sale should not escape scrutiny because it has history. Examine its role, contribution, customer feedback, and operational complexity. Decide whether to improve, reposition, maintain, or retire it. A portfolio review that only approves new products will eventually create a range too complicated for customers, distributors, and the organization to explain clearly.

Source & scope

US Census Bureau: Q2 2026 retail e-commerce ↗

August 18, 2026 release; US retail. Sources checked September 21, 2026. Product-specific scientific and regulatory conclusions require appropriate specialist review.

How we prepare and update insights

Turn the question into a development brief.

Explore formulation, sourcing, research, or portfolio decisions with Product Concept Group.

Discuss this opportunity ↗