Built by people who already write software for gold
JewellerGen is made by SilverGen Technologies. Our other product, SilvERP, runs refining, trading and compliance for the precious metal industry — which is how we know that a jewellery counter needs its own software rather than a module of somebody else's.
A counter is not a warehouse with a till
We had an enterprise suite that could, with enough configuration, be made to issue a jewellery invoice. We also had a clear view of what that would feel like on a Saturday afternoon in a shop with three counters and a queue: too many fields, too many words nobody uses, and a system designed for someone at a desk.
So JewellerGen is a separate product with its own database, its own login, its own look and no dependency on anything else we run. If every other system we own were switched off tomorrow, your shop would keep billing.
That decision costs us duplication. It buys you a product that can be simple, because it only has one job.
Five rules we do not break
These are the actual engineering rules the team works to, not a values page. They are the reason some obvious shortcuts are not taken.
One shop's data never touches another's
Your stock, your customers and your rates are yours alone — invisible to every other shop using JewellerGen. The separation is enforced in four independent places rather than trusted to one. A single leak between two jewellers would end this product, and we build as though that is true.
Branch is enforced, not displayed
Staff are allocated to branches and the allocation is carried in the signed session. An empty allocation means no access, never all access — the default that quietly grants everything.
No untranslated string ever ships
Every visible word is a key with an entry in English, Hindi and Arabic. A missing key fails the build, so a raw identifier cannot appear on a counter screen in front of a customer.
Money and weight are exact
Decimals, never floating point. Three places on a gram, one on fineness, two on money. In a business where a gram is worth thousands, a rounding convenience is a leak.
The interface is for a salesperson, not an administrator
Task-first home, scan-first flows, three steps to a sale, plain words. "Store", "counter", "old gold", "rate today", "tag" — never "entity", "sub-inventory" or "counterparty". Defaults are pre-filled and advanced fields sit behind one disclosure. If a flow needs a fourth screen, the flow is wrong.
Small enough that you talk to the people who make it
You reach the team, not a ticket queue. What jewellers tell us genuinely changes what we work on next, and the people who answer you are the people who build it.
- We migrate your data with you — the first import is done together, not handed over as a template.
- We will tell you what it does not do. That conversation happens before you buy, not after.
- We do not invent proof. No borrowed logos, no invented customer counts, no testimonials from people who do not exist.
- Your data leaves when you do. A full export of everything you hold is a support request.
The other thing we make
SilvERP is SilverGen's enterprise suite for the precious metal industry — refining, trading, manufacturing, retail and compliance. JewellerGen shares no code path, no database and no runtime dependency with it. They are made by the same people; they are not the same product.
Come and argue with us
The most useful conversations we have are with jewellers who tell us where we have got it wrong. If that is you, we would genuinely like the call.