One Pia. Many shops.

The first shop is hard. The second shop is harder than the first one twice over. Every chain owner knows this, and every piece of software built for single-shop owners pretends not to.

This post is about the work that multiplies when you open the second shop, the third, the eighth. It's about what stays the same. And it's about what the daily reality of a multi-shop owner looks like when the assumption all the way down is that you have more than one.

The work that multiplies

Open shop number two and a list of things you used to do once a day, in your head, becomes a list of things you do twice a day, never quite in your head, and never quite at the same time.

• Cash reconciliation. Two tills. Two staff handovers. Two cash bags that have to balance. Two stories about a missing ₹400.
• Stock movement. Branch A is running out of Dolo. Branch B has more than it needs. Either someone notices, or someone doesn't. Either a customer leaves empty-handed, or two months later you find the strips have gone past expiry.
• Staff coverage. Ravi calls in sick at branch B. Who covers? You used to know. With two shops you still know. With five you don't, not without writing something down.
• Supplier pricing. The same distributor is quoting ₹24.20 to branch A and ₹24.80 to branch B, depending on which manager picked up the phone. You won't catch it for three months. By then you've lost ₹40,000 you didn't have to lose.
• Compliance. Each shop has its own GSTIN, its own drug license, its own Schedule H register, its own expiry-checks logbook. Three of them are due for renewal this quarter, and you remember only because your CA reminded you Tuesday.
• The owner's attention. Twenty-four hours don't multiply when the shops do. You stretch the same attention thinner, and the thinnest stretched parts are where things go quietly wrong.

Most pharmacy software cannot help with any of these honestly. They were built for the single shop. The multi-shop "module" is a checkbox added in 2018 and a price multiplier added in 2020. What it actually does is run the same software N times, isolated, with a "consolidated report" screen tacked on the end. That isn't multi-shop software. That's single-shop software run N times.

The work that doesn't multiply

There's a smaller list, and it's the one worth dwelling on.

• The brand of the shop. Whether your chain stands for fair prices, friendly counter staff, and never running out of basic medication — that's the same across every branch. It either is true or it isn't.
• The accountability standard. What "we don't sell expired stock here" means at branch A means the same at branch H. The standard doesn't multiply; the enforcement does.
• The owner's intent. What you decided about the business when you opened the first shop — who you're for, what you'll never do, what trade-offs you've already made — doesn't get rewritten when you open the second. If anything, it has to hold harder.

These don't multiply, but the consistency-keeping work does. Every new branch is a new opportunity for the brand to drift, the standard to slip, the intent to soften. The chain owner's actual job — once the second shop is open — is to hold the line on these without being in every shop every day.

That holding-the-line work is what Pia, at the org level, is built for.

What "built for many shops from the start" actually looks like

A chain owner I spoke to last month described his current setup like this: "I run eight shops. I have eight Marg installations, eight backup PCs, eight worker WhatsApp groups, eight stockout panics, and one accountant who has been threatening to quit since 2022."

Compare that to what we're trying to make normal for the chain operator:

One identity that knows every shop. When you, the owner, open Pia, you don't pick a shop and then re-pick another. You see the network. Branch A's morning, branch B's morning, branch H's morning — together, in one paragraph, with the deltas highlighted. Branch A till is up 12% vs Tuesday. Branch C had two stockouts overnight. Branch F refills are running late by 4 hours.

Workers are workers; their shop is incidental. Ravi who covers branch B's evening shift sometimes also covers branch G's morning. He has one login, one identity, one history with Pia. He moves between branches; his surface moves with him. He never logs out, logs in, learns a new install.

Stock is yours, not the branch's. When branch B is running low on Dolo and branch A has too many, Pia doesn't wait for you to notice. The draft transfer appears in the owner's morning paragraph: "Branch A → Branch B: 8 strips of Dolo 650, draft ready, approve to dispatch." You approve from your phone in the auto-rickshaw. The branch managers see what the owner approved, in their language. Nobody types anything.

Pricing locked at the org, visible per shop. Whatever locked-price relationship you have with us as a chain stays consistent — you don't get re-priced when you open a new shop, and new shops fold into the chain's discount stack automatically. Branch managers see what their shop pays; the owner sees what the org pays.

Compliance rolls up; renewals don't surprise. Pia knows which drug license is up when. Pia knows when the Schedule H register at branch D was last reviewed. Pia tells the owner a week before any of these, not a week after.

Brand-keeping, automated. When the owner says "we don't sell expired stock at any branch, ever," every branch's expiry workflow is the same workflow. There isn't a branch-D-special exception. There isn't a different procedure at branch H because the manager there was trained earlier. The standard is the workflow.

Quiet visibility, loud anomalies. The owner doesn't get a notification every time a worker logs in. The owner gets a notification when branch F's till is short by more than its rolling-90-day median delta. The owner gets a notification when supplier pricing at branch C diverges from supplier pricing at the other branches. The owner gets the signal, never the noise.

A chain owner's actual day, redrawn

Six o'clock, you wake up. Before the chai is on the stove, your phone has a paragraph from Pia:

Network · 13 May. Yesterday's till across 8 branches: ₹4.71L. Top sellers: Dolo 650 (412 strips), Pan 40 (203 strips), Crocin 500 (188 strips). Two branch alerts: Branch C had a stockout on Telma 40 from 19:40 to close — covered by referrals. Branch F's evening till was ₹1,840 short of the rolling median; reconciliation flagged for manager. Three drafts await your approval: an inter-branch transfer (A → B, Dolo 650, 8 strips), a supplier reorder (Vinayak, ₹86,400, 6 SKUs), and a Schedule H register review for Branch D, due Friday.

You skim. You approve two and ask Pia to defer the third till you've called the manager at Branch D. You finish your chai. By the time you've reached your first branch by 9, three things have already moved without you having to say so.

That's eight shops, running on one Pia, before the day has properly started.

Why this is hard for incumbents to copy

It isn't impossible — anything is, given a decade. But the reason cloud-mobile incumbents struggle to land here, even with their better-than-Marg foundations, is that multi-shop is the assumption from the bottom of the stack, not a feature added on top. Adding it as a feature gives you "consolidated reporting." Building from it as an assumption gives you the morning paragraph above.

Pia was started by a team that watched chain owners try to bend single-shop software into shape. The bend never holds. The owner ends up running the chain in their head, and the software just records what already happened. We started from the other side — the chain is the unit; the single shop is the special case of N = 1.

For chain owners reading this

We're taking on a small number of chain customers in 2026. The conversation usually starts with us spending a day at one of your branches, watching the actual handoffs — supplier deliveries, shift changes, the moment something runs out. That day pays for itself; you find at least two operational gaps you didn't know you had, whether you end up working with us or not.

To start that conversation: write to [email protected] with how many shops you run, where they are, and what your CA has been threatening to quit about. The reply will be on WhatsApp, by the end of the next working day.

— Akshat, writing from Jabalpur