How to Read Your meed Pro Location Dashboard When You Run Three Shops, Not One

A multi-location dashboard only earns its keep if it tells you which shop needs attention today, not just how many stamps got collected company-wide. In meed Pro, that means reading three layers in order: the aggregate view for the trend, the per-location breakdown for the cause, and the campaign data for what to do next. Most owners read it backwards, start with a campaign number, panic, and miss that one location is dragging the average down while the other two are fine.

TL;DR

• Read location-level data before company-wide averages. One underperforming shop can hide two healthy ones.

• meed Pro's advanced analytics break down member, location, and campaign performance separately, each answering a different question.

• Many multi-location businesses still run no loyalty program at all, so having location-specific data already puts you ahead of a lot of competitors.

• Custom notifications let you message underperforming locations directly. This is a Pro-only feature, not available on the Free plan.

• Your first two locations are included in Pro; each additional shop is an incremental add-on, not a new subscription.

About the author: meed builds loyalty infrastructure for independent businesses running multiple locations, from cafe groups to salon franchises, and this guide draws on how the meed Business Portal structures location-level reporting for Pro accounts.

What does the meed Pro dashboard actually show for multi-location accounts?

The meed Pro dashboard organizes data into three tiers: account-wide totals, per-location breakdowns, and campaign-specific performance. Each tier answers a different question, and conflating them is the most common reading mistake owners make.

Account-wide totals tell you how the business is doing as a whole: total members, total redemptions, overall visit frequency. Useful for a board meeting, useless for deciding which shop needs a fix this week. Per-location breakdowns isolate each site's member count, redemption rate, and visit frequency, so you can see that Shop A has 400 active members redeeming weekly while Shop C has 150 members who haven't redeemed in a month. Campaign performance sits on top of both, showing how a specific promotion performed at each site.

The Free plan includes digital cards, QR enrollment, wallet integration, and nearby notifications. Advanced analytics, including the member, location, and campaign breakdowns described here, are a Pro-only capability.

Why does reading location data before aggregate data change your decisions?

Aggregate numbers average away the exact signal you need to act on. If you run three shops and look at a blended "total redemptions this month" figure, you can't tell whether that number reflects three shops performing evenly or one shop carrying the other two. A dashboard isn't useful until it can isolate the variable you need to change.

This is standard practice in multi-location loyalty management generally: centralized platforms with location-level drill-down let a corporate or owner view stay intact while still surfacing per-site detail. The mechanism is simple. Think of it like a restaurant group's P&L. Nobody manages three restaurants off a single combined revenue line, because that number can't tell you which kitchen has a cost problem. You need the line broken out by site before the combined number means anything. Loyalty analytics work the same way: the aggregate is a summary of a decision you've already made, not a tool for making the next one.

A related but distinct question is what to do once you've isolated the lagging location, which is where notifications and campaign targeting come in.

How do you compare performance across locations without misreading normal variation?

Comparing locations means measuring each site's performance against its own baseline first, then against the company average, not the other way around. A shop in a slower part of town will always show lower raw redemption numbers than a flagship location. That's not underperformance, that's footfall.

Best practice here, consistent with general multi-location analytics standards, is to track each location's trend over time and measure localized campaign results against that location's own history before comparing it to siblings. A few practical checks:

• Visit frequency trend, not visit frequency snapshot. Is this location's frequency rising or falling over the last three cycles, regardless of where it sits relative to the others.

• Redemption rate per enrolled member, not total redemptions. A smaller shop with fewer members but a high redemption rate is healthier than a larger shop with many inactive sign-ups.

• Campaign lift at that specific location compared to its own pre-campaign baseline, not compared to a different shop's baseline.

Building on the trend-versus-snapshot point above, the harder question is what you actually do once you've confirmed a location is genuinely lagging, not just quieter.

What should you do when one location is clearly underperforming?

Once location-level data confirms a genuine gap, the fix usually starts with a targeted message, not a blanket campaign across all three shops. This is where custom notifications matter, and it's a Pro-only feature.

When one location shows a pattern of inactive members while the others don't, sending a company-wide push wastes the message on locations that don't need it and risks notification fatigue for members who are already engaged. Custom notifications in meed Pro let you message a specific location's members directly, which is the mechanism this scenario calls for. If you're on the Free plan and considering this use case, that's the clearest sign it's time to move to Pro, since nearby notifications on Free are wallet-triggered by location proximity, not business-initiated custom messages.

The mechanical difference matters, because it explains what you can and can't control. Apple Wallet and Google Wallet both support multiple location triggers per pass, though each platform handles geofencing differently. That's why nearby notifications feel slightly different depending on the customer's phone, the wallet platform is doing some of that work automatically. Custom notifications in meed Pro sit above this layer entirely, they're business-initiated messages, not location-triggered ones, which is why they're the right tool for a targeted win-back push.

How does the dashboard structure change once you add a fourth or fifth location?

The reading method doesn't change as you scale past three shops, but the discipline required to use it well does. Pro includes your first two locations, with each additional site added for US$39/month. That pricing structure matters for how you think about the dashboard, because every new location is a new row in your per-location breakdown, not a new dashboard to learn.

At three locations, you can still eyeball the per-site breakdown and catch the outlier. At six or seven, you need a habit: check per-location redemption rate and visit frequency trend on a fixed schedule, weekly or biweekly, rather than only when something feels off. The dashboard scales fine. What doesn't scale automatically is your attention, so build the check into a routine rather than relying on noticing a drop.

One more thing if you're running stamp cards across locations: meed has a versioning feature for stamp cards, called Seasons. When it launches, it will be a Pro-plan feature that lets you update a stamp card's reward or stamp count without resetting customers who are already mid-cycle. Worth knowing it's coming, not yet something to plan a campaign around.

Frequently Asked Questions

Does the Free plan show per-location data for multiple shops? The Free plan includes digital cards and wallet integration, but advanced analytics with location-level breakdowns are a Pro-plan capability.

How many locations are included in the Pro plan? Pro includes your first two locations. Each additional location is US$39/month on top of the base Pro subscription.

What's the difference between nearby notifications and custom notifications? Nearby notifications are wallet-driven and triggered automatically by a customer's proximity to a location, available on both Free and Pro. Custom notifications are business-initiated push messages you write and send yourself, and they're Pro-only.

Can I compare two locations' campaign performance directly in the dashboard? Yes, campaign performance is broken out by location in meed Pro's advanced analytics, so you can see how the same promotion performed at each site.

Why do multi-location businesses need loyalty analytics at all? Many operate without location-level visibility into member behavior and redemption patterns, which means adding this data layer immediately surfaces decisions most competitors aren't even seeing.

Will Seasons let me update a stamp card without affecting current members? Seasons is designed so that members already collecting stamps stay on their original card version while new sign-ups move to the latest one. It will be a Pro-plan feature once launched.

Does the dashboard work the same on mobile as on desktop? The meed Business Portal is web-based, designed for managing programs and reviewing analytics from a browser on any device.

About meed

meed is a digital loyalty platform built for independent and multi-location businesses that don't want their customers downloading another app. Programs live directly in Apple Wallet and Google Wallet, with enrollment through QR codes, NFC taps, or AI-powered receipt scanning that works without any POS integration. For businesses running more than one site, meed Pro adds location-level analytics, custom notifications, and multi-location management built to scale without adding operational complexity. The platform serves independent businesses internationally, from single-site cafes to multi-location franchise groups.

If you're running more than one shop and still reading loyalty data as one blended number, you need the location breakdown. Visit meed to see how Pro's dashboard handles multi-location reporting.