A commerce platform for merchants who have outgrown what a hosted store will let them do — and don’t want to spend two years building one.
We’re building it in the open. Below is what runs today, what’s in development, and what’s still just a plan. If you sell things for a living, we’d like to know which parts matter to you — that’s what decides the order we build in.
They start on a hosted platform because it’s the sensible thing to do. Then the catalog gets strange, or the sale becomes a conversation, or they need to sell in two currencies and three languages — and suddenly they’re paying four apps to half-solve one problem, with their data somewhere they can’t reach it. We’ve built around that wall for other people for years. ClusaCart is us building the thing on the other side of it.
Most platforms treat the admin as an afterthought behind a pretty storefront. We started there — 69 pages of it. Orders, returns, claims, edits, price lists, inventory across locations. The parts you live in every day, not the parts that demo well.
Paste your own keys into the admin and they work on the next request. We verify the connection against the live service before it goes green, and encrypt it at rest. Your keys stay yours — they never sit in our environment.
Edit your theme as much as you like. Nothing reaches a customer until you publish. Changing your homepage on a Friday should not be an act of courage.
Made-to-order, made-to-measure, high-value pieces where the inquiry is the checkout. We built that as a first-class flow with WhatsApp attached, because bolting three apps onto a normal cart never quite works.
Everything tagged Running today exists and works — you could use it this afternoon if we handed you a login. The rest is tagged for exactly what it is. We’d rather you trust the list than be impressed by it.
Sixty-nine pages covering the real job: orders, catalog, inventory, customers, marketing, content, settings. Laid out along conventions you already know, so moving in does not mean relearning where things live.
Payments, fulfillments, returns, claims and order edits each as their own working surface. Draft orders for phone sales, quotes and wholesale. Configurable columns and saved views.
Products with media, options, variants, per-variant pricing and images. Categories with drag-to-organize, collections, types and tags. CSV import and export.
Multiple stock locations, inventory detail, adjustments, reservations and shipping profiles per location. Sell from a warehouse and a shop floor without lying to either.
Price overrides, sales and customer-group pricing. Promotions with a real rules engine, grouped into campaigns you can schedule.
Per-region currency and tax, with payment methods assigned per region — cards in one market, bank transfer in another, from one catalog.
Roles and policies that actually change the shape of the app. Your warehouse staff and your finance lead see different products. Users, invites and API keys included.
Pages, articles, blogs and size guides as proper models with an editor, served straight by the storefront. No second CMS to pay for, host or keep in sync.
Around 30 sections and 12 templates, edited through a settings editor with real draft state. Two themes today: a clean baseline and Mehfil, built for couture and RTL markets.
A full inquiry model worked as a sales queue, fanning out to email and WhatsApp the moment it lands. For catalogs where a buy button was never the point.
Transactional mail on order placed, canceled, refunded, shipped and delivered. WhatsApp on orders and inquiries. Abandoned cart running hourly, sent once.
Orders, products and customers with period-over-period deltas and sparklines, computed from your own records. Reading your numbers should not require a third party.
AES-256-GCM with a versioned envelope. The API returns a masked hint, never the secret. Anything reaching a browser passes a fail-closed allowlist.
Per-product translations, a storefront locale switcher and country-scoped routing. Built in, not an add-on.
A view of what ran, when, and how it went — so a stuck refund is something you look at rather than something you guess about.
Fulfillments surface as shipments with tracking today, and DHL connects. Live rate quoting and label printing are in active development, with more carriers behind the same contract.
Predictive search, filters and the full search experience are built and shipping against database search. A dedicated engine slots in behind the same interface.
Insight cards ship today on the dashboard. A full reporting section — sales, conversion, cohorts — is the next surface to land.
Issuance, balance and redemption across the admin and checkout.
Company accounts, buyer hierarchies and quote-to-order, extending the draft-order flow already in place.
Recurring orders and plan management on top of the existing order lifecycle.
A way for third parties to add to the platform without forking it. Shape and timing are genuinely open — tell us what you would want to plug in.
Same contract every time: you supply your own credentials, we verify them against the live service before marking the connection active, and they’re encrypted at rest. No deploy, no developer, no support ticket. If a service you depend on isn’t here, that’s a useful thing to tell us.
Cards, Link, Apple Pay and Google Pay. Your key, resolved per request, verified against Stripe before it goes live.
On by default, assignable per region — the payment reality in markets where cards are not the default.
Every transactional email, plus newsletter sync. Your sending domain, your key, verified on connect.
Via Respond.io. Order and inquiry messages out of the box — the channel that actually gets read in South Asia and the Gulf.
Pixel on the storefront with server-side attribution. Verified against the Graph API on connect.
GA4 from your measurement ID. Shown as connected-but-unverified, because Google gives no way to confirm a tag is receiving traffic and we would rather say so than show a fake green check.
AWS, Cloudflare R2, DigitalOcean Spaces or self-hosted MinIO. Keeps you portable.
Connection and tracking today. Rates and labels in development.
Most platforms hold your payment credentials centrally. We resolve them per merchant, per request, which changes what happens on your worst day.
The storefront is composed from a section library rather than a monolithic template, so themes share the parts that should be shared and differ where it counts.
PostgreSQL underneath, S3-compatible storage for media, and a REST admin API with 184 operations — the same one our own admin uses. Nothing privileged is held back for us.
Worth being plain about, because you’re reading a page for a platform you can’t sign up for yet.
We’d rather build the right thing than the impressive thing, and the only way to know the difference is to ask people who sell for a living. Two minutes. The feature question is the one we care about most — and it genuinely moves the roadmap.
ClusaCart is what we’re building next. Commerce work is what we do now — Shopify themes and apps, custom platforms, integrations. Same engineers, available this week.