Your own domain
Map any domain or subdomain. Each store is its own branded site, not a sub-path.
Your own branded storefront,
live in minutes.
webDule is the white-label web surface of the retail core: your own domain, server-rendered pages, and a theme per store, on the catalog you already keep.
In early access, alongside grossDule
Your domain, your brand, live in minutes
Server-rendered and SEO-ready, a theme per store, on the same catalog and stock as grossDule.
Trusted
Why a storefront keeps becoming a project
Three ways a branded web presence costs more than it should. Every one of them is a consequence of building the site separately from the shop.
A quarter, for one site
What it does
A storefront platform, not a one-off build
webDule turns the retail core into a themeable, multi-tenant web surface. One codebase, a storefront per store, each on its own domain and brand.
Theme per store
Colours, type, and layout tokens per store, from a shared, upgrade-safe design system.
Server-rendered and fast
SSR pages that load fast and index cleanly, with structured data and social cards per store.
Provisioned in minutes
Spin up a new branded storefront from a template. No rebuild, 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. Never out of sync.
Provisioned, not built.
Pick the template, set the theme tokens, point your domain at it. The storefront is serving server-rendered pages on your own brand, with no rebuild and no redeploy for the next merchant.
The launch path
The storefront you do not have to build twice.
In the box
Every storefront ships with the commerce already wired
A webDule store is not a template waiting for an integration project. The catalog, cart, checkout and account surfaces are part of the core, so a new storefront sells on its first minute.
Catalog, categories and product pages
Generated from the same catalog the counter reads, with variants, attributes and media resolved live. Adding a product is not a second job on a second system.
Cart and checkout
Cart, address, delivery or pickup, and payment through the provider you choose. The result is a real order on the platform, not an email somebody has to retype.
Accounts and order history
A customer signs in once and sees what they bought, whether the sale happened on the site or across the counter, because it is one identity and one order book.
Pages, sitemaps and social cards
Content pages, canonical URLs, structured data, sitemaps and a social card per store, generated when you publish rather than pasted in afterwards.
Live Preview
See webDule in Action
your own branded storefront, on one catalog
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.
For everyone who ships storefronts
Whether you run one store or a hundred, webDule is the branded web surface you do not have to build twice.
Independent merchants
One core, three surfaces
webDule is the branded web surface of the same domain-agnostic core that runs the counter and the shopper app. One catalog, three ways to sell.
grossDule™
Operations
The operating system your whole store runs on.
- Purchase orders, procurement, inventory, and warehouse
- POS, pricing, and the live catalog webDule reads from
- Offline-first, GST and country fiscal ready
storeDule™
Storefront
The shopper side of your store.
- Mobile-first storefront: cart, checkout, loyalty
- The same catalog, in your customer's pocket
- Click and collect straight to the counter
webDule™
WebYou are here
Your own branded storefront.
- Your own domain, theme, and SSR pages
- The white-label web surface for the same catalog
- Provisioned in minutes, no rebuild per store
What we will stand behind
The commitments, not the compliments
These are the guarantees webDule is built to keep. Each one is something you can verify on the first storefront you provision, which is a better thing to offer than a quote we cannot attribute.
A theme never forks the platform
Colours, type and layout tokens are configuration on a shared design system. A store cannot be themed into a version that stops receiving improvements, which is what makes upgrading everyone at once possible.
The catalog has one home
Storefronts read catalog, pricing and stock over an API instead of holding a copy. There is no import to schedule and no drift to discover, because there is nothing to keep in step.
A store is provisioned, not shipped
A new branded storefront comes from a template and a domain mapping. No release, no redeploy, and no per-merchant branch anybody has to maintain later.
Your data and your domain stay yours
The domain is yours, the content exports in open formats, and nothing about the platform depends on you being unable to move. Export is a feature, not a negotiation.
Frequently Asked Questions
storeDule is the shopper app surface, quick to turn on. webDule is your own branded website on your own domain, server-rendered and themed per store. Both read the same grossDule catalog, so you can run either or both.
Yes. Each webDule storefront maps to your own domain or subdomain and renders as its own branded site, not a shared sub-path.
Yes. webDule is white-label and multi-tenant, built for agencies and groups to provision and manage many branded storefronts from one platform. Ask us about early partner terms.
webDule is in early access with the founding grossDule stores and first agency partners. Apply for early access and we will onboard you as it ships in your market.
Colours, type, and layout tokens per store, drawn from a shared design system. The system stays upgrade-safe, so a theme does not freeze you on an old version.
Not to launch one. A storefront is provisioned from a template rather than built, which is the difference between a launch and a project.
Pages are server-rendered with canonical URLs, sitemaps, structured data, and social cards per store, so crawlers and link previews see real HTML.
Yes. About, contact, delivery, returns and opening hours are content blocks rather than a developer ticket, because a shop website is more than a product grid with a checkout on the end.
A theme is tokens on a shared system rather than a fork, so improvements land on your site instead of leaving you on the version you launched with. That is the whole reason themes are tokens and not copies.
Explore
Go deeper into webDule
The full picture, one page at a time.
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.