11001
0x4F
11001
0x4F
0x4F
FF
0x4F
&&
&&
01
=>
FF
10110
::
11001
{}
0xA3
0xA3
::
=>
All case studies
Next.jsMedusaMulti-marque

A regional brand on a shared core

A Breton store built on the same e-commerce core as its sister brands, with its own catalogue, collections and cultural identity.

ClientBreizh Gobelet

Visit the site
Screenshot of the Breizh Gobelet website
The client

Personalised drinkware, the Breton edition

Breizh Gobelet addresses the Breton market with a deliberate cultural stance: fest-noz, fest-deiz and pardon collections, and product names in the Breton language.

That grounding is not cosmetic. It is what justifies a separate brand rather than a regional category inside a generalist store.

The challenge

Launching a brand without starting over

Building a second complete store — catalogue, configurator, cart, customer account — to address a regional market would have doubled the development cost and, more importantly, doubled the maintenance to come.

Conversely, a simple regional category inside an existing store would have diluted the cultural positioning, which is precisely what makes the brand interesting.

The solution

A shared core, an independent brand

Breizh Gobelet runs on the same application core as the group’s other stores, while having its own domain, catalogue, collections and analytics. What is shared is the code; what is its own is the brand.

01

Dedicated catalogue and collections

Collections follow the Breton cultural calendar rather than a generic split by occasion, with references named in the Breton language.

02

Shared application core

Configurator, cart, customer account and checkout all come from the shared core. An improvement built for one brand benefits the others.

03

Separate analytics

Each brand has its own measurement container, so performance can be steered brand by brand without mixing audiences.

04

Multi-brand deployment

The architecture allows a new brand to launch by configuring catalogue and content, without redoing checkout development.

Tech stack

The technologies we chose

The same Next.js front end and Medusa engine as the sister stores, with catalogue, collections, content and analytics specific to the brand.

Next.js

Medusa

Fabric.js

Scaleway Object Storage

Tailwind CSS

The outcome

One more brand, not one more platform

The group runs several distinct brands on a single core. The marginal cost of a new brand becomes a catalogue and an editorial line, rather than a whole platform.

MPWB

Working on something similar?

Give us thirty minutes. We will tell you plainly what is feasible, at what budget and on what timeline.

Response within 24h 100% confidential No commitment