Opening
Two branches share an invoice series and GST numbering collides.
For multi-location retail
One set of books across every branch.
Branch naming series, transfers and stock parity, with an access check that makes sure no one quietly widens their access.
You know this week.
Midday
A transfer shows in one branch and not the other.
Closing
A branch manager was given Stock Manager to “fix one thing” and still has it.
In your words.
“Separate naming series for each branch”
“Stock transfer approval above ₹50,000”
“Daily branch-wise sales on WhatsApp”
“Branch managers can’t edit prices”
“Show stock parity across branches every Monday”
Where to start.
rung1 Enterprise
Change ERPNext by asking. Nothing lands unchecked.
rung1 Commerce
Price, stock and refund changes that reconcile to your books.
The access check (G3)
Any change that would widen someone’s access is refused, however small, and you’re shown exactly who would have gained what.
Illustrative · design preview
The objection we hear most
“Our branch staff need flexibility.”
They can ask for anything. What they can’t do is quietly gain access that nobody approved.
Further reading
- AI changes
What is an ERP change gate?
- Tally
Tally vs ERPNext: when to switch, and how to migrate safely
- For CAs
DPDP Act for SMEs: what to do before 13 May 2027
Start with one process. Add the next when it holds.
10 design-partner slots for Phase 1. 90 days free, onboarding done for you, a named founder on WhatsApp.
Not for service firms under ₹1 crore, firms above ₹250 crore, or anyone whose CA won’t take a call.