GUIDE / STRATEGY / 02

How to Build a Private Label Product Range

In this articleA good range is not a collection of products.Start with the customer journeyProduct architectureGive every product a role.Build the system, not just the SKU listBrand ABrand BStart with the launch rangeDo not try to launch everything at once.The three-stage range model1. LAUNCH RANGE2. PHASE 23. FUTURE DEVELOPMENTExample: a focused launch rangeAvoid duplicate productsMore choice can create less clarity.Build around customer levelsCONSUMERENTHUSIASTPROFESSIONALBuild around price architectureNot every product should sit at the same price level.Define the hero products earlyWhat should the brand be known for?Use different development routes within one rangeHERO PRODUCTSCORE PRODUCTSSUPPORT PRODUCTSExampleRange consistency mattersProducts should feel like they belong together.Think about bundles from the beginningWASH KITCOATING PREP KITMAINTENANCE KITThink about trainingThink about production complexityPackaging architectureBuild a system.Pack sizesThink about concentrationBuild for the sales channelE-COMMERCERETAILPROFESSIONAL DETAILINGDISTRIBUTIONOEM / AUTOMOTIVEInternational ranges need disciplineNaming architectureProduct names should help customers navigate.Avoid building around competitor cataloguesUse sales data to guide Phase 2When to discontinue a productA practical range-planning framework1. ROLE2. USER3. PROBLEM4. DIFFERENTIATION5. DEVELOPMENT ROUTE6. VOLUME7. MARGIN8. PACKAGING9. LAUNCH PRIORITY10. CONNECTIONExample range-planning tableThe key principleThe Infinitec approachPlanning a new range?

A good range is not a collection of products.

One of the most common private-label mistakes is starting with a product list.

A shampoo.

A wheel cleaner.

A coating.

An interior cleaner.

A polish.

A glass cleaner.

Ten products can quickly become twenty.

But a large range is not automatically a good range.

A strong product portfolio should have a clear structure.

Each product should have a reason to exist.

The customer should understand how the products fit together.

And the range should be commercially manageable to produce, stock, launch and grow.

The objective is not to launch as many SKUs as possible.

It is to build the right range.

Start with the customer journey

Before deciding which products to develop, map the way your customer actually cares for the vehicle.

A typical exterior workflow might look like:

WASH

↓

DECONTAMINATION

↓

CORRECTION

↓

PREPARATION

↓

PROTECTION

↓

MAINTENANCE

That immediately gives the range structure.

Instead of asking:

Which products could we sell?

ask:

Which stages of the customer journey should our brand own?

That is a much better starting point.

Product architecture

Give every product a role.

A product range can usually be divided into several functional groups.

ENTRY PRODUCTS

Products customers buy frequently or use regularly.

Examples:

  • shampoo

  • quick detailer

  • glass cleaner

  • interior cleaner

These products create repeat purchases and frequent brand interaction.

CORE PRODUCTS

Products central to the brand's proposition.

Examples:

  • wheel cleaner

  • APC

  • spray sealant

  • polish

These often define how customers experience the range.

HERO PRODUCTS

Products that demonstrate technical differentiation.

Examples:

  • ceramic coating

  • specialist protection system

  • advanced polish

  • unique cleaning technology

These products may not always generate the highest unit volume, but they can shape perception of the entire brand.

SUPPORT PRODUCTS

Products that complete a workflow.

Examples:

  • panel wipe

  • clay lubricant

  • applicator lubricant

  • maintenance spray

These may not need the same development intensity as hero products, but they make the overall range more coherent.

Build the system, not just the SKU list

Consider two brands.

Brand A

Offers:

  • ceramic coating

  • shampoo

  • glass cleaner

  • leather cleaner

  • compound

  • interior dressing

  • wheel cleaner

  • wax

  • APC

All individually good products.

But there is no obvious structure.

Brand B

Builds around a clear workflow:

CLEAN

Pre-wash
Shampoo
Wheel cleaner

PREPARE

Decontamination
Compound
Polish
Panel wipe

PROTECT

Ceramic coating
Spray protection

MAINTAIN

Maintenance shampoo
Detail spray

The second range is easier to:

  • understand

  • explain

  • merchandise

  • train

  • market

  • bundle

  • expand

The chemistry may be equally good in both examples.

The difference is architecture.

Start with the launch range

Do not try to launch everything at once.

A common early-stage mistake is overbuilding the portfolio.

A company may approach development with a wish list of:

20 products.

15 fragrances.

Three pack sizes each.

Multiple languages.

Several different triggers.

From a development perspective, that may be possible.

Commercially, it may be a poor decision.

Every additional SKU creates complexity in:

  • development

  • packaging

  • regulatory work

  • artwork

  • labels

  • purchasing

  • production

  • inventory

  • forecasting

  • warehousing

  • marketing

A smaller launch range usually allows better focus.

The three-stage range model

We recommend thinking in three phases.

1. LAUNCH RANGE

The minimum coherent range required to enter the market properly.

These products should:

  • represent the brand clearly

  • cover the most important customer needs

  • be commercially viable

  • be ready to support each other

2. PHASE 2

Products that complete or strengthen the initial range.

These should ideally be based on:

  • customer feedback

  • sales performance

  • channel requirements

  • distributor requests

  • gaps identified after launch

3. FUTURE DEVELOPMENT

Products that become relevant as the brand grows.

Examples might include:

  • specialist variants

  • professional-only products

  • concentrates

  • new protection technologies

  • alternative pack sizes

  • products for additional markets

This makes growth deliberate rather than reactive.

Example: a focused launch range

Suppose a new premium detailing brand wants to launch internationally.

Instead of starting with 18 products, it might begin with:

WASH

  1. Maintenance Shampoo

  2. Wheel Cleaner

PREPARE

  1. Panel Preparation Spray

  2. One-Step Polish

PROTECT

  1. Ceramic Coating

  2. Spray Sealant

MAINTAIN

  1. Quick Detailer

  2. Interior Cleaner

That is already enough to create a meaningful brand ecosystem.

Phase 2 could then add:

  • APC

  • glass cleaner

  • iron remover

  • tyre dressing

  • leather care

  • compound

The range grows with evidence rather than assumption.

Avoid duplicate products

More choice can create less clarity.

Brands sometimes develop several products that solve almost the same problem.

For example:

  • detail spray

  • spray wax

  • ceramic detailer

  • drying aid

  • maintenance sealant

  • quick protection spray

All may have technically valid differences.

But if customers cannot understand those differences quickly, the range becomes harder to sell.

Before adding an SKU, ask:

Does it solve a clearly different problem?

Does it serve a different user?

Does it create a different performance level?

Does it support a different price point?

Does it fill a real gap?

If the answer is no, the product may create unnecessary complexity.

Build around customer levels

Another useful range architecture is to separate products by user type.

For example:

CONSUMER

Easy application

High forgiveness

Strong visual results

Simple instructions

ENTHUSIAST

More performance

Greater control

More specialist applications

PROFESSIONAL

Maximum efficiency

Concentrated chemistry

Process optimization

Technical application requirements

A product designed for a professional detailer may not be the best product for a retail consumer.

The intended user should influence formulation decisions.

Build around price architecture

Not every product should sit at the same price level.

A range can also contain clear price tiers.

For example:

ENTRY

Accessible, high-frequency products.

CORE

Main commercial range.

PREMIUM

Higher performance or more specialist chemistry.

HERO

Technical flagship products.

This can create a natural upgrade path.

But the differences should be real.

Artificially creating “Premium” and “Pro” versions without meaningful distinction usually weakens the brand.

Define the hero products early

What should the brand be known for?

Every serious range should have a small number of products that carry more strategic importance than the rest.

These are the products where greater development effort may make sense.

For example:

A brand may want to be known for:

  • ceramic protection

  • wheel chemistry

  • polishing

  • ultra-safe maintenance

  • professional efficiency

That should influence development priorities.

If ceramic coatings are central to the brand, it may make sense to invest heavily in differentiation there.

The glass cleaner probably does not need the same development budget.

Use different development routes within one range

A strong range does not require every SKU to be custom-developed from zero.

That can waste time and money.

A more intelligent structure might be:

HERO PRODUCTS

Bespoke development

CORE PRODUCTS

Customized technology

SUPPORT PRODUCTS

Proven platforms

This allows the brand to concentrate differentiation where it matters most.

Example

A premium brand launches eight products.

BESPOKE

Ceramic coating

Spray protection

CUSTOMIZED

Shampoo

Wheel cleaner

Polish

PROVEN PLATFORM

Glass cleaner

Panel wipe

Interior cleaner

The range can still feel completely coherent.

The key is consistent:

  • positioning

  • fragrance strategy

  • naming

  • packaging

  • application philosophy

  • performance expectations

Range consistency matters

Products should feel like they belong together.

Consistency can be created through more than graphic design.

Consider:

APPLICATION PHILOSOPHY

Are products designed to be fast and simple?

Or highly technical and specialist?

FRAGRANCE

Is there a consistent fragrance family?

Or deliberately different scents by category?

APPEARANCE

Are liquids generally clear and technical?

Bright and lifestyle-driven?

Minimalist?

PACKAGING

Do bottle shapes, triggers and closures create a coherent physical system?

INSTRUCTIONS

Are application instructions consistent in style and level of detail?

PERFORMANCE

Does the customer know what level of product quality to expect throughout the range?

A consistent experience strengthens the brand even where formulations are technically unrelated.

Think about bundles from the beginning

Range architecture should also consider how products will be sold together.

For example:

WASH KIT

Shampoo
Wheel Cleaner
Drying Aid

COATING PREP KIT

Polish
Panel Wipe
Ceramic Coating

MAINTENANCE KIT

Maintenance Shampoo
Detailer
Glass Cleaner

Bundles are easier to create when the range was designed as a system.

Think about training

A coherent product range is also easier for:

  • sales staff

  • distributors

  • detailers

  • retailers

  • content teams

to understand.

If every product has a clearly defined role, training becomes simpler.

That matters particularly when selling internationally.

A distributor should be able to understand:

  • what the product does

  • who it is for

  • how it differs from another product

  • when to recommend it

without needing a chemist on every sales call.

Think about production complexity

Product architecture should not ignore manufacturing reality.

Every SKU can introduce:

  • another formula

  • another raw material combination

  • another bottle

  • another closure

  • another label

  • another carton

  • another forecast

  • another production setup

Sometimes two commercially different products can share:

  • bottle families

  • closures

  • triggers

  • carton dimensions

  • label sizes

  • raw materials

without becoming identical.

Smart standardization can lower complexity without reducing brand differentiation.

Packaging architecture

Build a system.

Instead of choosing packaging independently for each SKU, consider the complete range.

Potentially standardize:

  • bottle families

  • trigger types

  • closures

  • label dimensions

  • carton sizes

Then differentiate through:

  • colour

  • label design

  • category coding

  • finish

  • pack size

This can improve:

  • purchasing

  • stock management

  • production

  • visual consistency

  • scalability

Pack sizes

More sizes do not automatically create more sales.

Each additional pack size creates another SKU.

For example:

500 ml
750 ml
1 L
5 L

may look commercially attractive.

But initially, perhaps:

500 ml + 5 L

is sufficient.

One for consumers.

One for professionals.

Pack-size strategy should follow actual customer needs and distribution channels.

Think about concentration

Concentrates can change the economics and positioning of a range.

Potential advantages may include:

  • lower transport impact per use

  • professional positioning

  • lower packaging consumption

  • higher perceived technical value

But concentrates also require:

  • clearer instructions

  • dosing

  • user discipline

  • compatibility across dilution ratios

They are not automatically superior.

The application determines whether concentration creates value.

Build for the sales channel

Different channels favour different products.

E-COMMERCE

Can support specialist products and detailed education.

RETAIL

Requires immediate clarity and strong shelf communication.

PROFESSIONAL DETAILING

May value concentration, efficiency and process reliability.

DISTRIBUTION

Requires a portfolio that is easy to explain and commercially attractive for the distributor.

OEM / AUTOMOTIVE

May prioritize consistency, documentation and process integration.

A product range designed without considering channel economics may perform poorly even when the chemistry is excellent.

International ranges need discipline

Launching across multiple countries creates additional complexity.

Consider:

  • language

  • label space

  • classification

  • documentation

  • packaging

  • product names

  • claims

  • market-specific regulations

The wider the geographic scope, the more important standardization becomes.

A range that is difficult to manage in one country becomes significantly harder across ten.

Naming architecture

Product names should help customers navigate.

Names can communicate:

  • category

  • sequence

  • performance

  • application

  • technology

For example, a system might use:

01 WASH

02 PREP

03 CORRECT

04 PROTECT

05 MAINTAIN

Or more conventional product names supported by consistent category labels.

The exact naming style depends on the brand.

The important point is that the range should feel intentional.

Avoid building around competitor catalogues

A common way to develop a range is:

Competitor X has 35 products, so we need 35 products.

That is rarely a good strategy.

Competitor ranges may contain:

  • legacy products

  • overlapping SKUs

  • market-specific products

  • slow sellers

  • products created for historical reasons

Your range should be built around your own:

  • customer

  • brand

  • channel

  • market

  • capabilities

not someone else's catalogue.

Use sales data to guide Phase 2

Once the launch range is live, real data becomes available.

Look at:

  • unit sales

  • repeat purchase

  • margin

  • customer questions

  • bundle behaviour

  • complaints

  • distributor feedback

  • search behaviour

  • customer requests

Then ask:

What product should we develop next?

The answer becomes far more reliable.

When to discontinue a product

Range development also means removing products.

Consider discontinuation when:

  • sales are consistently low

  • the product overlaps another SKU

  • production complexity outweighs value

  • raw material issues create disproportionate difficulty

  • regulations change

  • customer behaviour changes

A smaller, stronger range is often better than permanent expansion.

A practical range-planning framework

For every proposed SKU, answer:

1. ROLE

Why does this product exist?

2. USER

Who is it for?

3. PROBLEM

What does it solve?

4. DIFFERENTIATION

Why would a customer choose it?

5. DEVELOPMENT ROUTE

Proven / Customized / Bespoke?

6. VOLUME

What do we realistically expect?

7. MARGIN

Does the product support the commercial model?

8. PACKAGING

Can it fit the existing packaging system?

9. LAUNCH PRIORITY

Launch / Phase 2 / Future?

10. CONNECTION

Which other products does it support?

If the answers are unclear, the SKU probably needs more thought before development starts.

Example range-planning table

| Product | Role | Development Route | Launch Priority |
|---|---|---|
| Ceramic Coating | Hero | Bespoke | Launch |
| Spray Sealant | Hero / Maintenance | Bespoke | Launch |
| Shampoo | Core | Customized | Launch |
| Wheel Cleaner | Core | Customized | Launch |
| Panel Wipe | Support | Proven | Launch |
| Interior Cleaner | Core | Proven / Customized | Launch |
| Glass Cleaner | Support | Proven | Phase 2 |
| Iron Remover | Support | Customized | Phase 2 |
| Compound | Core | Customized | Phase 2 |
| Leather Care | Extension | Proven / Customized | Future |

The exact structure will differ for every brand.

The important part is making the decisions deliberately.

The key principle

Do not ask:

How many products can we launch?

Ask:

What is the smallest range that clearly communicates what this brand stands for?

Build that first.

Learn from the market.

Then expand.

The Infinitec approach

When customers are developing multiple products, we prefer to define the range architecture before individual formulation work begins.

That usually means clarifying:

  • market position

  • customer type

  • workflow

  • hero products

  • launch range

  • Phase 2

  • expected volumes

  • development route per SKU

  • packaging architecture

  • target launch

Only then do individual product briefs begin.

This helps avoid developing products that later prove commercially unnecessary.

Planning a new range?

You do not need to arrive with a finished SKU list.

Tell us:

  • what market you are entering

  • who your customer is

  • where you will sell

  • how you want the brand positioned

  • what products you believe are important

We can help structure the range before development begins.

Start a Project

Continue reading:

Next: How to Write a Product Development Brief

THE INFINITEC DEVELOPMENT FRAMEWORKSee how these decisions connect to development

Practical Tool

Open the working template

Related Reading

Explore Custom Formulation · Explore Contract Manufacturing

Have a project where this matters?

Start a Project