When you run one store, you know how it's doing by feel. You're there every day. You see the traffic, you hear the register, you know when it's slow.
When you run two or more, that intuition breaks. You can't be everywhere, so you rely on data. And this is where things get complicated with Square — not because the data isn't there, but because it's structured in a way that makes meaningful comparison surprisingly difficult.
How Square organizes multi-location data
Square's data model is location-scoped. Every transaction, every inventory record, every employee, every customer interaction belongs to a specific location. This makes sense for operations — your staff at Location A shouldn't see Location B's time clock. But it creates a real problem for analytics.
When you open the Square Seller Dashboard, you can view reports for each location individually. You can see revenue for Store A and revenue for Store B. Square even offers a basic side-by-side comparison for some metrics. But that's where it stops.
What you can't easily do is normalize, contextualize, or cross-reference. You get columns of numbers without the framework to make those numbers meaningful.
The KPIs that matter for multi-location comparison
Before diving into tools and methods, you need to decide what you're comparing. These are the metrics that actually reveal performance differences between locations.
Revenue per location
The obvious starting point, and also the most misleading if used alone. A location that does $80,000 per month in a high-traffic mall is performing very differently from a location that does $80,000 in a suburban strip center with half the foot traffic and lower rent. Raw revenue tells you about volume. It tells you almost nothing about efficiency.
Transaction count and average order value
These two metrics together are far more useful than revenue alone. A location with high transaction count but low average order value (AOV) is processing lots of small purchases — possibly a convenience-driven customer base. A location with fewer transactions but higher AOV might be doing better at upselling or serving a different customer segment.
Square tracks both of these, but you need to pull them manually for each location and compare them yourself.
Item mix by location
Which products sell at Location A versus Location B? The differences are often surprising. A coffee shop might find that one location sells 3x more food items relative to drinks compared to another. That has implications for staffing, kitchen equipment, inventory allocation, and even store layout.
Square's item reports will show you top sellers per location, but it won't highlight the divergence between locations. You have to export and compare manually.
Revenue per labor hour
This is the metric most multi-location operators overlook, and it's arguably the most important. If Location A generates $500 per labor hour and Location B generates $320, that's a meaningful efficiency gap. It could indicate overstaffing, poor scheduling, lower traffic, or a less effective sales team.
Square Team Management tracks hours worked and can associate sales with employees, but the revenue-per-labor-hour calculation isn't surfaced in the dashboard.
Normalizing for differences between locations
Raw comparisons between locations are almost always misleading. A fair comparison requires normalizing for the factors each location can't control.
Operating hours. If Location A is open 12 hours a day and Location B is open 8, comparing daily revenue is pointless. Revenue per operating hour is the fair metric.
Foot traffic. A store in a busy downtown area will naturally see more transactions than one in a quieter neighborhood. If you have foot traffic data (from a counter or from your landlord's reports), revenue per visitor or conversion rate gives you a much better picture.
Store size and layout. Revenue per square foot is a standard retail metric for a reason. A 2,000 sqft store doing $100K per month is outperforming a 4,000 sqft store doing $150K, even though the raw number says otherwise.
Local competition. Harder to quantify, but important to acknowledge. A location that maintains steady revenue despite a new competitor opening nearby might be your strongest performer.
Square doesn't normalize for any of these factors. It gives you raw numbers by location and leaves the context to you.
Identifying best practices from top locations
The real value of multi-location analytics isn't just identifying which store is "winning." It's understanding why — and replicating what works.
When you find that one location consistently outperforms on AOV, dig into the details. Is it the product mix? The staff? The layout? The customer demographics? Often the answer is a combination, but there's usually a primary driver.
Staff practices. If one location's team consistently generates higher AOV, study what they're doing differently. Are they recommending add-ons? Mentioning promotions? Engaging differently during checkout? The data points you to the store; observation and conversation reveal the practice.
Product placement. Different locations sometimes organically develop better merchandising. A product that's buried in the back of Store A might be displayed prominently at Store B — and selling twice as much. Use the sales data to identify these discrepancies, then standardize what works.
Operational efficiency. Look at the location with the best revenue-per-labor-hour ratio. Map their shift schedule, their peak-hour staffing pattern, and their break rotation. Often the difference between your most and least efficient location comes down to scheduling, not skill.
Inventory allocation across locations
One of the biggest operational challenges for multi-location retail is deciding how to distribute inventory. Square Inventory tracks stock levels per location, and you can set up stock alerts. But the allocation decision requires more than current stock levels — it requires velocity data.
A product that sells 10 units per week at Location A and 3 units per week at Location B should have very different allocation ratios in your next purchase order. The problem is that Square doesn't surface sell-through velocity as a cross-location comparison. You see stock levels. You see sales. Connecting the two across locations is manual work.
Smart inventory allocation means sending more stock where it sells faster, not distributing evenly across locations. It also means identifying products that only perform at specific locations and not wasting shelf space elsewhere.
Where Square Dashboard falls short
Square's reporting is designed for single-location operational clarity. For multi-location analytics, you hit these walls:
- No normalized comparisons. Revenue side-by-side without accounting for hours, traffic, or size.
- No cross-location item performance. You can see top items per location, but not which items over-index or under-index relative to chain averages.
- No velocity-based inventory allocation. Stock levels per location without sell-through rate comparisons.
- No customer overlap analysis. If a customer shops at multiple locations, Square's Customer Directory doesn't consolidate that behavior into a unified profile.
- Limited export options. Getting data into a format suitable for cross-location analysis means multiple exports, multiple spreadsheets, and manual reconciliation.
These aren't failures — Square is a POS system, not a business intelligence platform. But they are real limitations for anyone running more than one or two locations.
Unified multi-location analytics with Spark
Spark by MishiPay connects to your Square account via OAuth and pulls transaction, catalog, inventory, and customer data across all your locations into a single analytical layer. No CSV exports, no manual merging.
Once connected, you can ask questions that span locations naturally:
"Which location has the highest AOV this month, and what's driving it?"
"Compare sell-through rates for my top 20 products across all stores."
"Which items sell well at my downtown location but underperform elsewhere?"
Spark normalizes the data so you're comparing like with like. The AI understands that raw revenue isn't the full picture and will factor in transaction counts, item mix, and time periods to give you actionable answers rather than raw numbers.
For merchants who also sell online through Shopify, WooCommerce, or another platform, Spark brings that data into the same view. You can compare how a product performs in-store across locations and online — all from one conversation.
A practical approach to multi-location analytics
If you're just getting started with multi-location comparisons, don't try to track everything at once. Focus on three metrics:
- AOV by location — Identifies upselling and product mix differences.
- Revenue per labor hour — Identifies staffing and efficiency gaps.
- Item velocity by location — Identifies where to allocate inventory.
Review these weekly. When you spot a significant divergence, investigate. Your best-performing location is a blueprint. Your underperforming location is an opportunity.
The merchants who scale successfully from two locations to ten all share one trait: they use data to replicate what works, rather than managing each location as a standalone experiment.
Compare your Square locations in one view
Spark connects to all your Square locations and gives you normalized, cross-location analytics — no spreadsheets required.