Multi-location: 3 branches, 3 spreadsheets, an owner who doesn't know which site sells. The group dashboard you're missing

Three branches, three truths, and nobody who knows which site actually sells

You opened the second location with pride. Then the third. From the outside you’re a small growing network; from the inside, you’re three companies that speak three different languages. Every branch has its spreadsheet, its way of counting receipts (scontrini), its manager who at month end sends “the numbers” — which arrive in three different formats, at three different times, with three different definitions of what went well. And you, owner or network director, find yourself doing the most absurd thing: adding three sheets by hand to understand how the group is doing, and still not being able to answer the simplest question — which site sells better, and why?

A multi-location dashboard is for exactly this: turning three (or five, or ten) separate truths into one, with unified branch data under a common definition, and the ability to compare stores honestly. It isn’t a whim of a big chain: it’s the tool that gives you control back at the exact moment the company has become too big to live in your head and too small to have a data office.

This article is for anyone who runs a network of locations — shops, branches, practices, stores, warehouses — and lives on manual consolidations that arrive late and never add up. Let’s see why consolidating isn’t adding up Excel, why the real value is the comparison between locations (and why it scares people), how you manage permissions so transparency doesn’t become a war, what the two different screens you need look like (leadership’s and the store manager’s), and how you do a rollout location by location without triggering a revolt.

Every location has its truth (and it’s a power problem, not an Excel problem)

The first thing to understand is that multi-location chaos isn’t a technical problem, it’s an autonomy problem. Every branch manager, over the years, has built their way of measuring: what counts as a sale, when they record a return, how they treat gifts and staff discounts, whether they include VAT (IVA) or not, how they count staff hours. They didn’t do it out of spite: they did it because nobody had given them a common way, and any way was better than none.

The result is that when you ask “how much did the Bologna branch sell in November?”, the answer depends on who calculates it. The Bologna manager gives you a number, central accounts derives another from the gestionale/ERP, and the two never match — not because anyone is cheating, but because they’re measuring different things with the same word. Multiply this by three locations and you have six numbers for one question. Every network meeting starts with ten minutes of “no, wait, my data says something else”, and ends without anyone having decided anything.

It’s the exact same mechanism as the KPI fight inside a single company, but amplified: here it isn’t two departments fighting, it’s three companies-within-the-company, each jealous of their own numbers. And there’s an extra, delicate ingredient: comparing locations touches the pride and sometimes the wallet of the managers. Whoever is first claims it; whoever is last finds a thousand reasons why “my numbers are different”. Building a multi-location dashboard means, before you even connect data, defusing this politics. Anyone who treats it as a purely technical problem fails.

Consolidating isn’t adding up Excel

The instinct, faced with three sheets, is: “we add them up”. Someone in accounts, every month, takes the three Excel files and pastes them into a fourth sheet, “the group one”. It looks like the solution, it’s the trap. Because adding three sheets that measure different things doesn’t produce a group number: it produces a fake number, the sum of three incompatible definitions. It’s like adding metres, feet and cubits and calling the result “total length”.

Consolidating for real means something else. It means, first, agreeing the definitions — one single definition of sale, of return, of average ticket, of hours worked, valid for all locations. Then it means taking the data at the source, not from the summary sheets each manager has already “worked” their own way, but from the gestionale/ERP or the tills, where the data is raw and the same for everyone. And then it means applying the same cleaning rules to all locations, every night, automatically. Only at that point is the group number true, because it’s the sum of three numbers built the same way.

The practical difference is huge. Manual consolidation is slow (it arrives mid-month), fragile (it depends on who does it and the sheets they receive), and false (it adds different definitions). A real consolidation is automatic (every night), robust (it takes data at the source), and reliable (same rules for everyone). And above all it lets you do the thing the summed sheets don’t allow: compare locations with each other, knowing you’re comparing apples with apples.

This is also why a multi-location dashboard isn’t “downloaded from a template”: the template doesn’t know your three diverging definitions, and it doesn’t do the political work of reducing them to one. It’s the same principle as the dashboard the owner actually opens: under the screen there’s a job of definitions and sources that no tool does for you. Multi-location is a chapter of the broader guide to dashboards and data products, to which the same rules apply.

The real power is comparison (and that’s why it scares people)

Here’s the part that’s actually worth the money, and that almost nobody sells you as they should: the value of a multi-location dashboard isn’t the sum, it’s the comparison. Adding the locations tells you how the group is doing; comparing them tells you where to intervene, and that’s pure management power.

When you can put your branches on the same row, with the same numbers, you start to see things that were invisible before. Why does the Bologna branch have an average ticket 20% higher with the same assortment? What does the Verona manager do to have half the returns of the others? Why does Turin have twice the staff cost on sales? Every difference between “equal” locations is a question, and every question is an opportunity: one location’s best practice becomes the recipe for the others, and one location’s problem is seen before it becomes the group norm.

Comparison turns network leadership from “feelings and phone calls” into “numbers and decisions”. Instead of running three companies by gut, you run a group with a common metre, and you can reward who deserves it, help who is struggling, and replicate what works.

And that’s exactly why comparison scares whoever is underneath. The moment locations are comparable, the manager who until now hid behind “my numbers are different” is exposed. It’s human that they resist. But it’s also the sign that the dashboard is working: a multi-location dashboard that doesn’t line the branches up is useless, it’s just three Excel files with a prettier cover. Transparency is the product, not a side effect — and it has to be managed with intelligence, as we’ll see with permissions.

To give you an idea of how concrete this is, here are the kind of questions an honest comparison puts in your hands every morning: which location has the best margin percentage, not only the highest revenue? Where are returns out of line, a signal of a sales or quality problem? Which manager manages to keep staff cost on sales low, and what do they do differently? Which location converts incoming customers better? Each of these questions, before, simply couldn’t be asked, because there was no common metre. With comparison they become your weekly agenda — and every answer is a concrete move on a precise location.

Permissions: everyone sees their location, leadership sees everything

If transparency between locations is powerful, it also has to be dosed, because total and brutal transparency creates more wars than value. The golden rule of a multi-location dashboard is permissions by role and by location, and it’s one of the parts a serious product handles and an Excel sheet doesn’t.

How it works, in practice:

• The branch manager sees their location in detail: their numbers, their products, their staff, their history. It’s their daily working tool.
• The manager also sees how they sit against the network average — not necessarily the naked numbers of the other locations with name and surname, but their gap from the average or the benchmark. It exists to make them improve, not to humiliate them in public.
• Network leadership sees everything: all locations, in a row, comparable, with names and numbers. They’re the ones who decide who to reward and who to help, and they need the full picture.
• Central accounts sees the cash and administrative numbers of all locations, but maybe not the operational details that aren’t their business.

Why is it important to dose it this way? Because putting the naked numbers of all locations in front of all managers, every day, with name and surname, turns the network into an arena. A bit of healthy competition helps; daily public humiliation generates defence, sabotage and data manipulation. Well-made permissions give everyone what they need to do their job better, and leadership what it needs to govern — without turning every number into a pillory. This dosing isn’t done by a shared Excel: it’s done by a product designed with roles in mind.

The two screens: leadership and the store manager

A classic mistake is to build one dashboard and give it to everyone. It doesn’t work, because the network owner and the manager of a single location need to look at different things. You need, at minimum, two screens.

The network leadership screen answers the question “how is the group and where do I intervene?”. At the top, the group numbers (sales, margin, cash) with the comparison against the same period. Straight underneath, the piece that counts: the ranking of locations, all in a row on the same metre, with the differences highlighted — who is growing, who is dropping, who is out of line on an indicator. And the alerts: “location X is 25% down for two weeks”, “Y’s staff cost is off the scale”, “Z’s returns have doubled”. Leadership, in twenty seconds, knows which location to pick up the phone about.

The store manager screen answers another question: “how is my location and what do I do today?”. Here you don’t need the brutal comparison with the others, you need operational detail: yesterday’s sales, the products that move and those that sit, staff, the month’s targets, and their own position against the network average as a stimulus. It’s a working tool, not a verdict.

Same source of truth, same definitions, two views. It’s the same principle as KPIs by department, applied to locations: common definitions underneath, specific views on top. If every location also has different definitions, the two screens will never reconcile, and you’re back to three Excel files with better graphics.

The alerts that count in a network

In a single company alerts warn you of drops; in a network they also serve another precious thing: telling you which location needs you today, without you having to look at five screens. The value of a multi-location alert is that it filters the noise and points you at the right branch.

A few examples of useful alerts for whoever runs a network:

• “Location X is 25% below its average of the last four weeks”: not a group drop, a localised problem to understand.
• “Location Y’s staff cost has risen 5 points on sales”: maybe too many hours, maybe a sales drop with the same shifts.
• “Location Z’s returns have doubled”: a problem of aggressive selling, of quality, or of a single member of staff.
• “A location hasn’t transmitted yesterday’s data”: often it isn’t a sales collapse, it’s a technical problem at the till — and you want to know immediately, not at month end when the consolidation doesn’t add up.

Without alerts, network leadership either looks at everything (and therefore looks at nothing) or relies on the managers’ phone calls, who call when things are going well and stay quiet when they’re going badly. With alerts, the system calls you when it’s needed, and you spend your attention where it actually counts.

Common definitions: the boring part that makes everything true

I come back to this point because in multi-location it’s even more decisive than in a single company: without common definitions, there is no consolidation and there is no comparison. And definitions, in a network, are more treacherous, because every location has invented its own.

A few examples of words that have to be decided once and for all, valid for all locations:

• Receipt / sale. With or without VAT (IVA), returns deducted when, gifts and staff discounts included or not. One location counts them, another doesn’t: the comparison breaks.
• Return. Deducted from the location that sold or from the one that receives the return? In a network a customer buys in Milan and returns in Rome: without a rule, that return “disappears” or is counted twice.
• Hours worked / staff cost. Do you include overtime, part-timers, seasonal staff the same way for all locations? “Staff cost on sales” is comparable only if you calculate it the same everywhere.
• Transfers between locations. Goods that pass from one site to another are neither a sale nor a purchase: if you don’t treat them well, they inflate or deflate the numbers of the locations involved.

The rule is the same as always: the definition is decided at the table and signed, and from that moment it holds for everyone. In a network, this table has to include the location managers (who know the real exceptions) but be closed by leadership (who has the authority). It’s boring work, and sometimes uncomfortable, because some manager will discover that their “good” numbers were good only because they counted generously. But it’s exactly this work that makes the group governable.

The rollout: location by location, not everything in one night

The way you introduce the dashboard also counts, and in multi-location the fatal error is the “big bang”: switching everything on for all locations the same day. Too much resistance, too many fronts open, too many things that break together. The way that works is a layered rollout.

You start from one pilot location — better if the one with the most collaborative manager, not the most problematic. On that one you connect the sources, you put the agreed definitions to the test, you adjust the screen to what is actually needed. When the pilot location works and its manager speaks well of it, you move to the second, then the third, taking the lessons learned with you. Every location added is easier than the previous one, because the system is more mature and — don’t underestimate this — because the managers of the other locations have seen that for whoever is already in, the dashboard is useful, instead of being only leadership’s Big Brother.

This approach also has a political advantage: it turns the first managers into allies instead of victims. The pilot location manager, involved in the build, becomes the internal testimonial. And they’re much more effective than any imposition from above.

“Our numbers are different”: handling the resistance

Get ready to hear it, because you’ll hear it from every location: “but here it’s different”. Sometimes it’s an excuse not to be compared; sometimes, though, it’s true — and distinguishing the two is half the work.

There are legitimate differences between locations that have to be respected: a branch in the city centre has different rent costs and customer mix from one in the outskirts; a younger location can’t be compared with a historic one on absolute volumes. The right dashboard takes these differences into account — comparing locations also on relative indicators (average ticket, margin percentage, returns as a percentage, revenue per square metre) and not only on absolute numbers, which would always favour the bigger locations.

But there are also invented differences, the ones that are born only from the fact that every location counted its own way. Those disappear the moment definitions become common: if everyone measures the sale the same way, the excuse “we count differently” no longer exists. The way to defuse resistance is exactly this: make the definitions so explicit and shared that “my numbers are different” becomes “my results are different” — and at that point you can finally talk about the why, which is the useful conversation.

A practical piece of advice: in the first weeks, use comparison to understand, not to punish. If the first use of the dashboard is a public dressing-down of the last location in the ranking, you’ve taught everyone that data is a weapon, and from then on everyone will manipulate it to defend themselves. If the first use is “let’s look at what the first one does well and try to copy it”, you’ve taught that data is there to improve. The same transparency, two opposite cultures.

A typical case: from five notebooks to a ranking

A typical profile, architectural, no names. Small chain, five stores, each with its own way of keeping the numbers: two on the gestionale/ERP, two on Excel, one practically from the branch manager’s memory. Every month central accounts spent two days collecting, chasing, pasting and “making five sheets add up”, and the consolidation arrived around the 15th. Comparison between locations didn’t exist: nobody could say which site actually yielded more, because the numbers weren’t comparable.

What was done, in phases. First the definitions table, with the five managers and leadership: one single definition of receipt, return, staff cost. Then the common catalogue, same product codes and categories for everyone (the most boring piece and the most important). Then the pilot location, the one of the most open manager, connected to the source; in a few weeks it worked, and the others were added one at a time.

After: consolidation every night instead of the 15th of the month; accounts no longer spends two days pasting; and for the first time an honest ranking of the five locations on the same metre. The uncomfortable discovery: the store the owner considered “the best” was only the biggest; at equal floor space it yielded less than two smaller locations. From there the right conversation started — what do the small ones do well? — which before was impossible because there was no common metre.

What adding Excel by hand costs (and what comparison is worth)

Let’s put some numbers, because manual consolidation looks like “only” two days of work and actually costs on three fronts. First, the hours: two person-days a month of qualified accounts collecting and pasting, plus the time of the managers who prepare their sheets, easily makes 4–5 person-days a month thrown into a job a system does on its own. Second, the delay: the consolidation that arrives mid-month is a month of decisions taken in the dark on the group. Third, and the most expensive, the missed decisions for lack of comparison: without knowing which location yields less and why, you don’t intervene, and a struggling branch can burn margin for months before you notice.

On the other side of the scale, the value of comparison is the hardest item to quantify and the biggest: replicating across five locations the best practice of the best one, or recovering the margin of the worst, is almost always worth far more than the cost of the project. A single point of margin recovered on a network that turns over a few million pays for the dashboard and leaves change. It isn’t an IT spend: it’s a profitability tool.

Three classic mistakes in multi-location networks

Three (actually four) mistakes I see repeating in networks that try to get themselves in order on their own.

• Adding the sheets instead of consolidating at the source. Produces a fake group number and no possible comparison. It’s the most common, because it looks the simplest.
• Giving everyone the same dashboard. The network owner and the store manager look at different things; one single screen disappoints both and makes nobody decide. You need at least two views, with different permissions.
• Using the data as a whip from day one. If the dashboard’s debut is a public dressing-down of the last location, you teach everyone that numbers are a weapon, and from then on everyone will cook them to defend themselves. Transparency has to be introduced as an improvement tool.
• Comparing only absolute numbers. That way the biggest location always wins, and the small ones feel treated unfairly — and they’re right. The useful comparison is on relative numbers (margin percentage, average ticket, revenue per square metre), where a small efficient location beats a big wasteful one: and that’s exactly the information you need.

What to do with the data before the software

One last thing, important so you don’t throw money away: often, before you buy anything, there’s preparatory work you can do yourself, and that makes the project much easier (and cheaper).

Before connecting sources and building screens, put three things in order. The definitions: call the table and decide the five or six key words, valid for all locations. It’s free and it’s worth half the project. The sources at the location: check that every branch actually records data at the source (till, gestionale/ERP) and not only on summary sheets — if a location keeps everything by hand in a notebook, that has to be fixed first. The common catalogue: products, categories, customers have to be coded the same way across locations, otherwise comparison is impossible (if “red t-shirt” in Milan is one code and in Rome another, you’ll never be able to add them). This hygiene work, done first, stops the dashboard being born already crooked.

If these three pieces are in place, building the multi-location dashboard is almost mechanical. If they aren’t, no software fixes them for you: it would fix them by hand every month, that is it would recreate the three-Excel problem inside a prettier interface.

One last note on this preparatory work: it doesn’t need to be perfect to start, it needs to be decided. You can start from the more ordered locations while you fix the others, and refine the catalogue along the way. The important thing is to have taken the underlying decisions — what counts as a sale, which codes we use — because those, once taken, hold for all present and future locations and aren’t put back in discussion every month.

From managing by phone calls to governing with numbers

There’s a cultural leap, not only a technical one, in all this. Many small and medium networks are still governed “by phone calls”: the owner calls the managers, has them tell how it’s going, and builds an idea of the group by putting impressions together. It works as long as the locations are two and you know them by heart. At the third, the fourth, the method breaks: impressions don’t add up, and the managers — by nature — tell you their point of view, not a neutral datum. Whoever is doing well emphasises, whoever is doing badly minimises, and you decide on an average of stories.

A multi-location dashboard changes the base of the conversation. It doesn’t eliminate the human relationship with the managers — that stays fundamental — but it puts a floor of shared facts underneath it. The phone call is no longer “how’s it going at yours?” with a vague answer, but “I’ve seen that returns have doubled, what happened?” with a concrete answer. You move from managing by anecdotes to governing by numbers, without losing contact with people: in fact, with more honest conversations, because they start from a reality you both see.

It’s the same leap a single company makes when it stops deciding by gut and starts looking at a few true numbers — only that in a network the gain is multiplied by the number of locations, and the stakes are the very ability to grow without losing control. A network you can’t see you can’t steer; a network measured with a single metre, yes.

It’s for you if / it isn’t for you if

It’s for you if: you have two or more locations and every month end you add Excel by hand to understand how the group is doing; you can’t answer with certainty “which site sells better, and why?”; you suspect some locations “tweak” the numbers and you have no way to check; you want to replicate what works in one location across all the others.

It isn’t for you if: you have a single location (then your topic is the single dashboard, not multi-location); the locations are so different from each other that they aren’t really comparable or consolidable (rare true cases, often it’s an excuse); source data doesn’t yet exist in some location — there you fix collection first, then you consolidate.

Frequently asked questions

Do I have to force all locations to use the same gestionale/ERP? It helps a lot, but it isn’t always indispensable. A good multi-location dashboard can read from different sources and reconcile them, as long as the definitions are common. If however the locations use systems that are too heterogeneous, unifying them upstream simplifies everything and reduces maintenance costs.

Will location managers see the others’ numbers? You decide with the permissions. The healthiest configuration: everyone sees their own location in detail and their own gap from the network average; leadership sees all locations with names and numbers. You can make it more or less transparent, but avoid the daily public pillory.

How long does it take for a network of 3–5 locations? The definitions phase and the pilot location take a few weeks; then each additional location is faster. A useful consolidation in a couple of months is realistic, if the source data exists and the catalogue is common.

And if every location sells different things? That’s fine for comparison on relative indicators (margin %, average ticket, returns %, revenue per sqm) and for group consolidation. Comparison on specific products will only make sense where there’s overlap. The dashboard adapts to the level of comparison that makes sense for your network.

Can I start from a comparison between only two locations? Yes, and it’s an excellent way to season the definitions and the mechanics before widening. Two well-compared locations are worth more than five badly added.

Do the data and the system stay mine? Yes. Code, definitions and data stay your property, no lock-in. In a growing network it’s even more important: adding a location tomorrow has to be your decision, not a negotiation with a supplier.

Does the multi-location dashboard replace network meetings? No, it makes them useful. Today meetings start with ten minutes of “my data says something else”. With common numbers, you dedicate that time to deciding: why this location is dropping, what to copy from the one that’s growing. The dashboard doesn’t take away the meeting, it takes away the opening fight.

How do I stop managers cooking the numbers? By taking data at the source (till, gestionale/ERP) and not from the sheets the managers prepare. If the number is born at the till and the calculation rules are written in the system, there’s no room to “tweak”. It’s another reason consolidating at the source beats adding Excel: it removes the temptation, as well as the error.

And if I open a new location in six months? With a well-made system, adding it is connecting one more source and applying the definitions already decided: days, not a new project. The network’s growth shouldn’t depend on a supplier’s availability, and that’s another reason the system has to stay yours.

Do I need a dedicated data person to run it? No. Once built, consolidation is automatic and the alerts arrive on their own. You need, if anything, someone who watches even part-time and a maintenance agreement for when sources change or locations are added. It’s much less than a data office: it’s the point of building a system instead of hiring someone to compile by hand every month.

In one line

If you have several locations and every month end you add Excel to understand how the group is doing, you aren’t missing a faster report: you’re missing a multi-location dashboard with common definitions, automatic consolidation from the source and permissions by role — where the real value isn’t the sum of the branches, but their honest comparison. It’s the tool that takes you from running three companies by gut to governing a network with a single metre: reward who deserves it, help who is struggling, replicate what works.

If you want to understand how to build it on your network — from the definitions to the permissions to the two screens — look at the projects I’ve delivered or drop me a line: you start from your locations and your data, not from a chain template.