How to Run a Fast, Accurate Jewellery Stock Audit: A Step-by-Step Guide for Indian Jewellers

In most retail, an audit answers one question: is the item there or not? For a jeweller, presence is the easy part. The harder questions are: is this the same 22-carat chain you logged, and does it still weigh 18.420 grams? A piece can be physically present on the tray and still represent a loss if 2 grams of gold have been shaved off, a diamond has been swapped for a cubic zirconia, or a lighter design has been substituted under the same tag.

That is why a jewellery audit has to verify three things at once for every item: identity (the right piece), weight (down to the third decimal for gold), and condition (the actual photographed item versus what was recorded). An audit that only counts pieces will pass a tray that has quietly lost value. This is also the reason a count-only system or an RFID gate is not enough on its own: RFID confirms a tag is in the room, but it cannot tell you the weight changed or that the stone was switched.

Treat the audit as a value-verification exercise, not a headcount. Once you frame it that way, the whole process below falls into place.

Most audits fail in the preparation, not the counting. The day before you verify a single item, lock down the conditions so the numbers actually mean something. The single most important rule: freeze movement during the audit window. If pieces are being sold, exchanged or moved between the safe and the counter while you count, your closing figure will never reconcile.

Decide your scope and your reference point. Are you auditing the entire showroom, one category (say, only diamond jewellery), or one branch? And what is the source of truth you are checking against, your last system export or a fresh baseline? For a first proper audit, build a clean baseline first (covered in the next section) rather than trusting an old, drifted spreadsheet.

The baseline is the master record every physical piece will be checked against. The fastest way to create it is a bulk CSV import: one row per item, carrying at minimum a unique barcode, the item's baseline weight, and ideally a reference photo and category. If you already maintain item data in Excel or your billing software, export it, clean it, and import it once rather than typing items in one at a time.

Get the weight field right, because it is the backbone of discrepancy detection. Record gold and diamond pieces to three decimals (e.g., 18.420 g) and decide upfront whether the baseline weight is gross or net of stones, then stay consistent. Mixing gross and net weights across rows is the most common reason audits throw false discrepancies.

A reference image per item is what later lets the system catch a swap rather than just a weight change. If you do not have photos yet, the first audit doubles as your photo-capture run: staff photograph each piece as they verify it, and that image becomes the baseline for next time.

A 4,000-piece showroom audited by one person is a recipe for a week of fatigue errors. Split the work. Assign verification tasks by tray, counter, category or branch so each staff member owns a defined set of items and nobody double-counts or skips a section. With role-based permissions, a sales associate can be allowed to scan and record while only a manager can review and close discrepancies, which keeps the audit trail clean.

A realistic throughput to plan around is roughly 60-100 items per person per hour once people settle into the rhythm of scan, photograph, weigh, submit. So a 4,000-piece store with four staff working in parallel is a single morning's work (around 4,000 ÷ (4 × 80) ≈ 12-13 person-hours, so about 3 hours wall-clock with four people), not a multi-day shutdown. Build your schedule from your own item count and team size using that rate.

Assigning tasks digitally rather than on paper means you can see live progress (who has finished, what's pending) and the system records exactly who verified each item, which is the foundation of accountability.

This is the heart of the audit and it should be a tight, identical loop for every piece. On the staff Android app, the worker scans (or types) the barcode, captures a fresh photo of the item, places it on the scale and records the actual weight, then submits. Three pieces of evidence are now attached to that item: what it is, what it looks like right now, and what it weighs right now.

Behind the scenes the system does the comparison no human can do reliably at speed: it matches the captured photo against the baseline image and compares the recorded weight against the baseline weight. A piece that matches on both is marked verified and the staff member moves on, no manual sign-off needed. Anything that fails either check is flagged instead of silently passing.

Set a sensible weight tolerance before you begin. Scales and stone settling cause tiny variations, so a small band (for example a few hundredths of a gram, or a percentage you decide based on your scale's precision) avoids drowning in false alarms, while anything outside the band is escalated. Keep the photo station's lighting and background consistent so image matching stays accurate piece to piece.

A discrepancy is not an accusation; it is a question that needs an answer while the trail is fresh. The moment a mismatch is flagged, the admin gets an alert showing the item, the baseline versus recorded weight, and the baseline versus captured photo side by side. Resolving it the same day is what separates a real audit from a spreadsheet that just lists problems nobody chased.

Work discrepancies in priority order. A weight that is lower than baseline on a gold item is the most serious, that is potential shaving or substitution and deserves immediate investigation. A photo mismatch can mean a genuine swap, or simply a bad-angle/poor-light capture, so re-photograph before escalating. A 'not found' item means it is sold (check the day's bills), misplaced on another tray, out for repair/approval, or genuinely missing, in that order of likelihood.

An audit is only finished when every item lands in a final state: verified, resolved-with-reason, or confirmed-missing. Before you reopen the counter, run a quick reconciliation: total items expected, total verified, total discrepancies raised, and total resolved. A clean close means zero items left in 'pending'.

The lasting value of the audit is the record it leaves behind. A tamper-proof audit trail captures who verified each item, when, the recorded versus baseline weight, and the actual versus baseline image. That history is what protects you in a staff dispute, what an insurer or auditor will ask for, and what lets you compare this audit to the last one to see whether your shrinkage is trending up or down. Across a multi-branch chain, the same record rolls up into a per-branch report so you can see which location runs tight and which needs attention.

The right frequency depends on volume, value density and risk, not on a calendar rule someone gave you. The practical answer for most Indian jewellers is a layered cadence: a small daily or weekly spot-check of high-value items (loose diamonds, heavy gold sets), a fuller monthly verification of a rotating section, and a complete store-wide audit each quarter, plus before and after every major event.

Festival and wedding seasons deserve special attention. Stock balloons before Akshaya Tritiya, Dhanteras and the wedding months, and high footfall is exactly when swaps and errors slip through. Run a full count before the season to start from a trusted baseline, and another immediately after to catch anything that moved during the rush. When verification is a quick scan-photo-weigh loop rather than a manual count, auditing more often stops feeling like a shutdown and starts being routine, which is the whole point.

If you want to see this barcode + photo + weight workflow running on your own stock, you can book a demo, but even with pen, a calibrated scale and discipline, the steps above will make your next audit faster and far more trustworthy than a count alone.