Build story · In-house product

eCommerce: a storefront engine with many personalities.

Brands shouldn't have to rebuild commerce to change how they look. We separated the storefront from the engine, then gave the engine a theme system.

Scope

Product strategy, theme system, commerce engineering

Surface

Storefront + admin

Status

Built and supported in-house

store.algorithmbd.com
Multipurpose storefront preview with a full retail homepage, product grid and footer.

Multipurpose and Fashion, running on the same engine.

The problem

A brand's look changes faster than its commerce platform.

A seasonal campaign, a new collection, a different audience — each one wants a different storefront. Rebuilding the theme usually means touching the platform underneath. That's backwards.

Redesign

Becomes a replatform.

Templates

Flatten a distinct brand.

Data

Presentation and commerce get tangled.

Growth

Every new storefront starts over.

“Changing a typeface shouldn't require a migration.”

The principle behind the theme engine.

The approach

Separate the look from the ledger.

The theme should own type, colour, spacing and imagery. The engine should own products, customers, orders and payments. The boundary is the architecture.

01

Split the storefront from the engine.

Presentation becomes a layer, not a fork of the whole platform.

02

Turn design into tokens.

Typography, spacing, radius, imagery and component behaviour live in the theme.

03

Build presets, then custom themes.

Start from a strong preset or design a distinctive theme from scratch.

04

Keep commerce data independent.

Switch the look without touching products, customers or order history.

What we built

One engine. Nine very different storefronts.

Multipurpose, Fashion and Electronics are three of nine live presets. Each changes typography, spacing, radius and imagery treatment — while products, customers and orders stay put.

Explore the themes
Multipurpose theme: a flexible retail homepage for a mixed catalogue.

Multipurpose

Flexible, general retail

Electronics theme: spec-led product discovery for considered purchases.

Electronics

Spec-led, high consideration

Fashion theme: seasonal collections and lookbook-led merchandising.

Fashion

Seasonal, lookbook-led

Theme system

Presets, seasonal variants and custom themes share one component model.

Catalogue & checkout

Products, collections, cart and checkout stay independent of the theme.

Payments & orders

Orders, customers and payment records stay consistent across storefronts.

Admin & analytics

Manage the storefront and see what is selling from one place.

What changed

The look moves. The data stays.

A theme change should be a design decision, not an engineering project. The storefront can change while the commerce record keeps its shape.

No migration

A redesign becomes a theme change.

Reusable

One engine can carry more than one storefront.

Distinct

Brand expression lives in the theme, not a fork.

Stable

Products, orders and customers stay independent of presentation.

A note on numbers: this is an in-house build, so there are no client metrics to quote. The test is whether a brand can change its look without touching its data.

Under the hood

A commerce core with a removable coat.

The theme system is only useful if the commerce underneath is solid. Catalogue, checkout, payments and orders are designed to be depended on.

Storefront

ThemesCatalogueCollectionsProduct pages

Commerce

CartCheckoutPaymentsOrdersCustomers

Operations

AnalyticsTheme managementMultiple storefrontsCustom themes

Next build story

TaskShaper — one operating record for HR, payroll and projects.

Read the TaskShaper story

Your store, your rules

Give your products the storefront they deserve.

Tell us what you sell and how you want it to feel. We'll show you the themes, the admin and the migration path.