How to Manage a Gold Scheme in Many Branches: Guide

A woman walks into your second branch on the fourth of the month. She joined your gold scheme at the main branch a year ago, she is near this shop today, and she wants to pay her instalment. Your staff here do not have her record. They take the cash, write a slip, and promise to phone the main branch. The main branch is busy. Two days later the payment is entered against the wrong slot, and next month a reminder goes to a customer who has already paid.

That one moment is the whole problem with running a scheme across branches. The way to manage a gold scheme in many branches is to stop keeping a book per branch and keep one shared record instead. Give every member a home branch, let them pay at any branch, set the rules once at head office, and give each role its own view. This guide shows how, with a worked example, the mistakes to avoid, and an honest note on when you do not need software for it.

What does managing a gold scheme across many branches mean?

It means two things stay true at once: every branch can serve any member in front of it, and head office can see the whole scheme on one screen. A branch handles its own members and takes payments from anyone. Head office sees every branch, the total, and the rules that hold them all together. One record sits underneath both.

Think of it as two different views of the same data, not two different books. The branch view is narrow and busy: this branch's members, this branch's collections today, this branch's overdue list. The head office view is wide and calm: all branches added up, one branch compared against another, and the rules that every branch follows. The figure below shows how those views split.

The rules matter as much as the record. A gold scheme is a promise that runs for many months, and the whole promise rests on every member being treated the same way. If you are still deciding what those rules are, our guide to how a gold saving scheme runs from joining to redemption walks through the terms you set once and then apply everywhere. Across branches, those terms cannot be a branch decision. They are a head office decision.

Why do separate books cause problems?

Separate books cause problems because a gold scheme is one promise, and a book per branch turns it into several. The moment a member can touch two branches, or money can move between them, two records that were never meant to disagree start to. Nobody is doing anything wrong. The setup is wrong.

Look at each leak and you will notice they are not branch failures. They are the gaps between branches. A member counted twice is not one branch being careless, it is two branches that cannot see each other. Cash that moves between branches with no entry is not theft, it is a transfer that no single book was built to record. This is the same pattern our guide on where a manual gold scheme leaks money describes for one shop, only now it happens in the space between shops, where it is even harder to spot.

The deepest of these is the last one: nobody owns the number. When the main branch says a member has paid ten months and the second branch's slip says eleven, who is right? On separate books, the honest answer is that you do not know, and you will spend an evening finding out. On one shared record, the question cannot come up, because there is only one number to begin with.

How do you manage a gold scheme across branches, step by step?

The method is five habits, and each one removes a leak from the figure above. None of them needs a large team. They need one record and one set of rules.

1. One scheme, one record. Every branch writes into the same record and reads from it. This is the founder's rule I hold to even for a small scheme: even two branches collecting for one kitty need one record, not two. It is the single change that removes most branch problems at once.
2. Give every member a home branch. The home branch owns the member's account, their reminders and their questions, usually the branch where they joined. Paying and redeeming can happen anywhere, but one branch is responsible, so two branches never both chase, or both ignore, the same overdue member.
3. Let members pay at any branch. A customer near your second branch will not travel to the first to pay. On a shared record the payment lands on the right slot the moment it is taken, with a numbered receipt, wherever it is taken. The daily habits behind this are the same as in our guide on tracking gold scheme payments every day, done at each counter.
4. Set the rules once, at head office. Grace period, due date, draw day, the late payment rule and what can be bought are decided once and locked for every branch. A branch that can change its own grace period gives two members on the same scheme two different answers.
5. Check across branches every week. Compare due against received for each branch, tick each branch's cash, UPI and card against its own proof, and read the overdue list per branch. A week is short to check. A month across every branch is the search that eats a weekend, as our guide on closing the monthly accounts in one evening explains for a single shop.

Matching payments correctly is the quiet job under all of this. When cash, UPI and card arrive at more than one counter, they still have to agree with one another and with the member's slot. If that word is new to you, our guide to payment reconciliation and the lists that must agree explains it in plain language before you scale it across branches.

Roles: who can see and do what

The heart of a multi branch scheme is that not everyone should see everything. A branch counter clerk does not need the total for all branches, and head office does not need to enter every receipt. Give each role the view its job needs, and no more. Here is a simple set of roles to start from.

Set roles once and the record protects itself. A branch clerk cannot change the scheme rules by accident, an accountant can pull every figure without touching a single payment, and only head office can run and lock a draw. This is one of the checks our buyer's guide to the best gold scheme software for jewellers tells you to ask every vendor about, because a tool that shows everyone everything is not ready for more than one branch.

A worked example: one member, three branches

All names and figures here are made up to show the method. Say you run a kitty of 100 slots at an instalment of two thousand rupees a month, across three branches: your main branch, a second branch across town and a small third branch.

A member joins slot 34 at your main branch, so that is her home branch. In month three she is near the second branch and pays there by UPI. On one shared record, that two thousand rupees lands on slot 34 at once, a numbered receipt reaches her on WhatsApp, and the main branch sees the payment without a phone call. On separate books, the second branch writes a slip and the main branch enters it two days later, if it remembers.

In month seven slot 34 wins the monthly draw. The draw is run and locked by head office, so all three branches, and every member, see the same result at the same moment. Her remaining instalments are now covered by the shop, and that shows on her record everywhere, not just at her home branch. The fairness rules behind a draw like this are in our guide on running a lucky draw members can see is fair.

At maturity she is near the third branch and wants to collect her gold there. Because every branch reads the same record, the third branch sees her full history, her payments at two branches, her draw win and the value due, and hands over the gold. On separate books the third branch would have to call the main branch and make a paying customer wait at the counter, which is the worst place to lose her trust.

What about running more than one scheme across branches?

Many jewellers run this year's kitty while selling next year's, and larger shops run different schemes for different customers. That is a related but separate question, and it stacks on top of everything above: each scheme keeps its own rules and its own slots, while each branch still serves any member of any scheme. Our guide on starting more than one kitty scheme covers the settings that can differ between schemes. The branch rule does not change: one record per scheme, read and written by every branch.

Common mistakes across branches

• A register in every branch. The most common mistake and the root of the rest. Two books that describe one scheme will always drift apart.
• Letting branches set their own rules. A different grace period at each branch means members compare notes and lose faith in the scheme.
• No home branch. Without one branch responsible, an overdue member is either chased by two branches or by none.
• Moving cash between branches with no entry. A transfer that is not recorded is a hole that only shows up at month end, when nobody remembers it.
• Head office reading totals only at month end. A branch drifting off track is cheap to fix in week one and expensive to fix in week four.
• Giving every branch the full view. More access is not more control. It is more ways for a number to be changed by someone who did not need to touch it.

The mistake with the longest tail is a branch that quietly serves customers worse than the others, because head office cannot see it. A slow, doubtful branch is one of the reasons in our guide on why customers leave a jewellery shop, and across branches it hides until the customers are already gone.

When you do not need multi branch software

Be honest about this before you spend. You may not need branch software at all. If your two branches are a short walk apart, run by the same owner who is at both every day, and almost every member pays at the branch where they joined, a single shared record can be a clean spreadsheet that one trusted person keeps. The rule that matters is one record, not one particular tool.

I build software and I still say it: the software does not run the scheme, trust does. A two branch scheme with one careful person and one shared file is in better shape than a ten branch scheme with a tool nobody checks. Software earns its place when payments arrive from home, when branches are far apart, when more than one person edits the record at once, or when a member expects to walk into any branch and be recognised. Below that, the habits above are enough.

Do you need software, and how GoldKitty does it

Once there is more than one counter, one shared record usually has to be software, because two people cannot safely edit one spreadsheet from two places all day. This is the point our comparison of paper, Excel and software for gold schemes calls out: even a small scheme needs software the moment two branches collect for it.

That is how GoldKitty, our gold scheme software, is built. One scheme runs on one shared record. Each branch records its own cash and counter UPI, in app payments land on the right slot on their own, and everything sits in one reconciled list, so no branch keeps a separate book. Roles decide who sees what, from branch counter staff up to head office. The dashboard shows collections against expected, overdue slots and winner cover across every branch, and the reports come as CSV or PDF for your accountant. Draw results are confirmed with a one time password and lock for everyone at once, so no branch can question the outcome. For the wider case, read why jewellers are moving the kitty to software.

GoldKitty is modular. It is set up for each shop according to its country and its offer, and payments run through local payment gateways integrated for that market, which matters when your branches sit in different places. It is white label, so members only ever see your store's name, at every branch. There is no published price. Pricing is given after a demo on your own scheme, and it is one of the products appico builds and maintains, so it has a running cost after launch worth asking about at the demo.

Our take

Most branch trouble is not a branch problem. It is a record problem wearing a branch costume. Two branches that share one record and one set of rules behave like one shop with two doors. Two branches that keep two books behave like two shops pretending to run one scheme, and the customer feels the gap.

Start with the record, not the software. Decide today that there is one scheme record and head office owns the rules. Give every member a home branch and let them pay anywhere. Check every branch each week. If the weekly check keeps growing as you add branches, you can watch your own multi branch scheme run in a demo on your own numbers. Either way, the member gets what she pays you for every month: to be known at every branch, not just the one where she signed up.

Frequently asked questions