Vowerole

Founder

Aman Kumar Singh

Aman Kumar Singh is the Founder and Lead Software Architect behind Vowerole. With years of experience designing enterprise software, distributed systems, cloud-native platforms and ERP solutions, he created Vowerole to help jewellery businesses across India streamline billing, inventory, manufacturing, CRM and retail operations.

Founder and Lead Software Architect · Vowerole · Noida, India

The Vowerole journey

Vowerole started from a specific observation about jewellery software: almost all of it stores stock as a quantity somebody can edit, and almost all of the pain a jeweller has with it follows from that one decision. A stock figure that cannot be taken apart into the entries that produced it is a figure nobody can defend at a stock take.

So the platform was built the other way round. Stock is an append-only ledger of movements; a balance is a projection of it. The weight identity that a jewellery business lives or dies by — gross at least net plus stone plus other — is a database check constraint rather than a form validation, so it holds for the import, the API and the offline counter as well as for the screen. Pricing and weight conversion are compiled packages that run identically on the server, in the browser and on the desktop counter, so the three cannot disagree about what a piece costs.

The rest of the product — GST invoicing, purchase, manufacturing and job work, karigar accounts, girvi, savings schemes, the catalogue website, the customer app — is built on that ledger rather than beside it. That is the whole design, and everything else is a consequence of it.

Engineering decisions

A ledger, not a stock column

Every movement of metal writes an append-only entry, and a balance is the sum of those entries rather than a number kept in step by hand. It is more work to build and it is the only version where a discrepancy can be taken apart and explained.

The weight identity belongs to the database

Gross must be at least net plus stone plus other, to a milligram. That is a check constraint, not a form validation — so it holds for the bulk import and the offline sync too, not only for the screen somebody remembered to guard.

One set of maths, three runtimes

Pricing and weight conversions are compiled packages that run on the server, in the browser and on the offline desktop counter. The three cannot disagree about what a piece costs, because there is only one implementation.

Offline-first, not offline-tolerant

The counter reads and writes to its own encrypted database first and treats the network as a background detail. A jeweller during a festival rush cannot stop billing because a line went down — that was the design constraint before a line of it was written.

Featured project

Vowerole — Jewellery ERP

A multi-tenant jewellery ERP, POS, manufacturing, girvi and commerce platform: NestJS and PostgreSQL with row-level tenant isolation, Next.js server-rendered product surfaces, an offline-first Electron counter over an encrypted local database, and a per-shop customer mobile app.

Get in touch

Questions about the architecture, or about the product

Either reaches the same person.

Talk to the person who built it

A walkthrough of the software, or a conversation about how it is put together.