A quick-commerce storefront for every ERP tenant
A Blinkit-style installable storefront each ERP company can switch on, where an accepted order becomes a GST sale bill inside the ERP.
- Client
- Tatva ERP customers
- Sector
- Retail and distribution
- Shipped
- 2026
- Practice
- Product and platform engineering
Tatva Shop is a quick-commerce storefront for businesses already running Tatva ERP. Any ERP company can switch on its own branded shop, served on its own subdomain or a custom domain, which customers install on a phone as an app. Orders are managed inside the ERP: accepting and packing one turns it into an ordinary sale bill, so stock and GST stay in a single system rather than being reconciled between two.
The problem
A shop that sells online and offline usually ends up with two systems and a reconciliation problem. The website knows about orders, the accounting software knows about bills, and somebody types between them, which is where stock drifts and GST filings go wrong.
What we built
- 01
One storefront codebase serving many tenants, resolved by subdomain, with a custom domain where a business wants its own.
- 02
A progressive web app rather than a native build, so a customer installs it from a link with no app store and no review cycle.
- 03
Orders modelled as ERP documents from the start, so accepting and packing an order produces a normal sale bill.
- 04
Per-tenant branding and catalogue driven from the ERP's existing item master, so nothing is maintained twice.
- 05
Deployment alongside the ERP it belongs to, with its own process and its own certificates.
What it does now
- An ERP customer gets an online shop without buying or integrating a second system.
- Stock and GST live in one place because the order becomes a sale bill.
- Customers install the shop from a link, on Android and on iPhone.
What people ask about this work.
Why build a PWA instead of a native shopping app?
Because the install friction is lower and the release cycle is shorter. A customer installs a progressive web app from a link on Android or iPhone with no app store listing and no review wait, and an update ships the moment it is deployed. For a shop whose catalogue changes weekly, that matters more than the handful of native capabilities given up.
How does an online order avoid being entered twice?
By making the order an ERP document from the beginning rather than importing it later. When staff accept and pack an order in the ERP, it becomes an ordinary sale bill, so stock movement and GST are recorded once in the system that already owns them.