Should a product range use the masterbrand logo or its own sub-brand?

Start with the relationship the range needs

Imagine an illustrative kitchenware business, Elm Table, introducing repair parts alongside its serving bowls. The repair range might simply be another Elm Table collection. A distinct outdoor equipment range could raise a different naming question. The choice depends on what buyers should understand about the offering, not whether the launch team wants fresh graphics.

Write the relationship in a plain sentence: this is the same brand, this range is supported by the parent, or this is a separate customer-facing brand. Shopify's architecture overview explains these different relationships. Use that vocabulary to clarify the brief, without assuming a structure will improve sales.

For Elm Table, write two alternative customer sentences before drawing anything: “These are Elm Table replacement parts” and “This is an independently named outdoor brand.” Then ask the business owner which sentence is accurate and intended. If the answer is still undecided, hold the logo brief. This is a naming and responsibility decision, not a test of which symbol gets more votes.

Separate a range name from a second identity

A descriptive collection name can sit beneath the masterbrand without becoming an independent mark. Check whether the name identifies a product family, a use occasion or another business. If customers need to recognize Elm Table first, a repair-parts descriptor should not compete with it as though it were a separate manufacturer.

List where the relationship must appear: store navigation, packaging, service instructions and invoices. A proposal that looks clear on a front label may become confusing in a customer-support message. Decide which name the customer should use when asking for a replacement. That practical question often reveals an unnecessary extra layer of branding.

Use a missing-context check: remove the shop header from a proposed label, then remove the label from a support email. In each isolated view, can a reader tell which name to quote and where to seek help? Record the exact phrase they read rather than calling the relationship obvious. A confusing endorsement needs clearer wording or prominence; it does not automatically justify another brand. A compact storefront logo solves a space constraint within the same identity.

Choose an architecture with explicit consequences

Give one person responsibility for the relationship decision and another for the visual execution. Multiple visual concepts cannot resolve an unresolved ownership or naming question. Record uncertainty as a hold point rather than allowing the most attractive symbol to determine the business structure by accident.

Apply the decision in order. First confirm the intended relationship and who can authorize it. Next decide whether the range needs its own customer-facing name. Only then approve the parent credit and its placement. An endorsed route needs an agreed visible association; separate branding needs an accurate service explanation even if the parent is absent from the front. These are editorial decision prompts, not automatic consequences of ownership alone.

Explore the identity that was actually chosen

In Logo studio, describe the authorized business, audience and intended relationship when exploring an original range identity. If the chosen route retains the masterbrand, commission a clear descriptor arrangement instead of requesting a competing symbol. CartVisual's concept generation does not establish brand ownership or automatically enforce an identity hierarchy.

Keep the approved parent artwork intact. A designer should assemble exact lockups and refine any selected raster concept into appropriate vector masters outside CartVisual. Compare the result in the real destinations and ask which brand a viewer thinks supplies the product. Qualitative reactions guide revision; they are not a market-wide recognition measurement.

Keep the architecture sentence identical across candidate briefs. Otherwise a comparison may reward a change in business promise instead of a better mark. Once the relationship is approved, use the neutral logo comparison for alternative executions. Approve motion permissions separately if a chosen mark will animate.

Save a rule for the next range

The handoff should specify required parent wording, relative prominence, permitted arrangements and examples of a range that does not need another logo. Preserve the decision reason alongside the artwork. A future product manager can then decide whether a proposed launch genuinely changes the relationship or only adds another collection.

For Elm Table, repair parts could retain the bowl brand while using clear component descriptions. An independent outdoor identity would need its own approval. Review that rule when ownership or customer expectations change. A consistent architecture remains a deliberate policy, not an automatic consequence of using similar colors in generated images.

Copy the following blank record into the project brief. The empty cells are fields to complete from the actual decision; they are not an approval or a report of an exercise already performed.

If the supplier name changes, a range is sold separately, or support moves to another business, reopen this record before reusing the lockup. A seasonal palette change alone may leave the architecture decision intact.