What agencies and merchants ask before building on it.

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.

A real shop. Cart, checkout, customer accounts and order records are part of the platform, so a storefront is transacting on day one rather than after a plugin project.

The same row the till decrements and the ledger posts against. Not a nightly sync with a disclaimer under it, which is the thing every competing storefront actually is.

Yes, because there is one pricing engine rather than two implementations of the same rule. A member price or a bundle behaves identically wherever the basket is built.

Web, counter, and account orders converge onto one order record with one status, so the shop fulfils from the floor rather than from a separate console per channel.

Card and UPI, settling into the same books as the counter and the storeDule app. Choosing your own processor does not cost you a percentage penalty here, which is not true everywhere.

The platform is multi-tenant by design and built for agencies and groups running many stores from one place. Tell us your expected number and we will scope it.

No. Stores can share a catalog or keep their own, which is what makes cooperatives and multi-brand operators work on one platform.

Yes, scoped to that merchant. They get their products and their orders without getting the platform, and your team keeps the parts that are yours.

Creating a store, mapping a domain, and applying a theme are API calls, so a storefront launch can sit inside your own workflow rather than being a manual checklist somebody works through.

One storefront is included with a grossDule plan and additional storefronts are priced per storefront per month, with the tiers published. Early access is free while we build together, and partner terms are a conversation rather than a page.

The merchant owns their content, catalog, customers and orders, and all of it exports in open formats. A platform that makes leaving painful is one you have to defend rather than recommend.

Not yet. Both are on the roadmap and both are expected on a hosted platform, so it is worth knowing before you plan a campaign around them.

Not fully. Company accounts, custom price lists, payment terms and quotes are a named gap on the roadmap.

Nothing yet, and we will not imply otherwise. The platform is designed to meet DPDP and GDPR obligations, with encryption in transit and at rest, scoped access, and audit logging. A certificate gets named and dated when it exists.