One stock, every channel
Website, app, store counters and marketplaces sell from one count, updated as each sale lands.
- Website
- POS
- Marketplace
The core five
The systems every
store runs on
With Commerce Engine, you can:List it everywhereSell once or on repeatCapture money anywhereGet it deliveredSell at the counter
Growth suite
And everything you
grow with after that
Customers, loyalty, marketing, promotions and reporting run on the same records the core five write to — so a campaign already knows who bought what, and when.
Questions
What teams ask
before they build
Nine suites on one engine raises the same handful of questions every time. These are the answers we give on the first call.
Is Commerce Engine headless, or does it come with a storefront?
Both, and you pick. Every capability is a REST API first, so you can build any front end against it — or start from a production storefront starter for Next.js, React, Astro or SvelteKit. If you would rather not build a checkout at all, use Hosted Checkout. Browse the starters
Do we have to adopt all nine suites?
No. Wire the suites you need and let the rest sit quietly until you want them. They all read and write the same records, so turning one on later is a configuration change rather than a migration.
Does it handle B2B as well as D2C?
One engine covers both. B2B customer groups, KYC validation and multi-warehouse stock run alongside ordinary D2C checkout, on the same catalog, order and customer records — so you are not maintaining two platforms to serve two kinds of buyer.
How do the suites stay in sync with each other?
There is nothing to sync. One data model and one event stream sit under all of them, so a capture, a loyalty accrual and a shipment are events on the order you already have — and 100+ signed webhooks fire the moment state changes, instead of a nightly export. Read the API reference
What does a developer get on day one?
A sandbox, a typed SDK and a project that already talks to the API. One command scaffolds a starter on your framework — client, session handling and environment written for you — or writes the Commerce Engine layer into the repo you already have. Storefront quickstart
Can our AI coding agents build against it?
That is a first-class path, not an afterthought. Installing the Commerce Engine skills teaches an agent the platform, the docs publish an llms.txt for machine reading, and every SDK surface is typed — so what an agent writes type-checks against the real API before it ships.
Which payment methods and gateways are supported?
Cards, UPI, wallets, net banking and pay-later sit behind one PCI-compliant flow, across multiple gateways. A failed authorisation reroutes to the next gateway before the customer notices, and captures, refunds and payouts reconcile against the order rather than a separate ledger. Payments in detail
Is there a free plan?
Yes — the Free plan costs nothing, needs no credit card, and every plan gets every online feature and a sandbox from day one. Paid tiers start when you outgrow it, and the pricing page lists exactly what each one includes. Compare plans
Do we have to replatform to get started?
No. Point one flow at Commerce Engine — checkout, loyalty, shipping, whichever hurts most — and run it alongside what you have. Because every suite shares the same records, expanding later costs configuration, not another migration project.
Can we keep our CMS, ERP and warehouse systems?
Yes. Content stays in your headless CMS and syncs in real time, carriers and 3PL partners connect once and then rate-shop per shipment, and everything else integrates against the same REST API the storefront uses. See the catalog's CMS sync
Still deciding? The docs cover the API surface end to end.Read the documentationBook a demo
Start with one suite
Grow into all nine
Open a free store and wire up the suites you need. The rest share the same records, so adding one later is a setting, not a migration.