Your brand.
Your store.
Your rules.
Its own domain. Its own catalogue. Its own customers. One commerce engine underneath, and only the parts you need.
Everything you sell.
Nothing you don’t.
Good brands don’t need more software. They need a store that gets out of the way of the sale.
Sell what matters.
Products, variants, categories, collections, media and inventory — one model, whether you sell jewellery, skincare or whatever you launch next.
See the modules →Make it your brand.
Your logo, your colours, your domain, your words. Branding is data, not a deploy — used exactly as you supply it, never cropped to fit a slot.
Make it your own →A store. Not an install.
One deployment, any number of brands. Each one a database row. Nothing about starting another needs an engineer.
Meet the brands →Every brand gets
its own front door.
A storefront is a row, not a re-platform. Nothing about starting one needs an engineer.
Three brands.
Three domains.
One engine underneath, and none of them wearing our name in the address bar.
Made-to-order, priced on request
A jewellery house with ring sizes, gold rates, certificates and gift wrapping — the full atelier flow on the engine.
Commerce with a charity module
A gifting brand with the optional giving module switched on — every order carries a cause, tracked in the ledger.
38 products across five ranges
A herbal skincare brand with a full catalogue — five ranges, concern and ingredient filters, ready for launch.
Three brands run on the platform today, each on its own domain with its data walled off from the next. The list grows as they do.
The guarantees that
live in the database.
Most platforms ask you to trust the interface. These rules live in Postgres instead.
One brand can’t read another.
Every row is scoped to its store by row-level security. A bug in one brand cannot leak another brand’s orders or customers.
Prices are computed server-side.
Every price, discount, gift card, shipping and tax figure is calculated in the database. The browser only ever holds an unguessable cart token.
Every decision is logged.
Orders, fulfilments, refunds and admin actions are written to an audit log per store — so what happened to a brand can be accounted for later.
What is running
today.
Live means in production now. In build means in active work. Nothing else is on this page.
Live
- Multi-store catalogue — products, variants, categories, collections, media
- Server-computed cart, discounts and gift cards
- Checkout with Razorpay, UPI, cards and cash on delivery
- GST invoicing with per-store HSN, tax rate and numbering
- Orders, fulfilments, returns and refunds, with an audit log
- One dashboard across every store, with store-scoped staff roles
- Database row-level isolation between brands
- An optional charity-giving module, per store
In build
- Self-serve store creation and domain pointing
- Courier integration and pincode serviceability
- Product reviews and ratings
- A hosted theme editor for brand colours and layout
Anything on neither list is not built yet, and will arrive on the left with a date rather than here as a promise.
Make room for
something you sell.
Three moves from a brand name to a live checkout.
Add the store.
Name the brand, set its tax and shipping, point its domain. It inherits the whole engine immediately.
Load the catalogue.
Bring in products, images and collections. Price now, or keep them price-on-request until launch.
Switch on checkout.
Connect Razorpay and a courier, flip the store live, and start taking orders — reporting flows into one dashboard.
Before you start.
Do I need a developer to add a brand?
No. A store is a database row rather than a separate install, so naming it, branding it, setting its tax and choosing its modules all happen in settings. Nothing waits on a deploy.
Can each brand use its own domain?
Yes. A store starts at an address on intentconvert.com and moves to a domain you own whenever you’re ready. The original address keeps working until the new one is verified.
How is one brand’s data kept from another’s?
By row-level security in Postgres. Every product, order and customer row is scoped to its store, so a bug or a mistake in one brand cannot surface another brand’s data — it’s enforced in the database, not by hiding a link.
Is it built for Indian commerce?
From the first line. GST invoicing with per-store HSN and rate, Razorpay and UPI, cash on delivery, and courier hooks are part of the engine rather than add-ons.
What does it cost?
Starting a store is the plan every new brand is on — the full engine, your own branding, and an address on intentconvert.com. A white-label arrangement on your own domain is the paid tier, and we haven’t fixed a price for it yet.
One engine for every brand you’ll ever launch.
See IntentConvert running three live brands — and how fast the fourth goes up.