Per-branch stock and numbering
Each branch holds its own parts stock and its own invoice and job number series, so the two counters never collide.
Multi-branch
Run Every Branch From One Account
Separate counters, separate stock, one consolidated view.
The second branch is where informal systems collapse. Stock that was 'on the shelf' is now on someone else's shelf, the numbering series collides, and the owner loses the daily feel for takings that a single counter gave them. PhoneMistri keeps branches operationally separate but financially consolidated.
Recorded stock transfers
Parts moving between branches are transferred rather than silently disappearing from one book and appearing in another.
Consolidated owner reporting
Takings, repair volumes, technician productivity and stock value across every branch in one view, or filtered to a single one.
Staff scoped to their branch
Counter staff see their own branch. Managers see theirs. Owners see everything.
What breaks when the second branch opens
The failure is rarely dramatic. It is a customer told a part is unavailable while the same part sits at the other branch, a technician's payout calculated from the wrong branch's tickets, and an owner who no longer knows which counter is actually making money.
Separating branches operationally while consolidating them for reporting is the whole requirement. Neither one alone is sufficient — fully shared stock creates chaos at the counter, and fully separate systems leave the owner blind.
Comparing branches honestly
Raw takings mislead when comparing a high-street counter with a market-lane one. Repair volume, average ticket value, parts margin and rework rate together give a much truer picture of which branch is well run.
Because customers are held centrally, it also becomes visible when someone drops a device at one branch and collects at another — a service you can only offer confidently once the record is shared.
The comparison worth running monthly is margin per technician-hour rather than revenue. A branch turning over less but running a leaner bench is frequently the better business, and revenue alone will never show it.
Who sees what
Multi-branch operations fail on access control as often as on stock. Counter staff given a full view will, sooner or later, quote a customer from another branch's pricing or move stock informally between locations.
Access here is scoped by role and branch. Counter staff work within their own branch. A branch manager sees their branch's tickets, stock and daily reconciliation. Only owner-level accounts see the consolidated picture and the cross-branch reporting.
That scoping matters commercially as much as operationally: it is what lets you hand a manager real responsibility for their counter's numbers without exposing the whole business.
Opening a third branch
The jump from one branch to two is a systems problem. The jump from two to three is a management problem — an owner can personally hold two counters in their head and cannot hold three.
What changes is the reporting cadence. At three branches the useful artefact is a weekly comparison across counters rather than a daily feel for takings, because no owner is physically present at all of them any more.
Setting up branch-level reporting before the third counter opens is considerably easier than retrofitting it during the scramble that follows.
Where PhoneMistri helps during the day
The product is built around the points where repair teams usually lose time: intake, handovers, parts, approvals, QC, payments, and customer updates.
Unlimited branches on the higher plans
Cross-branch stock visibility before turning a repair away
Per-branch daily cash reconciliation
Branch comparison on volume and margin
Central customer database across branches
One login for the owner, scoped logins for staff
Frequently asked questions
Is there a limit on branches?
Multi-store is available on the higher plans. Contact us with your branch count and we will confirm which plan fits.
Can a customer drop at one branch and collect at another?
Yes. The customer and ticket records are shared, so any branch can look up the job and complete the handover.
Do branches need separate GSTINs?
If your branches are registered separately, each branch carries its own GSTIN and invoice series. If they operate under one registration, they can share it.
Can I stop one branch seeing another's data?
Yes — staff access is scoped to their branch by default, and only owner-level roles see the consolidated view.
Start with a repair workflow built for growth
Track every device, manage inventory, serve teams in their preferred language, and connect repair work with online sales in one place.