Usually, it all starts with one product and one name. Then a second position appears — slightly more expensive or slightly simpler — and the question arises: should it be given a new name or just append "Pro", "Lite", "2.0"? Within six months, the line expands to five to seven SKUs, and it turns out that the buyer does not understand the difference between them, and the sales department confuses the names in the price lists. This is a typical path by which brand architecture turns into a mess — not because the individual decisions were bad, but because they were made without a single logic.
Here a simple rule applies: a subbrand with a separate name is justified if the product changes the audience or the context of use so significantly that the old brand name will hinder rather than help. A descriptor or series is sufficient if only the level of characteristics changes within the same audience and the same consumption scenario.
If you are in doubt — ask yourself one question: will the buyer recognize the parent brand if you remove the subbrand from the packaging? If yes — the subbrand is redundant, a series is enough.
Here, most articles make mistakes in priorities. A study in the Journal of Marketing Analytics (Springer Nature) shows: it's more critical not the similarity of names, but the similarity of product functions. Sub-brands with similar functions cause greater cannibalization than products with different names but differentiated properties. That is, you can give two SKUs almost identical names — and they will not compete with each other if they solve different customer tasks. And vice versa: different bright names won't help if both products meet the same need at the same time.
Practical conclusion: before inventing a name, divide products by consumption moment, not by category. One SKU — 'morning', with one emotion and context, another — 'evening', with another. Then they won't take demand from each other, but expand the overall coverage of the line. This is a basic mechanism for protection against cannibalization, and it works more reliably than any tricks with names.
There is no universal answer, but there are criteria by which it's easy to decide.
| Criterion | A single logic (system) | Different names for each SKU |
|---|---|---|
| Number of items in the line | From 5 and above — a system is mandatory | Up to 4-5 — individual names are sufficient |
| Speed of launching new SKUs | High — the system saves time and budget | Low, individual launch once every one to two years |
| Brand objective | To fix memory of the parent brand | To maximize the difference of each product |
| Example | VW: Passat, Golf, Jetta — a single theme of 'wind' | P&G: Tide, Ariel, Pampers — independent brands |
An important caveat: semantic or phonetic themes that VW (wind names) and McDonald's (the 'Mac-' sound rhyme) used today are almost impossible to replicate — all lexical categories are occupied by others' registrations, and each name will have to be checked for legal purity separately. This is not a theoretical problem, but the first thing any team attempting to create 'their own theme' for a line in 2024–2025 years encounters.
Another fact to keep in mind when choosing: according to Nielsen and Ehrenberg-Bass data, a person can name on average 3–5 brands in a category without prompts, despite seeing hundreds of brands daily. Descriptive names like 'Delivery360' or 'SmartOffice' require additional advertising investments to anchor in memory compared to short or emotionally charged names. If there's no budget for promoting each SKU — a single system with one strong name saves not only time but also money on media.
Jardin had long named its flavors according to a geographical principle: Guatemala Cloud Forest, Original Oro. The names were informative, but did not create an emotional connection and were poorly remembered in the stream of competitors. Transitioning to emotional subbrands — Ethiopia Euphoria, Bravo Brazilia — unified under the common platform 'Art of Living,' resulted in a noticeable increase in sales and engagement with different flavors in the lineup.
The cost of such a transition is not a five-minute job: the team spent six months, developed six conceptual directions, and went through more than 60 name options before selecting the final set. This shows the real scale of the task for those who want a systematic rebranding of a product line, not just cosmetic label tweaks.
A four-level hierarchy solves a practical problem that is rarely written about: the same name physically does not fit everywhere equally. There is enough space on the packaging for the full name, only enough space in the marketplace search results for a short query, and enough space in the product card for a series and refinement.
The rule is simple: each level must work independently, without the other three. If you remove the 'refinement,' the buyer will still understand the brand and the series. If only the 'product' is visible in the marketplace search, the buyer will fill in the rest, because the product name already carries sufficient meaning. Checking the hierarchy for strength is a simple test: write the name in one line in different ways (full, series+product only, product only) and ask a stranger whether they recognize the brand in each variant.
To ensure the architecture withstands five years of product line growth, rather than collapsing after the third SKU, formally document:
These rules do not guarantee perfect naming, but they eliminate the most common cause of product line failure — decisions made on the fly, without considering what will happen to the portfolio in two years and ten SKUs.
Usually, it all starts with one product and one name. Then a second position appears — slightly more expensive or slightly simpler — and the question arises: should it be given a new name or just append "Pro", "Lite", "2.0"? Within six months, the line expands to five to seven SKUs, and it turns out that the buyer does not understand the difference between them, and the sales department confuses the names in the price lists. This is a typical path by which brand architecture turns into a mess — not because the individual decisions were bad, but because they were made without a single logic.
Here a simple rule applies: a subbrand with a separate name is justified if the product changes the audience or the context of use so significantly that the old brand name will hinder rather than help. A descriptor or series is sufficient if only the level of characteristics changes within the same audience and the same consumption scenario.
If you are in doubt — ask yourself one question: will the buyer recognize the parent brand if you remove the subbrand from the packaging? If yes — the subbrand is redundant, a series is enough.
Here, most articles make mistakes in priorities. A study in the Journal of Marketing Analytics (Springer Nature) shows: it's more critical not the similarity of names, but the similarity of product functions. Sub-brands with similar functions cause greater cannibalization than products with different names but differentiated properties. That is, you can give two SKUs almost identical names — and they will not compete with each other if they solve different customer tasks. And vice versa: different bright names won't help if both products meet the same need at the same time.
Practical conclusion: before inventing a name, divide products by consumption moment, not by category. One SKU — 'morning', with one emotion and context, another — 'evening', with another. Then they won't take demand from each other, but expand the overall coverage of the line. This is a basic mechanism for protection against cannibalization, and it works more reliably than any tricks with names.
There is no universal answer, but there are criteria by which it's easy to decide.
| Criterion | A single logic (system) | Different names for each SKU |
|---|---|---|
| Number of items in the line | From 5 and above — a system is mandatory | Up to 4-5 — individual names are sufficient |
| Speed of launching new SKUs | High — the system saves time and budget | Low, individual launch once every one to two years |
| Brand objective | To fix memory of the parent brand | To maximize the difference of each product |
| Example | VW: Passat, Golf, Jetta — a single theme of 'wind' | P&G: Tide, Ariel, Pampers — independent brands |
An important caveat: semantic or phonetic themes that VW (wind names) and McDonald's (the 'Mac-' sound rhyme) used today are almost impossible to replicate — all lexical categories are occupied by others' registrations, and each name will have to be checked for legal purity separately. This is not a theoretical problem, but the first thing any team attempting to create 'their own theme' for a line in 2024–2025 years encounters.
Another fact to keep in mind when choosing: according to Nielsen and Ehrenberg-Bass data, a person can name on average 3–5 brands in a category without prompts, despite seeing hundreds of brands daily. Descriptive names like 'Delivery360' or 'SmartOffice' require additional advertising investments to anchor in memory compared to short or emotionally charged names. If there's no budget for promoting each SKU — a single system with one strong name saves not only time but also money on media.
Jardin had long named its flavors according to a geographical principle: Guatemala Cloud Forest, Original Oro. The names were informative, but did not create an emotional connection and were poorly remembered in the stream of competitors. Transitioning to emotional subbrands — Ethiopia Euphoria, Bravo Brazilia — unified under the common platform 'Art of Living,' resulted in a noticeable increase in sales and engagement with different flavors in the lineup.
The cost of such a transition is not a five-minute job: the team spent six months, developed six conceptual directions, and went through more than 60 name options before selecting the final set. This shows the real scale of the task for those who want a systematic rebranding of a product line, not just cosmetic label tweaks.
A four-level hierarchy solves a practical problem that is rarely written about: the same name physically does not fit everywhere equally. There is enough space on the packaging for the full name, only enough space in the marketplace search results for a short query, and enough space in the product card for a series and refinement.
The rule is simple: each level must work independently, without the other three. If you remove the 'refinement,' the buyer will still understand the brand and the series. If only the 'product' is visible in the marketplace search, the buyer will fill in the rest, because the product name already carries sufficient meaning. Checking the hierarchy for strength is a simple test: write the name in one line in different ways (full, series+product only, product only) and ask a stranger whether they recognize the brand in each variant.
To ensure the architecture withstands five years of product line growth, rather than collapsing after the third SKU, formally document:
These rules do not guarantee perfect naming, but they eliminate the most common cause of product line failure — decisions made on the fly, without considering what will happen to the portfolio in two years and ten SKUs.