Your domain in front. The retail core behind.

A storefront is only as good as what it is connected to: the catalog, the stock, the payments and the analytics that make it a shop rather than a page.

The web layer

Your domain, your brand, your search presence

Domains and DNS

Map any domain or subdomain per storefront, provisioned as part of creating the store.

Theme tokens

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

Search and social

Canonical URLs, sitemaps, structured data, and link previews per store, built in rather than bolted on.

Analytics

Storefront traffic and conversion measured per store, so an operator can compare their own sites.

The commerce layer

Everything a storefront needs is already behind it

Headless catalog API

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

Card and UPI checkout

Checkout settles into the same books as the counter and the storeDule app.

storeDule

The app-style shopper surface, on the same core. Run either, or both.

Early Access

Ship branded storefronts with the first cohort

Tell us how many storefronts you expect to run and what your stack looks like, and we will shape the partner terms and the theming engine around it.

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.

Features

Everything webDule does, from your own domain to the catalog behind it.

Use cases

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

Pricing

Your own branded storefront, on the same catalog as grossDule. Free during early access.

FAQ

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