One Shopify theme run as a shared platform.
An enterprise multi-brand commerce group's shared Shopify theme platform — a Horizon reference theme extended for regulatory age-gating, a headless CMS integration, GA4 analytics and multiple app integrations, used upstream across umbrella brands — plus a legacy-platform-to-Shopify replatform for one brand, delivered under enterprise CI/CD governance.
Constraint confirmed · outcome not claimed
- Industry
- Enterprise multi-brand Shopify (regulated retail)
- Platform
- Shopify Plus
- Theme
- Horizon
- Engagement
- Since November 2025
Built with.
- Reusable base theme
- Magento → Shopify
- Headless CMS integration
- CI/CD pipeline
- Staging + production stores
- Visual regression
- Unlighthouse
- Sentry
- Snyk
- SonarQube
- Consent manager integration
- Age gate
- SSR compliance footer
- GA4
The real constraint was a platform, not a theme.
This is an anonymised account — no name, logo, screenshots or identifying detail. A large multi-brand commerce group needed one Shopify theme to behave as a platform, not a one-off build. Several umbrella brands had to inherit the same maintained foundation, and the storefront carried real regulatory weight, so the constraint was never "build a theme" — it was keeping customisation maintainable and compliance dependable as the foundation fanned out across brands.
Treated as a one-off, that programme drifts: each brand forks the theme, compliance becomes a per-brand bolt-on, and analytics and app behaviour blur into the theme's own code. The diagnosis was to hold all of it as one long-lived platform product instead.
Compliance and content engineered in, not bolted on.
A Horizon reference theme was extended for enterprise use and shared upstream across the group's umbrella brands, with brand-specific customisation isolated so the platform stays maintainable as it spreads. Regulatory behaviour — an age-gate and consent-aware storefront — was built as a first-class platform feature rather than a per-brand patch.
Around that core: a headless CMS integration so editorial content is authored outside the theme and composed into the storefront; GA4 analytics with a clean dataLayer across theme, consent state and checkout-tracking surfaces; and multiple third-party app integrations, with app-owned behaviour kept distinct from theme-owned code. One brand on the foundation was a replatform off a legacy commerce platform onto Shopify, reusing the shared platform rather than forking it.
A foundation each brand inherits, kept reliable under governance.
All of it ran under enterprise delivery discipline — automated quality and accessibility checks, code review and release governance — so the platform stays dependable as more brands adopt it. The reusable point is capability, not a result: we can operate inside an enterprise Shopify programme where a shared upstream theme platform, regulatory compliance, headless content, analytics integrity, app boundaries and release governance all matter at once.
The hard part of this work sits outside the page template: keeping customisation maintainable across brands, treating compliance and consent as platform features, and routing analytics, app and pipeline findings to their real owner. No business, compliance or launch outcome is claimed; the evidence supports the scope and the engineering role, not launch, conversion, security or accessibility results, so none are stated.
Scope confirmed · lift not claimedRecognise this in your store? Bring this page to the call.
We'll tell you in 20 minutes whether the same constraint applies to your situation — and what the right next step would be.