The category mistake most jewellery owners make
Walk into any tech-park demo room and you will see retail POS vendors pitching jewellery retailers with the same product they sell to apparel stores, electronics shops, and supermarkets. The pitch is seductive: "It is a proven retail platform; we will configure it for jewellery."
The configuration never quite works, because the core data model is wrong.
Generic retail POS systems are built around a deceptively simple idea: every product is an SKU with a quantity, a price, and a tax category. You scan the barcode, the system finds the SKU, the price is fixed, and the till adds it to the basket. The taxes apply at flat rates. The inventory drops by one. The day closes.
This works beautifully for a shirt that costs ₹2,499 with 12% GST. It works terribly for a 22K gold chain whose price changes every morning based on the MCX gold rate, whose making charge varies by design, whose value depends on its fine weight (not gross weight), whose tax is 3% on the gold portion, whose stones are taxed at a different rate, whose customer may be paying partly in old gold deposits, and whose final price line on the invoice requires four separate calculations the cashier should not be doing in their head.
What is missing in a generic POS that breaks jewellery retail
Daily rate-card management
Gold prices fluctuate every day based on global market movements. A jewellery retailer publishes a daily rate card by purity (22K, 18K, 14K) and metal (gold, silver). A generic retail POS either does not understand rate cards (every item has a fixed price), or supports rate cards as a manual lookup the cashier consults. Both are wrong. A jewellery ERP fetches the morning rate from MCX or the retailer's bullion desk, propagates it to all SKUs by purity, and prices every piece dynamically.
Component-level pricing
A jewellery invoice is a decomposition, not a fixed price:
``` Gold value = fine_weight × rate_per_gram_for_purity Making charge = gold_value × making_percentage OR flat_per_gram × gross_weight Wastage = gold_value × wastage_percentage (if applicable) Stone value = sum of (stone_weight × stone_rate) for each stone Sub-total = gold_value + making + wastage + stone_value GST = (gold_value + making + wastage) × 3% + stone_value × 0.25% TCS = sub-total × 1% (if cash payment > ₹2 lakh) Final price = sub-total + GST + TCS ```
A generic retail POS cannot do this without heavy customisation, and the customisation invariably breaks on the next vendor upgrade.
Customer-supplied gold and exchange
A returning customer brings in old gold to deposit against a new purchase. The old gold is tested for purity (often XRF-tested in-store), valued at today's rate minus a "polishing deduction" of 5-15%, and the exchange value is netted against the new sale. Some customers also bring loose stones to be set in new designs.
This is not a discount transaction. It is a barter transaction with tax and accounting implications. The exchange value must flow into the gold-stock ledger as a receipt, the deduction must be recorded, the new sale must be invoiced at the gross value with GST on the new gold supplied, and the customer's running ledger must update. A generic retail POS treats this as a "discount" line item, which is wrong and creates GST reconciliation problems at year end.
Karat-wise inventory
A generic retail POS tracks inventory as "300 chains in stock". A jewellery ERP tracks "180 grams of 22K gold value, 90 grams of 18K gold value, 12 carats of mounted diamonds, 4 carats of mounted coloured stones" — and ties this back to the physical pieces in the showcase. When the morning gold rate changes, the value of the entire inventory changes too. The retailer's working-capital-to-sales ratio shifts daily. None of this is visible in a generic POS.
Goldsmith and karigar workflow
A jewellery retailer's stock is constantly in motion: out to karigars for manufacturing, out to AHCs for hallmarking, in transit between branches, out for repair, out on approval to a wedding customer, in for melting and recasting. A generic retail POS has no concept of "stock on someone else's premises for a specific operation". A jewellery ERP has six or seven stock locations active at any time, each with its own reconciliation rhythm.
Customer profile that matters
Jewellery customers come back once every two to seven years. The salesperson needs to know: what they bought, when, what they paid, what their preferred style is, who their family members are (because Diwali and weddings are family events), and whether they have a gold-loan account with the retailer. A generic retail POS stores a name and a phone number. A jewellery ERP stores all of the above plus design preference, stone preference, special occasions calendar, and lifetime value.
The total cost of fitting the wrong shoe
A mid-size jewellery retailer (₹50 crore turnover, 3 branches, 8,000 SKUs) that runs on a customised generic retail POS typically incurs:
| Cost type | Annual estimate |
|---|---|
| Vendor customisation hours | ₹4-8 lakh |
| Workarounds (Excel layers, ad-hoc scripts) | ₹6-10 lakh in staff time |
| Reconciliation failures (gold leakage at 1-2%) | ₹40-80 lakh on a 12kg gold inventory |
| Compliance penalties / near-misses | ₹2-5 lakh |
| Lost sales from inventory-visibility gaps | ₹15-30 lakh |
| **Total hidden cost** | **₹70 lakh – ₹1.3 crore per year** |
A purpose-built jewellery ERP for the same retailer costs ₹15-30 lakh upfront and ₹3-6 lakh annually in support. The payback is usually within the first 9-12 months.
When generic POS is fine
Generic retail POS is the right answer for a jeweller who only sells gold coins, silver bars, and a small range of bangles with no stones. Coins and bars are quantity-and-rate transactions; the math is simple; there is no karigar workflow because there is no manufacturing. For a small retailer with under ₹5 crore turnover and a simple product mix, the simplicity of a generic POS may outweigh its limitations.
For everyone else — a jewellery retailer with stone-set pieces, karigars, multiple branches, customer exchanges, gold loans, and hallmarking — the generic POS approach is a slow-motion margin leak.
The jewellery ERP feature checklist
When evaluating a jewellery-specific platform, these capabilities should be visible in the demo:
- Daily rate-card sync from MCX or your bullion desk, with rate-card history
- Component-level invoice decomposition (gold, making, wastage, stones, GST, TCS)
- Karat-wise stock with fine-weight valuation
- Karigar issue-receipt workflow with approved wastage
- BIS AHC portal integration for hallmarking (covered separately)
- Customer-supplied gold exchange with proper accounting treatment
- Multi-branch stock transfer with in-transit visibility
- Gold-loan integration (if the retailer offers it)
- Customer 360 with purchase history, family relationships, and occasions
- GST + TCS auto-calculation at the till
- Aged-stock reports for design refresh decisions
- Auditor-ready compliance reports (BIS, GST, income tax stock register)
A jewellery ERP that handles 80%+ of this checklist out of the box will save a retailer 5-7 years of customisation pain on a generic POS — and is invariably cheaper in total cost over a three-year horizon.
FlowSense Jewellery ERP is purpose-built for Indian jewellery retail with all of the above as core features. For retailers above ₹10 crore turnover with stone-set inventory and multiple branches, the right question is not whether to switch — it is when.
