A storefront per merchant. One platform behind them.

Your own domain, your own theme, server-rendered pages that a search engine can read, and the catalog and stock of the retail core underneath every one of them.

The site

Your brand, on your domain

webDule turns the retail core into a themeable web surface. One codebase, a storefront per store, each on its own domain and brand.

Your own domain

Map any domain or subdomain. Each store is its own branded site, not a sub-path on someone else's.

Theme per store

Colours, type, and layout tokens per store, drawn from a shared design system that stays upgrade-safe.

Server-rendered and fast

Pages that load fast and index cleanly, with structured data and social cards per store.

Search and social, handled

Canonical URLs, sitemaps, and link previews are part of the platform rather than a plugin to install.

The pages a shop needs

About, contact, delivery, returns, and opening hours as content blocks rather than a developer ticket, because a storefront is more than a product grid.

Readable on any screen

Responsive layout, real contrast, and keyboard-reachable navigation come from the design system, so accessibility is not per-merchant homework.

The shop underneath

It is a shop, not a brochure with a form on it

The reason this is a platform rather than a site builder: the commerce is already there, running on the same core as the counter.

Cart and checkout

A real basket, a real checkout, and real order records from day one. There is no plugin project between launching and taking money.

Live stock, not a snapshot

The quantity a shopper sees is the row the till decrements. Not synced overnight, not an approximation with a disclaimer under it.

One pricing engine

Promotions, member prices, and bundles behave identically on the website and at the counter, because there is one engine rather than two implementations of the same rule.

Orders the shop can fulfil

Web orders land on the same list as counter and account orders, so the shop floor works from one queue instead of a console per channel.

Customer accounts

Order history, saved addresses, and loyalty balance for the same customer record the shop already has, rather than a separate web identity.

At scale

Built to run many stores, not one

The hundredth storefront should cost what the first one did. That is an architecture decision, and it is the whole reason this exists as a platform.

Provisioned in minutes

Spin up a new branded storefront from a template. No rebuild and no redeploy per merchant.

White-label and multi-tenant

One platform, many stores, built for agencies, groups, and cooperatives to run at scale.

One catalog, headless

Reads the same grossDule catalog, pricing, and stock over a clean API, so it is never out of sync.

Isolated per merchant

Each tenant has its own data and its own configuration. A change one merchant makes cannot reach another, which is the property an agency is actually buying.

One upgrade, every store

Themes are tokens on a shared system rather than forks, so an improvement lands everywhere instead of on whichever sites somebody had time to revisit.

Measured per store

Traffic, conversion, and revenue per storefront, so an operator running twelve of them can compare their own sites rather than guess which theme is working.

For whoever runs them

The day-to-day of operating a portfolio

Every store in one console

Launch, theme, configure, and check on all of them from one place, under your own brand rather than ours.

Access per merchant

A client can be given their own products and orders without being given the platform, and your team keeps the parts that are yours.

Shared or separate catalogs

Stores can run on one shared catalog or keep their own, which is exactly what makes a cooperative and a multi-brand operator work on the same platform.

Provisioning over the API

Creating a store, mapping a domain, and pushing a theme are API calls, so an agency can put a storefront launch inside its own workflow.

Early Access

Ship branded storefronts with the first cohort

webDule is in early access with the founding grossDule stores and our first agency partners. Join now to shape the theming engine and the partner program.

Free during early access. One catalog with grossDule and storeDule. Your data stays yours.

Explore

More from webDule

The full picture, one page at a time.

Use cases

Who ships storefronts on webDule, from one merchant to a hundred.

Pricing

Your own branded storefront, on the same catalog as grossDule. Your first storefront is included.

Integrations

What webDule plugs into: your domain, your catalog, your payments, your analytics.

FAQ

Every question we are asked about webDule, answered in one place.