One brand, several names: when an offer needs a family and when it needs order
Organise relationships between a main brand, products, services and variants so names help customers choose.
Article language: English

In this article
A company has three services, four proper names and seven ways of writing them. A customer asks for “that catalogue package”, while the team uses an internal chat to establish whether it means a product, a stage of cooperation or a campaign from two years ago. A new logo for each name would look impressive. For now, a family dinner where everyone gets the right place card might help more.
Brand architecture defines relationships between the main brand, product names, services and their variants. On a website it appears in menus, headings, comparisons and labels. Its job is to help answer simple questions: who offers this, what is it for and how does it differ from the neighbouring offer? An elaborate diagram becomes useful when it helps answer them.
Not every new offer needs a separate brand. Sometimes it needs a description, sometimes a shared family name and sometimes a consistent qualifier. Decide that relationship before designing another set of marks. Otherwise the identity starts preserving the disorder it was meant to solve.
List what the customer can actually choose
Imagine a fictional studio furnishing spaces. It sells shelving, designs layouts and runs a workshop on organising a home studio. The shelves are called “Linia”, the design service “Plan” and the workshop “Przestrzeń”. Everything belongs to one company, yet each word has received its own mark and a different presentation on the site.
From the customer's perspective the problem is not the number of names. It arises when the customer cannot recognise the type of offer. Is “Plan” a shelf, a subscription or a meeting? Can shelving be bought without design? Does the workshop include furnishings? The first task is to record the relationships between offers, not vote for the prettiest logo arrangement.
For each name, note what the customer receives, how it is ordered, whether it can be chosen independently and which other item is needed to use it. Add where the name currently appears. A price list, website, post-purchase message and instruction file may now describe the same scope under different titles.
Separate a public name from a working term. “Project North” may be a useful internal codename without needing to become a service name. A technical system variant need not appear in the offer if the customer makes no decision based on it. Having its own row in a spreadsheet does not automatically give it citizenship in the menu.
Stack Overflow's naming principles define the main brand, sub-brand, product and feature separately and identify descriptive naming as the default. This describes that organisation's own system. It can prompt a question about the level of a name without copying the hierarchy into another company.
In our studio, buying a shelf is an independent decision. Layout design is a separate service, though it can support the purchase. Shelf colour is a product variant. Approval of a drawing is a process stage. Ordering these four levels immediately reduces the number of things said to need their own brand.
Keep historical names in the inventory too. Mark their current equivalents and where the older form still appears. When a customer brings an old offer, the person helping them should recognise its scope rather than invent a connection based on a similar sound. Customers may still use old names in conversation and search. They need not return to the main menu, but the team should know where they lead. Removing an old word from a presentation does not erase it from customers' memories or saved document names.
A shared family should explain a shared meaning
A product family makes sense when a common name helps people recognise a meaningful relationship. For shelving it might be a compatible system of modules. For services it might be a shared way of working or audience. The mere fact that two things are sold by the same department may be too weak a reason to ask customers to remember another level of division.
A family name and qualifier can work together. “Linia - low shelf” explains both the relationship and the specific object. In “Linia Compact Essential”, the extra words sound serious, but someone must still establish which means size, scope or the author's enthusiasm. If a qualifier does not help predict the difference, it is not doing its job.
Define the family's boundary too. If shelves use different connectors and cannot be freely combined, a common-looking name should not suggest complete compatibility. The page must explain the limitation at selection, not only in assembly instructions. Brand architecture therefore touches actual product dependencies, not just graphic packaging.
For services, check whether names mix a stage with a result. “Diagnosis”, “Design” and “Care” might describe a sequence of cooperation. “Store”, “Catalogue” and “Portfolio” might describe result types. Putting them all in one row of cards makes comparison harder, even if every card has the same height and perfectly even shadow.
Comparing two services (in Polish) requires common criteria. Naming should help people find them. If one name speaks about time, another about customer type and a third about project scale, the visitor must reconstruct the rules. Decide first which axis the company uses to distinguish its offers.
Sometimes a short description under an existing name is enough. Not every ambiguity requires renaming a product. If customers recognise “Linia”, keep it and add “modular shelves for a studio”. Communication can use existing recognition while a newcomer still understands the category.

When does an offer need a separate name?
A different audience, buying method or experience that the current brand does not explain may justify a separate name. These are reasons for discussion, not an automatic recipe. An additional brand means more materials, language rules, maintenance and a new relationship the audience must learn.
Mozilla's report on its rebrand describes bringing offers together under the Mozilla umbrella and the difficulty created by Firefox's strong association with a browser. This is a specific, historically described reason for changing name relationships. It does not prove every company should adopt the same model.
For our studio, a separate workshop brand may look tempting, but first check whether the workshop has its own customer flow and enduring scope. If it is a one-off event supporting shelf sales, an event title with a clear organiser name may suffice. There is no need to build a small empire of marks for a Saturday meeting.
On the other hand, the design service may need a clearer place if customers routinely mistake it for a free addition to a purchase. A separate page with scope and ordering method may solve this. Only observing that journey will show whether the problem was the relationship between brands or simply the absence of a visible service description.
Compare two possible solutions on real tasks. In one, keep the main brand name and add a service qualifier. In the other, give the service a separate name with a consistent owner attribution. Ask a visitor to explain what they are ordering and from whom. Do not begin by asking which version seems more prestigious. Prestige is a convenient place to hide an unresolved decision.
When designing B2B website information architecture (in Polish), also establish the route between offers. A shelf customer should find a suitable layout service, but need not see the company's entire organisational tree. Connections should support the next choice rather than present every internal dependency.
If you want to turn an organised offer into a website, Aeneia Design is a place to discuss content structure and consistent presentation of services.
Establish wording that survives beyond the home page
After choosing a hierarchy, prepare a short naming glossary. For each item record the full name, permitted short form, category description and an example sentence. Also identify forms no longer in use. A page of rules may be more useful than dozens of impressive mockups that do not answer whether a message should say “Plan” or “Plan Studio”.
Test names in ordinary use: a card title, message subject, form and a person's reply. A word that sounds good alone can become awkward in a sentence. You need an inflection rule or a construction that avoids the problem. Do not leave every person to conduct a separate language experiment.
Also establish when a name needs explanation. An internal team may use an abbreviation, while a visitor arriving from search needs the offer category. A description beneath a product name can be necessary on its page even if it appeared earlier on the home page. Nobody is obliged to start a visit with a company-prescribed prologue.
Naming must meet the brand's voice in the interface (in Polish). If a card calls a service “Plan”, the form should not suddenly ask the visitor to choose “Project Package Pro”. Buttons and confirmations should use the same recognisable term. The visitor then knows they are still discussing the same scope.
Separate the naming rule from appearance. Once names are approved, organise handover of brand-logo variants (in Polish) so files do not reproduce the old naming confusion. Capital letters in a mark need not mean capitals in every sentence. A family colour should not be the only information about membership. Once the order is understandable, its visual roles can become design tokens (in Polish) instead of being recreated by hand for each new card.
Do not expand the design work into a claim that a name is legally available. Choosing communication and checking rights to use a sign are separate tasks. If a company plans a new market name, agree the scope of a separate check with a qualified specialist. The website design should use a name approved for use.
Finally, test a future extension. Add one hypothetical product and one service that do not yet exist. See whether the system names them clearly without another exception. You need not predict the company's entire development. It is enough to notice whether the first new item forces you to explain the basic relationships again.
Finish acceptance with a short conversation with someone outside the team: show the offer and ask them to identify the product, the service and their relationship. If they correctly identify what can be bought separately and what is a variant or stage, the hierarchy helps perform the intended task. Then service-page copy (in Polish) can be more concrete too, because the names no longer obscure scope.
Pass the rules to the person maintaining the catalogue. Each new name should have a decision owner and a reason for introduction. Future proposals can then enter a conversation about function, audience and relationship before receiving their own logo. A brand family can be large. It just helps if customers do not need a genealogy to buy a shelf.










