What merchants ask before opening an online counter.

storeDule is designed as the shopper surface of grossDule and reads its catalog, pricing, and stock. The two are built to run together, so the storefront is never out of sync with the counter.

No. storeDule reads the same catalog you already keep for the shelf. Change a price or a product once and it updates in store and online together.

Yes. storeDule supports pay-online, pay-at-store, delivery, and click-and-collect, with collect orders dropping straight onto your counter queue.

storeDule is in early access with the founding grossDule stores. Apply for early access and we will onboard you as it ships in your market.

No. The storefront opens in the browser on their phone, so there is nothing between seeing the link and shopping.

Yes. Shelf and screen share one live count, so "do you have it" is answered before the trip rather than at the shelf.

Points, member prices, and promotions apply the same online as they do at the till, because it is one programme rather than two.

It is not offered, because the count is live rather than a nightly snapshot. If something goes during picking, the shopper is offered the substitution rather than finding it in the bag, and the order and receipt reflect what was actually supplied.

Past orders and saved lists are one tap away, which is how a weekly shop actually behaves. The person at the till and the person online are one customer record, so history and points do not fork.

Your own staff, from the counter queue. Collect and delivery orders arrive on the same list the shop floor already works from.

Run collect only. Delivery windows are a capability you turn on, not a commitment you have to make to use the storefront.

The catalog is the one you already keep for the shelf. The daily work is picking the orders that come in, not maintaining a second system.

Slots, cut-off times, and how many orders an hour you accept are yours to set. A storefront that commits the shop to more picking than it can do is worse than no storefront.

A return moves stock back to a slot and posts the credit, against the order it came from. Both halves happen, rather than the refund happening and the stock quietly going missing.

Yes, or one shared shop. Either way each runs on its own live stock, so a customer is never offered something that is only sitting in another town.

No. You pay for the software, not a share of what you sell. Marketplace economics and shop economics are different things, and thin retail margins do not survive a percentage on every basket.

One storefront is included with a grossDule plan, and additional storefronts are priced per storefront per month. Early access is free with your grossDule store, and the tiers are published.

Card, UPI, and pay-at-store, all settling onto the same books as the counter. Your processor is a choice you can change without changing your storefront or paying a penalty for choosing differently.

The same as one rung up at the counter: the same tax treatment, the same receipt rules, and the same sealed fiscal record. There is no second set of books to reconcile at month-end.

Not yet. Both are table stakes on a hosted storefront platform and both are on the roadmap. We would rather you know that now than discover it in week three.

Not fully. Company accounts, custom price lists, payment terms and quotes are named as a gap and are on the roadmap. Trade selling at the counter works today; trade selling online does not yet.

On the roadmap, built as a single rail rather than one integration each. The catalog is already model-agnostic, so this is a projection over what exists rather than a new data model.

Because you will find out anyway, and a page that only lists wins is a page you cannot plan against. Everything above is either shipped and described in the present tense, or named as roadmap.