Studio open4 Products in MarketMentziAurumOSDepoZerocodeAICTO Partner — VDOlocal5 Patents FiledBuilt for BharatBooking Q3–Q4 2026Studio open4 Products in MarketMentziAurumOSDepoZerocodeAICTO Partner — VDOlocal5 Patents FiledBuilt for BharatBooking Q3–Q4 2026
AurumOSTechnology

The Jewellery Industry’s ERP Problem — And Why Generic Software Always Fails

Tally and generic ERPs collapse in jewellery workshops because they cannot model gold. Why the industry keeps failing at software and what finally works.

Sitio Labs Team7 min read4 topics

A graveyard of abandoned software

Walk through any cluster of jewellery manufacturers in India and you will find a graveyard of abandoned software — Tally licences gathering dust, half-implemented ERPs, and spreadsheets that nobody updates. These businesses are not anti-technology; many have spent real money trying repeatedly. The pattern is consistent: enthusiastic adoption, mounting frustration, and a quiet return to paper within months. Understanding why generic software fails in jewellery is the first step to understanding what could actually work.

Gold is not a SKU

The core failure is that generic ERP and accounting software model inventory as discrete units with fixed prices — a SKU with a barcode and a number. Gold is fundamentally different: it is a fungible commodity measured in grams at a price that changes daily, transformed by labour whose making charges are tracked separately from metal value. When you issue 50 grams to a karigar and receive back a 47-gram finished piece plus 2 grams of dust, no SKU-based system can represent what just happened. Software that cannot model gold movement cannot run a jewellery business.

The making-charge and wastage gap

Even ERPs that bolt on a "jewellery module" usually stumble on the economics of the trade. A jewellery transaction separates metal value from making charges and wastage, applies different logic for old-gold exchange, and must handle purity conversions between 22-karat and 24-karat fluidly. Generic systems force these into clumsy workarounds — extra fields and manual calculations that defeat the point of automation. The owner ends up doing the real math on paper anyway, using the software only as an expensive typewriter for invoices.

Why Tally specifically falls short

Tally is excellent at what it was built for — accounting and GST — and nearly every Indian jeweller uses it for exactly that. The problem arises when owners try to stretch it into production, inventory, and karigar management, where it has no native model for job cards, gold issue-and-return, or piece rates. Tally tells you your financial position; it cannot tell you which karigar is holding 30 grams or which festival order is behind schedule. Asking Tally to run the workshop floor is asking a calculator to run a factory.

What jewellery-specific software gets right

Software purpose-built for jewellery starts from gold as a fungible, labour-transformed, daily-priced commodity rather than retrofitting that reality onto a SKU model. It treats job cards, karigar advances, making charges, wastage, and hallmarking as first-class concepts, and it integrates with Tally for accounting rather than trying to replace it. This is why generic ERPs fail and specialised platforms stick — one fights the industry’s reality, the other is built from it. For India’s jewellery manufacturers, fit beats features every time.

Frequently Asked Questions

Why does generic ERP software fail for jewellery manufacturers?

Generic ERPs model inventory as fixed-price SKUs, but gold is a fungible commodity measured in grams at a daily-changing price and transformed by separately-charged labour. Software that cannot represent gold issue-and-return and wastage cannot run a jewellery workshop.

Can Tally be used for jewellery manufacturing?

Tally works well for accounting and GST, which is why most jewellers use it for that. But it has no native model for job cards, gold issue-and-return, piece rates, or production tracking, so it cannot manage the workshop floor.

Why isn’t gold treated like a normal SKU?

Gold is fungible and measured in grams at a price that changes daily, and a piece’s value separates metal cost from making charges and wastage. Issuing 50 grams and receiving back a 47-gram piece plus dust cannot be represented by a barcoded, fixed-price SKU.

What should jewellery-specific software handle natively?

It should treat job cards, gold issue-and-return, karigar advances, making charges, wastage, purity conversion, and hallmarking as core concepts, not bolt-on modules. It should also integrate with Tally for accounting rather than replace it.

Why do jewellery ERP projects keep getting abandoned?

Owners adopt generic software enthusiastically, then hit workarounds for gold movement, making charges, and wastage that force them to do the real math on paper anyway. Frustration mounts and they return to paper within months.

More from AurumOS