← All articles
Case Studies

Variant-Level Product Content for BREE: Extending a Custom Shopify Broadcast Theme

Variant-Level Product Content for BREE: Extending a Custom Shopify Broadcast Theme

A colour change can change more than a product’s appearance. For a luxury fashion brand, it can also change how that product should be described.

For BREE, a Germany-based luxury fashion brand, I extended a heavily customised Shopify Broadcast theme to support variant-specific titles and descriptions on the product detail page. The goal was to give the team more control over colour-specific storytelling without disrupting the content already displayed across the existing catalogue.

The challenge: more flexibility, no visible disruption

BREE’s product pages already used custom product-level metafields for titles and descriptions. These fields replaced the standard Shopify product title and description on the storefront.

The new requirement was to let each colour variant have its own custom title and description, with the displayed content changing when a customer selected a different colour.

The important constraint was backwards compatibility. Existing products needed to look exactly as they did before, without requiring the team to copy their current content into every variant.

For me, this was not just about adding two new fields. It was about extending an established content model without breaking the workflow the client already relied on.

The approach: variant overrides, product-level defaults

I structured the feature around a simple rule: variant content takes priority when it is populated; otherwise, the existing product-level custom content continues to display.

The title and description follow that rule independently. A variant can have a custom title while still using the product’s existing custom description, or vice versa. The team does not need to populate both fields just to change one.

That distinction matters. Treating variant content as an all-or-nothing override would create unnecessary content work and make partial updates harder to manage.

With the fallback in place, an existing product can remain untouched. Its current custom title and description continue to apply across its variants until the team deliberately adds variant-specific copy.

Integrating with a heavily customised Broadcast theme

Because BREE’s Broadcast theme had already been extensively customised, the implementation needed to fit the existing product-page behaviour rather than introduce a separate interaction.

The content update follows the selected variant. When a customer changes colour, the PDP title and description reflect that selection, using either the variant’s custom content or the product-level fallback.

The same content rules apply when the page first loads. Variant-aware content should not depend on a customer making an additional selection before the correct copy appears.

This is an important distinction in Shopify theme development: storing content in metafields and keeping the storefront in sync with variant selection are two separate parts of the feature. Both need to work together for the experience to feel native.

The requirement also covered desktop and mobile. The layout can differ between screen sizes, but the selected variant needs to determine the content consistently.

Making content management practical

The new editorial workflow centres on two variant metafields: a custom variant title and a custom variant description.

For future products, BREE can manage its copy primarily at variant level. For existing products, the product-level fields remain useful defaults.

That gives the team a gradual adoption path. They can add tailored content where it matters without turning the entire catalogue into a migration project.

It also keeps the choice with the content team: shared copy where it is appropriate, colour-specific storytelling where it adds value.

Why backwards compatibility was central to the build

In an established storefront, a new feature should not create work simply to preserve what already exists.

Without the fallback logic, introducing variant-level content could leave existing product pages with missing copy or force the team to duplicate content across variants. Keeping the current product-level fields as defaults avoided that problem.

The feature was designed to be additive. It expanded what the team could do without requiring them to abandon their existing setup.

The result

The completed customisation gave BREE variant-level control over PDP titles and descriptions within its existing Broadcast-based storefront.

Customers could see content relevant to their selected colour, while products without variant-specific copy retained their existing product-level content. The team could then introduce the new workflow selectively, rather than updating every product at once.

The takeaway for Shopify developers

The interesting part of this project was not the number of fields added. It was the relationship between content priority, variant selection and an existing customised theme.

A good implementation needs to respect all three: give the merchant more control, keep the customer-facing experience consistent, and preserve the content that already works.

For BREE, that meant building variant-level overrides on top of reliable product-level defaults. A focused change, but one that made the product page more flexible without making catalogue management more complicated.

Put this into practice

For a small, well-scoped version of this exact work, it's live as a Fiverr gig.

Fiverr gig

I'll build you a custom AI agent

An assistant trained on your business that replies and takes actions for you.

See the gig