One catalog, price and stock source
The storefront, admin and POS read the same catalog, prices and stock, so a change is made once.
A moat is a structural advantage: something that is part of how the platform is built, not something you bolt on later. Each of the 43 below was checked against the product as it runs today, and where a capability has a limit, the limit is written next to it. Anything that is only planned lives on the roadmap, not here.
How to read the impact labels
The storefront, admin and POS read the same catalog, prices and stock, so a change is made once.
Checkout reserves stock first. If it is not there, no order or payment attempt is created.
Products carry variants, and names and descriptions can be stored in nine Indian languages, falling back to English when a translation is missing.
Build customer segments from order count, lifetime value, tier, points and location, and use them in journeys and on the storefront.
Lot and serial numbers travel with receipts, picks and stock movements, and expiring batches can be looked up.
Trade customers get a portal with their own prices, quotes, purchase orders, approvals, credit terms and invoices.
Recurring orders from weekly to yearly, with trial days, and a billing job that retries failed charges before marking the subscription past due. No proration yet.
Onboard sellers, approve their listings, set commissions, settle on delivered orders and work disputes from one admin.
The register queues completed sales on the device and sends them when the connection returns. Offline limits are settings only and are not enforced yet.
Receiving, putaway, counts, transfers and wave picking run on the same stock the storefront sells from.
Send orders to a warehouse, store or carrier using first-match rules and pincodes, and test the rules before they go live.
Marketers build pages from blocks and show or hide a block by segment, country, device or date window.
Message flows with triggers, waits, conditions and actions that send through the SMS, WhatsApp and email providers you already use.
Design a flow that searches the catalog, adds to a cart and sends a payment link. Language-model intent detection is not connected yet.
Fuzzy matching, synonyms, redirects and ranking weights, with a meaning-based fallback when keywords find nothing.
Weighted rules score each new order as allow, review, hold or block. Scoring runs after the order is created.
Register your own model provider keys, set spend budgets, and block personal data or risky prompts with rules you choose.
Ask questions about orders, catalog and analytics in plain language. It reads live data as you and cannot change anything yet.
The admin and its backend share types, and inputs are validated with Zod, so type mismatches surface when the code is built.
Rooms, rates and reservations, and event tickets with QR check-in, live in the same system as the rest of your business. Both are foundations, not finished suites.
Roll a feature out to a percentage of visitors for one business or all, and switch it off again. Changes take up to about a minute to spread.
Run on a shared multi-business Worker with your own domain and theme, or on a dedicated Worker of your own.
Pages are cached close to shoppers and purged by tag, so a change reaches visitors without clearing the whole cache.
Time limits, circuit breakers and cached fallbacks keep search responding when a dependency is slow or failing.
One-time importers for OpenCart (categories, products, customers, orders), Shopify and Wix products, plus catalog scrapers. These are imports, not a live sync.
Products, orders, inventory and customers can be read through the REST API with scoped keys, so your data is not locked behind the admin.
Queries are scoped to the business in the application layer, with a CI check that fails the build on new unscoped queries, row-level security policies are defined in the database, and dedicated-database tenants are isolated at the instance level. The security page states the limits.
POS card machines connect through a payment hub that never holds card data, and a sale completes only after the machine approves it.
Each business's backup is encrypted with its own key, and point-in-time snapshots can be restored from the admin.
A data processing addendum is published on this site (see the DPA page).
Publish your catalog as feeds for Google Shopping, Meta, Instagram, TikTok, Pinterest, Bing, Snapchat and Meesho.
Pull Amazon and Flipkart orders into your order system on a regular poll. eBay and Etsy connectors are planned.
Country profiles carry the currency, default language, address format, delivery partners and payment methods for each market.
Shoppers can add the storefront to their home screen from the browser, and it can be packaged as a mobile app.
A versioned REST API for products, orders, inventory, customers, feeds and webhooks, limited by the scopes you grant.
Let apps connect with OAuth 2.0 (authorisation code with PKCE, refresh tokens or client credentials) or issue keys you can rotate.
HMAC-signed deliveries, a log of every attempt, three tries and a dead-letter list retried after ten minutes.
Let an AI tool search your catalog, read products and create orders through a scoped MCP connection.
A hand-maintained OpenAPI 3.1 description and a small TypeScript client. There are no official Python, Go or Ruby clients.
Adapters for payments, carriers, messaging, ads and accounting that your business connects with its own credentials.
Events are saved with the change that caused them, signed, and retried with a growing delay if the partner is down.
Growth and Scale list prices are published on the pricing page, and Enterprise is quoted from a published starting price.
The roadmap page separates what is in progress from what is only planned, instead of presenting plans as shipped.
This list covers only what we could confirm in the product today. It is not a complete inventory, and a capability that is only planned is not on it. When the list changes, it is because something was checked, not because a number needed to be reached. Subscribe to hear about releases.
QuantumOS Dispatch
Insights for commerce operators
Operator stories, platform deep dives and notes on what ships.
We'll send the QuantumOS Dispatch by email. Unsubscribe any time. See our privacy notice.