Brand architecture is the structure that explains how a company's brands, products, and services relate to one another. It determines which name leads, how closely an offer is associated with its parent, and where a distinct identity is needed. Four common approaches are the branded house, house of brands, endorsed brands, and hybrid architecture.
Think of it as a family tree with a customer-facing purpose. The connections matter, but so does what each name means to the person choosing a product. This guide compares the four models, examines Apple, Procter & Gamble, Marriott, and Coca-Cola, and explains how to choose and implement a structure without creating unnecessary brands.
What Is Brand Architecture?
Brand architecture provides a framework for organizing a portfolio. It answers practical questions: should a new service carry the company name, have its own name, or use a phrase such as “by” the parent brand? Should customers see two offers as closely related or as different choices?
A company's legal structure, management chart, and brand architecture are not interchangeable. Two brands can share an owner, manufacturing, or support systems while presenting different promises to customers. Conversely, one recognizable brand can span several business units. The architecture describes the intended brand relationships, not who reports to whom.
As companies diversify or acquire businesses, brand architecture becomes part of a wider strategic decision about audience, positioning, and growth. A diagram helps make the relationships visible, but the useful output is a set of rules that teams can apply to names, communications, and customer experiences.

Distinguish a Master Brand, a Sub-Brand, and a Product Name
The master brand is the main identity an offer draws on. A sub-brand has a distinct identity within that relationship. A product name or descriptor may simply identify what someone is buying. Not every feature, service package, flavour, or price tier needs to become a separate brand.
For example, “Northstar Payroll” could be a descriptive offer under a fictional Northstar business. Calling its plans “Essential” and “Advanced” would not automatically create two more brands. The question is whether each name has a separate promise and identity that customers need to understand, not whether it appears in a product catalogue.
Why Brand Architecture Matters
Documenting robust brand architecture gives teams a way to resolve recurring decisions instead of debating every launch from scratch. It can help customers understand what belongs together and help the business decide where to share recognition, where to preserve differences, and which names warrant continued investment.
The benefits depend on execution. One identity can reduce duplicated design and communication work, but it may stretch too far across unrelated offers. Separate identities create room for different positions, but each needs support. Architecture does not automatically generate loyalty, lower costs, or eliminate reputational risk.
Review the structure when customers confuse products, teams invent overlapping names, an acquisition brings valuable recognition, or a new offer no longer fits the existing promise. A branding project should address those relationships before settling on how everything looks.
The Four Main Brand Architecture Models
The most useful comparison is how prominently the parent brand appears and how much independence each offer needs. These models are planning categories rather than rigid boxes. Some frameworks treat sub-brands as a separate category; here, they are considered within the degree of connection between an offer and its master brand.
1. Branded House: One Main Identity Across Related Offers
A branded house makes the master brand the main source of recognition across its products or services. Individual offers can have different names and functions while sharing an overall identity and promise. A customer should readily understand that they belong to the same family.
This model is worth considering when the offers serve compatible needs and the parent name adds useful reassurance. Teams can reuse parts of the identity system, concentrate communication around one name, and explain related products together. However, every offer still needs a clear purpose; shared branding cannot resolve a confusing product range.
The main tradeoff is association. Problems with one offer can affect perceptions of the others, and a move into an unrelated category may strain what the master brand stands for. A future separation can also require more work if a product's identity depends heavily on the parent.
Apple's core product range illustrates this pattern. Its official product navigation brings Mac, iPad, iPhone, and other offers together within the Apple environment. The connection does not depend on every product literally including “Apple” in its name. This is an interpretation of the visible relationship, not a claim that every business Apple owns uses an identical model.

2. House of Brands: Distinct Identities Under Common Ownership
A house of brands gives individual brands their own customer-facing identities and positions. The corporate parent may be visible in company information or on packaging without leading the purchase decision. Distinct branding does not mean completely separate operations or an absence of shared resources.
This approach can suit a portfolio with meaningfully different audiences, price positions, or category expectations. One brand can communicate a specialized promise without asking the same name to represent every offer. The cost is maintaining several identities, content programmes, and routes to market rather than assuming one campaign serves them all.
Separation may reduce immediate associations between brands, but it does not guarantee that a problem stays contained. Customers, partners, and media can connect related companies. Decisions about quality, reputation, and corporate accountability still require attention across the portfolio.
P&G's brand directory includes Tide, Pampers, and Gillette under their distinct names. Their shared owner is clear on the corporate site, while the product brands address different needs. That illustrates a house-of-brands relationship without establishing how independently every operational decision is made.
With a legacy spanning over 180 years and a global presence serving 5 billion consumers across 10 product categories, P&G's portfolio was profiled in The Branding Journal's January 2022 overview. Those reach and category figures belong to that historical source, not a current audience estimate or evidence that architecture alone caused the company's performance.

3. Endorsed Brands: A Distinct Name With Visible Reassurance
An endorsed brand leads with its own identity while showing a connection to a parent or endorsing brand. “Courtyard by Marriott” makes the relationship explicit: Courtyard identifies the hotel brand, while “by Marriott” supplies the endorsement. The two names have different jobs.
Consider this model when an offer needs a distinct position but the parent's reputation is relevant to the buyer. It can also be useful when an acquired brand has recognition worth retaining. The endorsement needs a clear rationale; a parent name that means little to the audience may add clutter rather than reassurance.
The tradeoff is maintaining two identities and their relationship. Define the endorsement wording, placement, and relative prominence across the website, packaging, and sales materials. A visible link can transfer negative perceptions as well as positive ones, so endorsement is not a risk-free compromise.
Marriott's wider portfolio also shows why a whole company need not fit one simple label. Its hotel brand portfolio includes Courtyard by Marriott alongside names such as Sheraton and Westin. Marriott Bonvoy, meanwhile, is a travel and loyalty programme, not another hotel brand equivalent to Courtyard. Compare the specific relationship, not just the corporate owner.

4. Hybrid Architecture: Different Relationships Within One Portfolio
A hybrid architecture combines models where different parts of a portfolio need different treatment. A company might keep closely related offers under one master brand while retaining an acquired name with a distinct audience. The relationships should follow explicit criteria rather than whatever naming choice was made most recently.
The advantage is flexibility. The difficulty is governance: teams must know when to use the parent, when to endorse a name, and when to keep a separate identity. A hybrid model is not automatically the best of every approach. Without clear rules, it can preserve the confusion it was meant to solve.
The Coca-Cola example is easiest to understand at two levels. The Coca-Cola Company owns a portfolio that includes Coca-Cola, Sprite, Fanta, Dasani, and Minute Maid. Calling all those names sub-brands of the Coca-Cola drink would confuse corporate ownership with consumer-facing branding.
Within the Coca-Cola trademark family, the company's 2016 One Brand packaging announcement described a shared red-disc design across Coca-Cola variants. That historical initiative illustrates a closely connected product family within a broader portfolio of distinct names. It does not establish that all portfolio brands carry the same endorsement or that the 2016 design remains unchanged.
The companion Coca-Cola marketing case study examines communication and campaigns. Architecture addresses the earlier decision: which brand is doing the communicating, and how does it relate to the rest of the portfolio?

How to Choose a Brand Architecture Strategy
Start with the business problem, not the model used by a famous company. Compare plausible structures against the same criteria and record the evidence behind your decision. The following questions help identify where connection is valuable and where separation earns its cost.
- Would customers naturally group the offers together? Shared ownership is not enough if the needs, expectations, or reasons for choosing differ substantially.
- Which name already carries useful recognition? Examine what customers associate with the parent and with each existing brand before removing either.
- Can one promise credibly cover the portfolio? A price difference alone need not require a new brand, but conflicting positions deserve closer examination.
- Can the team fund the proposed structure? Account for research, identity, content, websites, customer support, and maintenance, not just a logo launch.
- What happens after an acquisition, new category, or disposal? Test how an additional offer would enter the structure and how an existing one could leave.
Use brand research to investigate recognition, associations, and customer confusion rather than assuming all existing names are valuable or all buyers prefer simplicity. Start with customer-facing evidence and check it against operational constraints.
As a practical decision rule, consider a branded house when the shared promise is credible; separate brands when meaningful differences justify separate investment; endorsement when both distinctiveness and a relevant parent connection matter; and a hybrid when different parts genuinely require different rules. None of these choices removes the need to test the result.
For a closer comparison of the two ends of that spectrum, the branded house versus house of brands guide explores their respective tradeoffs. A model name should summarize a decision, not substitute for one.
A Hypothetical Portfolio Decision
Imagine Northstar sells payroll and scheduling software to the same small-business buyers. A shared Northstar identity with descriptive product names is a reasonable starting hypothesis. Creating a separate brand for each feature would add names without necessarily helping customers choose.
Now suppose Northstar acquires a specialist product whose customers recognize that name but have little awareness of Northstar. Keeping the name initially, testing an endorsement, or gradually migrating it are different options. Compare customer understanding, recognition, support needs, and transition costs before choosing. The acquisition alone does not dictate the architecture.
Turn the Model Into Naming, Design, and Website Rules
Map the Portfolio Before Renaming It
Inventory every customer-facing name, including product families, service packages, tiers, regional variants, and acquired brands. Record the audience, offer, current parent association, and where each name appears. Separate existing facts from proposed changes so the team can see what must actually move.
Then assign each name a role. Decide whether it is a master brand, a distinct brand, an endorsed brand, a product line, or a descriptor. This makes brand naming a response to the architecture rather than an open-ended search for memorable words. The product-line naming guide provides a related framework for managing names within those roles.
Make Relationships Visible Without Making Everything Identical
The visual identity should express the chosen relationship. A branded house may share typography, colour, and layout conventions while using product descriptors to distinguish offers. An endorsed system needs a consistent way to show the parent without overwhelming the lead brand.
Document approved name combinations, endorsement placement, and examples at realistic sizes. Check a product card, presentation cover, package, and mobile header. A relationship that only works on a large portfolio diagram is not ready for everyday use.
Test How Customers Find and Compare Offers
Translate the structure into website design: navigation labels, product pages, comparison routes, and clear explanations of who provides each offer. Brand architecture and website information architecture should support one another, but they are not the same thing. Customers may need to browse by task or category rather than by the company's internal hierarchy.
Use UI/UX design to test ordinary journeys. Can someone identify the right product, understand the difference between tiers, and find support? Ask participants to explain what they think the names mean before telling them the intended structure. Record the misunderstandings and revise the presentation.
A separate brand does not automatically require a separate domain, and a shared brand does not dictate every URL. Decide from the customer journey and operational requirements. When URLs do change, Google's site-move guidance recommends mapping old URLs to appropriate new destinations, implementing redirects, and monitoring the move. Do not treat a cleaner brand diagram as a guarantee of unchanged search traffic.
Governance and Rollout: Keep the Structure Usable
Assign an owner for architecture decisions and define which changes require review. A new product family or acquisition needs more scrutiny than another descriptive feature label. Keep a current portfolio map, naming rules, identity examples, and a record of exceptions with their reasons.
Architecture work does not always require a full rebrand. Some problems can be addressed through clearer descriptors, consistent endorsement, or better navigation. Where an established name must change, plan customer communication, sales materials, packaging, support references, and website updates together.
Before rollout, establish how you will assess clarity: whether customers select the correct product, understand brand relationships, or ask fewer questions about confusing names. Also track the work required to maintain the system. These observations can guide improvements, but changes in sales or support volume have other possible causes and should not automatically be attributed to architecture.
The strongest brand architecture is one your customers can understand and your team can maintain. Choose the level of connection each offer needs, make the rules visible in everyday materials, and revisit them when the business changes.
For help connecting portfolio strategy, naming, and your website experience, contact Brand Vision to discuss your priorities.











