Work / EV-03 / Multi-store architecture · b2b

Two lighting brands, two continents, one codebase.

An Australian store copied into a European sister brand, built so every fix ships to both at once.

Client: Lighting manufacturer, AU and EU
Catalogue: 10,000+ lighting products
Status: AU live · EU built, pre-launch
Stack: Shopify, GitHub, Cloudflare Workers

EV-03a · HOW ONE CODEBASE SERVES TWO BRANDSSCHEMATIC

main · shared theme code + workers

store/versalux

Own branding, templates and content. Live in Australia.

store/architech

Own fonts, colours and logo, five more languages prepared. Europe and UK.

CODE CHANGES START IN MAIN · BRAND FILES ARE MERGE-PROTECTED · THE CLIENT EDITS EACH STORE IN THE THEME EDITOR

THEME FILES IDENTICAL 523/523 Across both stores. Only branding and content differ.

SECOND BRAND CHECKED Every change to the European brand was checked against the live Australian store, which stayed unchanged.

EV-03b · CARRIED INTO THE NEW STORE

27,277media files, 0 failed

695redirects

144metafield definitions

73collections

10,000+products, imported by the client's team

FEATURE · DATASHEET PDF

Long datasheets were cut off at one page. Now they print in full.

A server renders each product datasheet as a multi-page A4 PDF with page numbers, a running header and the right logo and contacts for each brand. One click, the same file on every device.

FEATURE · LIGHTING DATA FILES

IES, LDT or both, in one dropdown.

Lighting planners download the photometric file their software needs. Built once and live on both stores the same day, because there is only one codebase.

FEATURE · PROJECT BRIEFCASE

One service, both stores.

The project list on both storefronts runs as one Cloudflare deployment that recognises which store is calling and answers with that store's data.