Storely
An operator-owned, multi-tenant ecommerce platform for running independent merchant stores from one centrally maintained engine.
Storely is an operator-owned, multi-tenant ecommerce platform. You run one instance. Each merchant gets an isolated store organization, manages it from a back office, publishes a governed storefront template, and serves that storefront on their own domain. It replaces running one separate site install per client with one engine you maintain centrally.
Every merchant can sell without another installation to maintain.
Running one site per client makes every improvement a fleet problem. A routine change becomes a sequence of upgrades, plugins drift apart, storefront behavior diverges, and the operator spends more time reconciling installations than helping merchants sell. The damage compounds as the customer base grows: one fix reaches some stores but not others, support must first discover which version a merchant has, and every new account adds another environment to watch. A commerce business needs each merchant to feel independent without turning the platform behind them into a collection of unrelated projects.
- Catalog, variants, collections and media (Manage products, variants, collections and media, with CSV/JSON portability for products, variants and customers)
- Cart, discount, checkout and order engine
- Payments and refunds through enabled matrix cell (Stripe Connect payments and refunds using direct charges on connected accounts)
- Merchant orders, fulfillment, refund and credit note operations
Storefront changes reach shoppers without turning publication into guesswork.
A storefront is the merchant's public promise, so a change that cannot be trusted is more expensive than a slow edit. Teams hesitate to update campaigns, switch presentations, or correct content when they cannot tell what will go live, whether the last version can be recovered, or which hostname shoppers will actually reach. That uncertainty creates stale stores and late-night launch checks, then turns every correction into an incident. The operating goal is simple: merchants should be able to change the storefront confidently while the platform owner avoids a support queue filled with preventable publishing surprises.
- Governed storefront template, slots, preview, publish and rollback
- One custom merchant hostname (Custom merchant hostname provisioning with ownership verification)
The selling loop stays legible after the customer completes checkout.
The moment after checkout is where fragmented commerce systems start charging interest. Stock, payment, fulfillment, customer history, adjustments, and recovery often tell different stories, leaving staff to reconstruct what happened before they can answer a simple question. Every handoff increases the chance of duplicate work, an incorrect promise, or a customer waiting while two dashboards disagree. As volume grows, the cost is not just slower support; it is the loss of confidence that the order record reflects the business. Store teams need one operating story they can follow from demand through resolution.
- Inventory ledger and short-TTL reservations
- Customer account, addresses and store-scoped order history
- Merchant orders, fulfillment, refund and credit note operations
- Abandoned-cart eligibility and recovery (Consent- and suppression-aware abandoned-cart email sequences)
Owners and staff work each store without inheriting the whole platform.
Multi-store operations fail quietly when access is broader than the job. A store employee sees controls they should never need, an owner cannot tell where merchant authority ends, and the platform team becomes the only group trusted to make ordinary changes. That produces support dependency on one side and avoidable risk on the other. The problem grows with every merchant because permissions that were understandable in the first store become impossible to reason about across dozens. Each seat needs a clear scope so daily commerce work can move without turning every task into a platform-level decision.
- Staff invitations and merchant roles
The commit path is re-entrant. If a process dies between recording a paid order and taking the stock, the next attempt re-commits — a no-op once committed — instead of leaving a paid order whose stock was never taken and a reservation held forever.
Expired reservations are swept by a scheduled task. If scheduled work is not running, stock stays held after abandoned checkouts.
The cart is persistent and signed, and works for guests. Checkout is a server-side quote-then-finalize state machine:
Orders reference the quote they came from, so an order can never exist without the priced, validated basis it was created from.
Refunds reconcile against the order's real refundable balance and call the provider with an idempotency key before persisting anything. The path fails closed — an unknown provider outcome never becomes a recorded refund.
Staff permissions are allowlisted per employee — typically orders, catalog and inventory. Owner-only surfaces are: staff management, billing, payment onboarding, capability configuration, domains, template choice, publish, rollback, customer erasure, and shipping and tax configuration. Staff never reach those regardless of permissions.
Where an account lands after sign-in: super_admin and admin go to the admin panel, org_admin and staff go to the merchant dashboard, and member goes to the public home.
The platform underneath the product — counted in this product's own source, not claimed from a template. Where a row carries a list, open it to read the names behind the number.
Coinbase
dLocal
Flutterwave
Komoju
Mollie
NOWPayments
Opn
Paystack
ActiveCampaign
Customer.io
Segment
Canny
Amplitude
Custom Head Scripts
Pushover
Twilio SMS
Crisp
Tawk.to
Monday.com
fal.ai
Axiom
hCaptcha
Freshsales
Pipedrive
Pabbly Connect
AWS S3
MuxHover a table to isolate what it touches; click one to read its relationships. The big nodes are what everything else hangs off. organizations is referenced by 83 tables because every single record in this product belongs to an organization, and that is what makes tenant isolation a property of the database rather than something the application has to remember on every query.
all 97 tables, as text
active_boosts · admin_notifications · analytics_daily · analytics_events · analytics_funnels · announcement_dismissals · announcements · api_key_logs · api_keys · assistant_actions · assistant_conversations · assistant_messages · assistant_usage · audit_logs · automation_log · automation_templates · cart_items · carts · checkout_quote_lines · checkout_quotes · collection_products · commerce_collections · commerce_intent_events · commerce_orders · commerce_products · commerce_provider_events · commerce_rollups · credit_balances · credit_notes · credit_transactions · currencies · customer_addresses · data_exports · data_imports · discount_redemptions · discounts · faq_categories · faq_items · feature_flags · fulfillment_items · fulfillments · inbound_webhook_events · inbound_webhooks · inventory_items · inventory_ledger · inventory_reservations · languages · marketing_audience_members · marketing_audiences · merchant_payment_accounts · merchant_staff_permissions · notification_log · notification_rules · notifications · order_items · organization_limit_overrides · organizations · payment_transactions · pickup_addresses · plans · platform_secrets · platform_settings · product_media · product_options · product_purchases · product_variants · products · provider_prices · push_devices · recovery_attempts · refund_items · refunds · report_templates · roles · scheduled_tasks · seo_meta · shipping_rates · shipping_zones · store_capability_cells · store_customer_sessions · store_customers · store_domains · store_profiles · store_template_content · store_usage_counters · storefront_publications · storefront_template_packages · subscriptions · tax_rules · theme_page_sections · theme_section_library · theme_sections · translations · user_sessions · users · webhook_logs · webhooks
The chassis, and anything particular to this product. 3 required, 2 optional.
Next 16.2.10 and React 19.2.3.
Supabase is present in the product tree.
Four jobs are declared in `vercel.json`; on another host they must be wired manually.
Brevo, Mailgun, Resend, SendGrid and SMTP providers ship.
UPSTASH, NEXT and SENTRY families appear in the shipped example configuration.
Already built — plug and play
Every provider integration in this list ships wired into the product. You bring your own keys, connect them in the admin, and go live — there is no integration code to write. Nothing is resold through us: the ongoing cost is whatever these providers charge you. Capabilities marked plan-gated elsewhere on this page unlock by plan, not by extra code.
What exactly do I receive after purchase?
The complete source repository behind the live demo — 197,713 lines across the application and its database, 97 tables defined by 130 migrations that the shipped scripts apply for you, plus the seed data, the demo accounts and the setup documentation. Not a subset and not a scaffold: the same code that runs the demo you just used.
Is the live demo the same product whose source I receive?
Yes. The Storely demo runs the delivered release (v1.0.0), and the build figures on this page are measured from that same source — not from a showcase build kept separately.
Can I test every account role before buying?
Yes — all 3 of them: Store staff, Store owner, Platform operator. Each one is seeded in the live demo and reachable from the role board above, so you can inspect the product from the customer's side, the agent's side and the administrator's side before you decide.
Is this a complete product or a starter template?
Complete. 122 page modules and 350 HTTP operations, with authentication, roles, billing, an administration panel, background jobs and seeded demo data all wired and running. A template gives you the shape of an application; this is one you can deploy and start operating.
Can I rebrand and modify it?
Yes, without asking. The name, identity, copy, styling and code are yours to change. Rebranding and operating it as your own service is exactly what the licence is for.
What does the licence allow?
A perpetual, worldwide, non-exclusive, non-transferable licence to the product you bought and to every update released for it. The Standard licence covers one business — yours. If you deploy for clients, the Client licence covers up to five. You can modify it, rebrand it, deploy it and charge your own customers.
Can I resell the source code?
No. Reselling, redistributing, sublicensing or giving away the source itself is not permitted under either licence. You build and deliver products with it — the code stays with you.
What services and ongoing costs are required?
You bring your own accounts, so we never mark anything up and there is no ongoing cost to us beyond the purchase. Required: Node host, Supabase, Scheduled runner. Optional: Email delivery, Optional environment services. The table above says exactly what stops working without each one; most have usable free tiers at low volume.
How difficult is deployment?
Two ways, and most buyers use the first. The installer in your saascode dashboard walks it: you create free accounts at Vercel and Supabase, connect them, and it provisions the database, applies 130 migrations, seeds the data, deploys and verifies the result — you watch the steps go green. Or take the source and do it yourself with the shipped scripts and docs, which is the same sequence run by hand.
What updates and support are included?
Updates to that product for as long as we maintain it — no renewal fee and no expiry date on your access. Support covers download problems, defects in the code as shipped, questions about what the product does and how it is structured, and licence questions. It does not cover debugging your own modifications, building features for you, or setting up your hosting and third-party accounts.
Why does a complete codebase cost $299?
Because it was built once and is distributed many times. SaaSCode builds each product and ships the same finished release through the catalog, so the price reflects repeatable distribution — not a reduced codebase, an unfinished template, or what the same work would cost commissioned.
Do I need to be a developer?
No, for the normal path. You create free accounts at Vercel and Supabase, connect them to the installer in your saascode dashboard, and it does the deployment for you — provision, migrate, seed, deploy, verify. What it asks of you is creating two accounts and copying a token, not writing code. If you would rather deploy it yourself, or host it somewhere else, the full source and the scripts are yours to do that with. Running the product day to day needs no technical skill at all: that happens through its own interface, which is what the demo shows.