· Orqestra Team · 7 min read

Clover Reports for Multiple Locations: Setup and Compare

How Clover reports for multiple locations work: the multi-location dashboard, switching stores, consolidated Sales report, permissions and a weekly template.

Clover reports for multiple locations run from a separate Multi-location dashboard that Clover sets up when your stores are chained together as an enterprise or group. From that dashboard, Reports, then Sales Reports, gives you net sales, gross sales, refunds, tips and tender mix for a group, one location, or any set of locations, viewable by hour, day, week or month. Each store still has its own dashboard for everything else. This guide covers how to get there, how to compare stores, what Clover's roll-up leaves out, and a weekly template you can fill from the exports.

Every product claim below comes from Clover's help center as of 2026-10-27.

How Clover structures multiple locations

Clover's multi-location hierarchy overview describes up to four levels:

  • Enterprise: all groups and locations in the business. Non-processing, so no payments are taken here. Not every business has this level.
  • Groups: a set of locations. Also non-processing.
  • Individual processing locations: each store, with its own devices and payments.
  • Custom groups: any set of locations you want to report on together, for example "downtown stores" or "stores with the new menu."

The email address attached to the enterprise or group can see every location under it. Clover's multi-location FAQ adds three facts that matter before you expect a roll-up. The structure "is based on the structure set up in Fiserv," and changes go through your account manager or Clover support. A new location should appear under its group automatically; if it does not within 48 hours, call support. And locations on the Starter plan "will not have multi-location capabilities or be part of multi-location groups." If your second store was opened under an unrelated merchant account, there is no consolidated view until Clover chains it.

Switching between locations

  1. Log in to the Clover Web Dashboard.
  2. In the top left, next to the business name, select Switch your business.
  3. If you see Multi-location groups, pick a group name and select Apply to open that group's Multi-location dashboard. If you see Locations, you are already inside a group; use the Back arrow to go up a level.
  4. To open one store, expand the group with the arrow or type the store name in the search field, select it, and select Apply.

The group dashboard shows net sales and average amount for the group, the locations with the highest and lowest net sales, a tender breakdown, and an activity log. Clover's FAQ notes that Sales Activity, Finances and some other features are not available at the multi-location level; for those you switch to the individual store.

Running the consolidated Sales report

These steps follow Clover's Run the Sales Report for multiple locations page.

  1. From the Multi-location dashboard, select Reports, then Sales Reports.
  2. Pick a preset range (Today, Yesterday, This week, Last week, Last 7 days, Last 30 days) or Custom date range with a start and end date.
  3. Use the location filter to choose the group, one location, or several locations. The default is the current dashboard's location.
  4. Use Filters to narrow by location status (Open or Closed), city, state or ZIP.
  5. Next to the Sales table, set View by to hourly, daily, weekly or monthly (the options depend on the range you chose), Summary, or Locations.
  6. With Locations selected, use Columns to show or hide gross sales, refunds, tips, city, state and so on, and Advanced filters to save a custom filter.
  7. Set the Tender Types table to Summary or Locations the same way.
  8. Select Print, or Options then Export, to get the report out.

The summary section defines net sales as sales after discounts and refunds, gross sales as sales before them, amount collected as the final amount collected, and unpaid balance as pending payments on partially paid orders. These match the single-store definitions covered in how to read a Clover sales report.

The FAQ also lists a multi-location Employee Sales report and a multi-location Item Sales report under the same Reports menu, and Items and Employees screens for managing both across the enterprise.

Employee access across locations

By default, an employee you create at one store exists only on that store's dashboard. Clover's consolidate employees page describes an Owner-only setting, under Employees, Employees list, Options, Employee settings, with two choices: roll up all employees from individual locations to the corporate dashboard, or keep them separate (the default). Rolling up may force passcode changes and notifies affected employees by email. Clover warns that once saved, reversing the choice requires contacting support, so decide before you click. For reporting, the practical effect is that a district manager who needs the Employee Sales report across stores needs either the roll-up or an account created at the group level.

A weekly cross-location comparison template

Clover's roll-up gives you sales, orders, tips and tender mix per location. It does not give you labor or food cost, because Clover has no payroll or invoice data; that gap is covered in Clover reporting limitations. The template below combines the Clover export with two numbers from outside it. A fuller version with targets lives in the restaurant KPI dashboard template.

MetricSourceLocation ALocation BLocation C
Net salesClover multi-location Sales report, Locations view
Orders (paid)Same report
Average ticketNet sales divided by orders
Net sales vs same week last yearTwo exports, compared in a spreadsheet
Tips as % of net salesTips column divided by net sales
Card share of tendersTender Types table, Locations view
Labor costPayroll or scheduling tool
Labor %Labor cost divided by net sales
Food costInvoices plus inventory counts
Food cost %Food cost divided by net sales
Prime cost %Labor % plus food cost %

Fill the Clover rows from one export with View by set to Locations. Fill labor from your scheduling or payroll system and food cost from invoices and counts. Average ticket, the percentages and prime cost are formulas.

Worked example: three stores, one week

A three-unit fast-casual group, week of October 20 to 26, 2026. The numbers are made up but sized like a real operator.

MetricDowntownWestsideAirport Rd
Net sales$31,200$24,600$18,900
Orders2,0801,8451,260
Average ticket$15.00$13.33$15.00
Labor cost$9,050$7,870$6,240
Labor %29.0%32.0%33.0%
Food cost$9,360$7,750$6,430
Food cost %30.0%31.5%34.0%
Prime cost %59.0%63.5%67.0%

Reading it:

  1. Downtown has the most sales and the lowest prime cost. It is the benchmark, not necessarily the best-run store, because volume hides inefficiency.
  2. Westside's average ticket is $1.67 below the other two. Open the multi-location Item Sales report filtered to Westside and compare attachment of drinks and sides. A $1.00 lift on 1,845 orders is $1,845 a week.
  3. Airport Rd has the highest food cost. That can be waste, portioning, or a different menu mix. Run the Item Sales report by location and compare the top ten items' share of net sales; if the mix matches Downtown, the problem is in the kitchen, not the menu.
  4. Airport Rd labor at 33% on $18,900 of sales suggests the schedule was built for more volume. Pull the hourly View by for that store and find the hours where sales per labor hour collapse.

Taken together, the group runs at 62.5% prime cost (total prime cost $46,700 on $74,700 net sales). Getting Westside and Airport Rd to Downtown's 59% is worth about $1,100 and $1,500 a week respectively.

Handling locations that are not chained

If Clover support cannot chain a store, or one store is on the Starter plan, you can still compare. Run the single-store Sales report on each dashboard for the same range, export each to CSV, and paste them into the template. The definitions are the same, so the numbers line up. The cost is time: three logins, three exports, every week. Tools that connect to each Clover merchant account separately, such as the multi-location reporting apps on the App Market or Orqestra's sales analytics for Clover, remove the manual step by reading every store into one view regardless of how Clover has them chained.

Common mistakes

  1. Expecting a roll-up before the stores are chained. Check Switch your business first; if you only see one location, call your account manager.
  2. Comparing stores on amount collected. Use net sales. Tax rates and tip behavior differ by location and distort amount collected.
  3. Ranking stores on sales alone. The highest-volume store can carry the worst prime cost in dollars.
  4. Mixing date ranges. Set the range once on the multi-location report; do not pull one store from Today and another from Yesterday.
  5. Ignoring the daypart gap. Multi-location hourly views exist, but the employee attribution rule still applies: the order taker gets net sales, the payment taker gets amount collected.
  6. Rolling up employees without reading the warning. It cannot be undone without support.
  7. Leaving labor and food cost blank. A comparison with only sales columns tells you which store is busiest, not which one makes money.