Sign-up, trial and tenant setup
Self-serve onboarding that creates an isolated store, owner login, subdomain and trial in a single step.
Solutions · Commerce SaaS
A store builder never sells a product of its own. It rents merchants a complete shop, with a domain, a theme, a catalogue, a checkout and an admin, all running on shared infrastructure while each merchant’s data, customers and money stay walled off from the next one. This model is for founders who want to be the platform those merchants subscribe to, not another storefront fighting them for shoppers.
Professional plan. Enterprise customization is quoted on scope.
One codebase, isolated tenant data
Plans that switch features on and off
Custom domains with automatic certificates
V1
Self-serve onboarding that creates an isolated store, owner login, subdomain and trial in a single step.
Products with variants and stock, collections, discount codes, shipping zones, tax settings and one hosted checkout.
Enough choice for shops to look different, with edits kept as settings so themes can be upgraded underneath.
Two or three plans enforced server-side, card billing with retries, and domain connection with automatic certificates.
Operating loop
The sign-up form creates a tenant: a store record, an owner account, a default theme, a temporary subdomain and a trial plan. Within minutes the merchant can add a first product and see it on a live page, which is where most trials are won or lost.
They choose a theme, rearrange sections in a visual editor, upload a logo, write policy pages and connect their own domain. The platform checks the DNS record, issues a TLS certificate and serves the shop on that domain without the merchant touching a server.
A shopper sees only the merchant’s brand. Cart, checkout, tax and shipping rates follow that merchant’s settings, the payment settles to the merchant’s account through the platform’s payment integration, and the order appears in the merchant’s admin.
Each cycle the merchant is charged the plan fee, any usage such as extra staff seats, and a transaction fee if they process cards through an outside provider. A failed renewal moves the shop into a grace period, then a locked state, and never straight to deletion.
Roles
Runs one shop or several, sets prices and policies, and decides which plan is worth paying for. Judges the platform by how quickly a change can be made on a busy day without breaking checkout.
Packs orders, answers customers and edits products under permissions the owner grants. A seasonal helper should be able to print labels without seeing payouts or deleting the catalogue.
Never needs to know the platform exists. Expects a fast page, a checkout that remembers them on that shop, and order emails carrying the merchant’s name and reply address.
Runs plans and pricing, screens new shops for fraud and prohibited goods, answers merchant support and tracks trial conversion, churn and payment volume across every tenant.
Hard parts
One missing store filter in a report or export shows one merchant another merchant’s customers. Enforce tenancy at the lowest layer, through row-level security or a tenant-aware data access layer, and run automated tests that try to read across tenants on every release.
A merchant running a flash sale or importing two hundred thousand products can slow every other shop sharing the database. Queue heavy jobs per tenant, rate-limit per store, and serve storefront reads from caches that a single tenant’s import cannot flush.
Every merchant domain needs DNS verification, a certificate issued and renewed over ACME, and correct routing at the edge. A certificate that quietly expires takes a shop offline, so renewals need monitoring and an alert to the merchant when their DNS stops pointing at you.
Merchants customise themes, then the platform ships a new theme version. Store merchant edits as settings and section data layered over a versioned theme instead of letting them fork template code, or every theme release turns into a pile of support tickets.
Hiding a button in the admin does not stop an API call. Each feature a plan unlocks, from staff seats to discount rules, must be checked server-side, and a downgrade has to define what happens to data created under the larger plan.
Operator controls
Plans defined as bundles of limits and feature flags, prices per currency, and one-off exceptions for a single merchant without a code change.
New stores checked for prohibited categories, copied branding and payment risk signals, with a switch that pauses checkout on one shop while the rest keep trading.
Look up any shop to see its plan, domain status, recent errors and failed webhooks, and enter it as a support user with the merchant’s consent and an audit trail.
Invoices, failed charges, retry schedule, grace periods and lock or reactivate actions, with revenue reported by plan and by sign-up month.
Revenue
Tiered subscriptions priced on features and limits, usually with a discounted annual option. This is the predictable base of the business.
A margin on card payments processed through the built-in payment integration, or a percentage on orders paid through an outside provider.
Once outside developers sell add-ons and themes in your directory, the platform keeps a share of each sale or subscription.
Later
Open it once your own API and webhooks are stable; outside developers build on whatever you publish, and breaking it later is expensive for everyone.
Valuable for merchants who also trade from a physical shop, but it is a separate hardware and stock-sync problem.
Add local prices and currency switching when merchants start selling across borders in real volume.
Next decision
Weighing a store builder against a marketplace that sells under one brand? The e-commerce overview sorts the models by who owns the shopper and the stock.
Open registerIf shoppers should browse every seller in one place while you take commission on each order, a multi-vendor marketplace fits better than separate shops.
Open registerWhen your customers mainly need brochure sites, blogs and bookings with a small shop attached, an extensible website builder is the closer model.
Open registerWant a team to build the tenant platform, billing and merchant admin with you? Our SaaS development service describes how that work is planned and what code you keep.
Open registerLive demo
Open each app or panel in a new tab and sign in with the demo login shown. The demos run on shared sample data, carry our demo product names, and show the ready-made product before any customization.
Artifact register
Reference screens illustrate workflows, not a contracted feature list. Sample prices, data, and responses are demonstration content; confirm the current scope during a walkthrough.
Deployable Product Architecture
Medicine delivery workflow / system register
Live operations
Pharmacy shelves for medicine delivery app planning
Request
Assign
Track
Settle
Deployable Product Architecture
Clinical operations technology / system register
Care workflow
Medical team using digital health workflows
Verify
Schedule
Deliver care
Audit
Deployable Product Architecture
Facility service workflow / system register
Content platform
Facility operations for on-demand service app content
Publish
Discover
Deliver
Moderate
Deployable Product Architecture
Laundry processing operations / system register
Product delivery loop
Laundry processing for service app planning
Discover
Blueprint
Build
Operate
Store builders are often tempted to court shoppers directly with a shopping app or a cross-store marketplace. That tends to backfire, because merchants chose a store builder precisely to own their customers. Spend the effort on what makes a merchant’s week easier: faster product edits, clearer order screens, payouts that arrive when promised and pricing without surprises.
Judge the business by trial-to-paid conversion, revenue retained from each sign-up cohort and the share of new merchants who take a first order within seven days. Total shops created flatters everyone, since most trial stores are abandoned before they sell anything.
Merchants rarely ask how tenancy works until something leaks, and one cross-tenant bug can cost the trust of every merchant who hears about it. Give isolation tests, per-tenant rate limits and audited support access named owners and release checks, the same as checkout, rather than treating them as infrastructure to tidy up later.
Limits that rise as a merchant succeeds, such as staff accounts, locations or advanced reports, let small shops start cheaply and pay more as they expand. Limits that punish success, such as hard caps on monthly orders, push the best merchants to migrate away just as they become valuable to you.
FAQ
In a marketplace, shoppers browse one site and the operator owns the customer relationship. In a store builder, every merchant has a separate shop and brand, keeps its own customers and pays the platform a subscription, while the platform stays invisible to shoppers.
Rarely at the start. A shared database with a tenant key on every row, enforced at the data layer, is cheaper to run and to upgrade. Separate schemas or databases suit large merchants with contractual isolation needs, so design the code to allow moving one tenant there later.
Yes. The merchant points a DNS record at the platform, which verifies it, issues a certificate automatically and renews it before expiry. Keep the platform subdomain working as a fallback, so a DNS mistake does not take the whole shop offline.
If card numbers pass through your servers, yes, and the scope is wide. Loading card fields from the payment provider, or sending shoppers to its hosted checkout, keeps card data off your systems and narrows that scope, although duties remain for the pages that load those fields.
After your own admin runs on the same API you intend to publish. If your team relies on private shortcuts, outside apps will hit gaps, and every later change risks breaking somebody else’s product.
Primary sources
Dated official documentation, standards, and research that support the factual claims on this page.
The protocol used to issue and renew certificates automatically for merchant custom domains.
Card-data standards that decide how much of a hosted checkout falls into compliance scope.
One example of a payments platform that lets a SaaS route card payments to each merchant’s own account.
How to read this page
Scope, cost and timeline figures are planning guidance until confirmed in a written proposal. Diagrams and screens are illustrations, not client deliverables, and source-code rights and handover follow the signed agreement. See the delivery process and the full disclaimer.
Next decision
Define outcomes, constraints, evidence, rights and handover before delivery begins.
Commercial rights, repositories, environments, documentation, acceptance and handover remain contract-defined.