Botble Ecommerce SaaS | Multi-tenant Store Platform

Ecommerce SaaS is a standalone, self-hosted multi-tenant store builder – no subscriptions required. Install it once on your own server and sell online stores the way the big hosted store builders do: a visitor picks a plan and a store address on your marketing site, and about a minute later they have their own storefront, their own admin panel and their own database. You keep the recurring revenue, the customer data and the source code.

Where most “multi-store” scripts put every merchant into one shared set of tables, Ecommerce SaaS gives each store its own MySQL database, storage directory and cache keyspace. Around that sits a purpose-built operator console, a 38-endpoint REST API, 27 signed webhook events, 43 languages with RTL on both the marketing site and the control plane, and 20 storefront presets so a new store opens with a themed catalogue instead of an empty screen.

Built on the Botble CMS core and Laravel, with complete source code included. The store side is the full Botble ecommerce admin. The platform side – plans, quotas, billing, provisioning, domains, API and webhooks – is the part a normal ecommerce script does not have.

Why Ecommerce SaaS?

Hosting stores for other people is a different problem from running one store. The moment a second merchant signs up you need isolation, billing (plans, trials, failed cards, suspensions), operations (updating fifty stores without visiting fifty admin panels) and a way for your own systems to react when a store is created or cancelled. Ecommerce SaaS was built for that job from the start, not by bolting a store column onto a single-store script.

• Real database-per-store isolation – one database, one storage directory and one cache keyspace per store. A store can be moved or removed on its own, and no store’s products, orders or customers are ever mixed with another’s.
• A control plane you can automate – 38 REST endpoints and 27 signed webhook events, so your CRM, billing or support desk can create, suspend and inspect stores without a human in the loop.
• Operations quality – a preflight check before launch, one command that updates every existing store after a release, every impersonation written to the platform log, and every billing change recorded with who caused it.
• 43 languages on both sides – the marketing site your customers sign up on and the console you run the platform from, RTL included.
• 20 storefront presets – every new store opens with a themed catalogue to edit, not an empty screen.

We deliberately did not compete on feature count. The core is kept lean so it stays upgradeable: POS, wallets, loyalty points, live chat and similar extras are not bundled – they are the roadmap for paid add-ons.

Third-party services you may need

Please read this before buying. Several optional features in this product connect to services that are not ours and are not included in the purchase price. Enabling them requires you to register your own developer or merchant accounts with those providers, accept their terms, and pay any fees they charge. We do not control their pricing, approval processes or availability in your country.

The product runs without any of them. Each feature below is switched off until you supply your own credentials, and nothing else in the product depends on it.

Payment gateways for your stores’ shoppers

• Stripe, PayPal, Razorpay, Paystack, Mollie and SSLCommerz each require your own merchant account with that provider, plus their onboarding and identity checks
• Gateways charge their own transaction fees and, in some cases, monthly or payout fees. Those fees are set by the provider and are entirely separate from the price of this item. Availability varies by country
• Cash on delivery and bank transfer need nothing external and work out of the box

Stripe for subscription billing

• Charging your own store owners uses Stripe Checkout and the Stripe Billing Portal, which needs a Stripe account and is subject to Stripe’s fees and country availability
• Without Stripe you can still assign, change and cancel plans by hand from the operator console, and take payment offline by bank transfer. No other subscription processor is included

An SMTP provider

• Lifecycle email (store ready, trial ending, payment failed, suspension, bank-transfer receipts) needs a mail service. Nothing external is bundled; any SMTP provider works, configured once for the whole platform

A DNS provider you control

• Store subdomains need a wildcard DNS record and a wildcard certificate on a domain you own. Customer custom domains are verified against the exact DNS records the product shows them. Domain registration and certificates are between you and your provider