| Product | Expected | Counted | At cost |
|---|---|---|---|
| Stud, Plain, 22K, 3 g | 8 | 7 | −₹43,340 |
| Coin, Lakshmi, 24K, 1 g | 28 | 29 | ₹15,140 |
| Nose pin, Diamond, 18K | 9 | 8 | −₹9,580 |
16 Stories from the shop
For everyone
- How the ideas and screens in this guide fit together in a shop’s year.
- What to do in situations every jeweller meets.
These are moments from Jholok Jewellers’ year. The figures are the demo shop’s own, so you can open the app’s demo and find each of them.
16.1 The first full count
Bidisha decided to count the whole shop at the end of the financial year, before opening on 14 April. She had set up People the week before (Chapter 4): Ramesh and Meena to count, Sita to approve.
Ramesh started the count in the Count tab, with All types, and he and Meena counted tray by tray, each signed in with their own PIN (Chapter 8). Neither could see what the ledger expected. They finished in two hours and Ramesh submitted.
Sita opened Review. 39 of 42 matched (93%). These didn’t:
The shortages waited under Recount first, so Sita recounted them herself, blind. They were still short, and she found no missing sale to explain them. She recounted the coins too, checked that no delivery of coins was missing, and accepted the extra one. She ticked all three and completed the count with a reason, signing with her PIN (Chapter 13). Each accepted difference became a count adjustment in the ledger.
The lesson: the first count sets the baseline. From then on, every count is compared with the last one of the same types.
16.2 Dhanteras
On Dhanteras, 1 November, the shop sold 71 coins in one day:
| Coin | Sold |
|---|---|
| Coin, Lakshmi, 24K, 1 g | 45 |
| Coin, Silver 999, 10 g | 13 |
| Coin, 24K, 5 g | 10 |
| Coin, Lakshmi, 24K, 10 g | 3 |
Every sale was recorded as it happened, so the ledger kept up. The Overview’s sales chart labelled that week with its festival (Chapter 7), and Needs attention lists any product that, at its new pace, won’t last the supplier lead time.
The lesson: after a rush, count what moved fastest. Busy days are when a sale is most easily missed.
16.3 The pendant below zero
The Overview showed one product Below zero: the Lakshmi pendant, at −1. Its last movement was a sale on 4 Oct, with the note “Walk-in, receipt of 6 not yet entered”.
The pendant had sold out, a delivery of 6 had arrived, and a customer bought one before anyone entered the delivery. Bidisha opened the pendant and tapped Receive, entered 6, and set the date to the day the delivery came. The stock became 5, and the warning went away (Chapter 6).
The lesson: below zero always means a missing movement. Find it, enter it with its real date, and the stock is right again.
16.4 The customer’s repair piece
At the count at Showcase 1 on 26 September, the hammered hoops came out one pair over. Sita, approving, didn’t accept it straight away: an over usually means a missing record. Ramesh, who led the count, told her why: a customer’s repair piece had been left in the tray.
The extra pair wasn’t the shop’s stock at all, so Sita left the line unticked. The hoops’ stock didn’t change, and the Result lists the line under Left unchanged (Chapter 14).
The lesson: keep customers’ pieces out of the trays, or mark them, and never make stock up to a count without asking why.
16.5 The karigar’s chain
A chain (Rope, 22K, 18 in, 10 g) had gone to Ramesh karigar for repair, memo K-17, due back in 30 days. By then it was 14 days late, and the Overview’s Needs attention listed it: “1 memo more than a week overdue” (Chapter 6).
Bidisha called the karigar. The chain had come back the week before and was already in the showcase, but nobody had recorded it. Sita opened the chain, tapped ⋯ beside the memo under Off the shelf, chose Back in, set Back on to the day it came back, and signed with her PIN. The chain was in the shop again, and the next count expected it on the shelf (Chapter 12).
The lesson: record pieces back in when they come back. Otherwise the next count finds them “over”, and the overdue list keeps nagging.
16.6 A new member of staff
When a new assistant joined, Bidisha added them in Settings → People as a Counter, and let them choose their own PIN (Chapter 4). Their first count was a small one, the rings in one showcase, with Ramesh beside them to show how + and the number pad work, and how − and Undo put a slip right.
Counting is blind, so the ledger couldn’t sway the new counter. And a counter can never approve a count. The activity log shows each figure they entered.
The lesson: start new staff on small counts. The app’s rules protect the shop and them: nobody can be blamed for a figure someone else entered.
- Count the whole shop once to set a baseline; then count often, a few types at a time.
- Record every movement when it happens, with its real date.
- A difference is a question: below zero, over and short each have a usual cause worth finding.
- Record pieces back in when they come back from jangad or the karigar.