· Orqestra Team · 8 min read
Clover Reporting Limitations: What the Reports Miss
Clover reporting limitations explained: no food cost or prime cost, limited date comparisons, multi-location setup, export and API limits, plus workarounds.
Clover's built-in reports tell you what you sold, who sold it, when, and how customers paid, and they do that well. The main Clover reporting limitations are that they do not know your purchases or your payroll, so there is no food cost, labor cost or prime cost; that date comparisons are limited to stepping backward one equal period at a time; and that multi-location roll-ups, long date ranges and bulk exports each come with conditions. This article lists each limit, cites where Clover documents the behavior, and gives a workaround.
Everything below is checked against Clover's help center and developer docs as of 2026-10-27. Where Clover's documentation is silent rather than explicit, the text says so.
What Clover reports do well
Clover's reports overview lists a solid set: Sales, Item sales, Employee sales, Tender and card types, Order types, Discounts, Removed items, Gift cards, Kitchen operations, Guest count and Requested reports. The Sales report breaks gross sales down to net sales and amount collected, filters by employee, device, order type and daypart, and reaches back five years. The Item sales report shows quantity sold, net sales per item, and, if you enter a cost on each item, cost of goods sold and gross profit. For a single location that wants to reconcile the day and spot its top sellers, that is enough. If you have not worked through what each line means, start with how to read a Clover sales report.
Where owners hit walls
| Question you want answered | Where Clover shows it | What is missing |
|---|---|---|
| What was my food cost % last week? | Item sales report shows COGS only as quantity sold times the per-item cost you typed into Inventory | No purchases, invoices or inventory counts, so no actual food cost |
| What is my labor cost %? | Employee sales report shows sales, refunds, charges and tips per employee | No wages, hours or labor cost; the report has no payroll data |
| What is my prime cost? | Nowhere | Needs food cost plus labor cost, neither of which Clover computes |
| How did this Tuesday compare with the same Tuesday last year? | Left and right arrows step to the previous or next period of the same length | No side-by-side view of two custom ranges |
| Sales by hour for one location | Sales report View by offers Monthly, Daily and Summary, plus a daypart or custom time window | Hourly appears in the multi-location report's View by list, not on the single-location Sales report page |
| Item sales by day | Item sales report for a range | Clover's own FAQ says default reports may not show daily breakdowns by item |
| Margin per item | Gross profit and gross profit margin columns | Only for items with a cost entered; Clover warns the number is too high if any item lacks a cost |
| All locations in one report | Multi-location dashboard Sales report | Only if your accounts were chained as an enterprise or group; Starter plan locations are excluded |
| 14 months of history in one pull | Sales report, custom range | One year at a time; over three months becomes a requested report |
| Every line item for a year in a spreadsheet | Report Export (CSV) or the REST API | API filters cap at 90 days per call and 1,000 records per page; the Export API covers 30 days per request |
No food cost, labor cost or prime cost
Clover's Item sales report definitions state that COGS equals net sold quantity multiplied by the individual cost for each item, with the cost coming from the Inventory app. That is a theoretical cost based on a number you typed, not what you actually paid your suppliers or what you actually used. The same page warns that gross profit "is higher than it should be if you have items without a defined cost." Clover does not have an invoices module, a purchase log or an inventory count, so actual food cost cannot be computed inside it. Labor is the same story: the Employee sales report covers sales, refunds, charges and tips, not hours or wages. Prime cost, the sum of food and labor, is therefore outside Clover's reporting entirely.
Limited custom date comparisons
Clover's Sales report page documents preset ranges, a custom range, and arrows that "cycle through previous and next time frames of the same duration to compare results." That handles this week against last week. It does not document comparing two ranges you choose, such as Super Bowl week this year against last year, in one view. You can run two reports and compare by hand, or export both.
Hourly and daypart views
The single-location Sales report lets you filter by business hours, a named daypart, or a custom daypart such as 7:00 PM to 11:00 PM repeated across each day. That shows one window at a time. The multi-location Sales report lists "hourly, daily, weekly, or monthly" in its View by menu, but the single-location page lists only Monthly, Daily and Summary. For a true hour-by-hour curve on one store, run a custom daypart per hour or export and bucket in a spreadsheet.
Multi-location roll-up depends on setup
Clover's multi-location FAQ explains that the enterprise and group structure "is based on the structure set up in Fiserv," that changes to the hierarchy go through your account manager or Clover support, that locations on the Starter plan "will not have multi-location capabilities," and that Sales Activity and Finances are not available at the multi-location level. If your second store was opened as an unrelated merchant account, there is no consolidated report until it is chained. See the companion guide to Clover multi-location reporting for the steps that do work.
Export granularity and the API
Dashboard reports export what the report shows. The Order types report states Export downloads CSV and Print saves PDF. Clover's dashboard and reports FAQ says that "while the default reports may not show daily breakdowns by item," you can export sales data and analyze it in a spreadsheet. For raw data, the REST API lists orders and payments, but Clover's filter documentation restricts time-based filters to a 90-day range per request, the pagination page caps a page at 1,000 records, and the Export API is limited to 30 days per request, is not real-time, and deletes files after 24 hours. None of this is a wall for a developer, but it is work.
Retention and requested reports
History is generous: five years. The catch is in how you reach it. Clover's Item sales report page says any range over three months becomes a report request delivered by email, viewable for 7 days, then listed in history until day 14, after which "you'll need to submit a new request." Save the export when it arrives.
Employee and device attribution
Clover notes that the employee who takes the order is credited with net sales while the employee who processes the payment is credited with amount collected, and the same applies to devices. If your servers ring and a cashier settles, per-employee totals will never tie to each other. That is by design, not a bug, but it limits how far you can trust per-person comparisons.
Workarounds, in order of effort
- Enter a cost on every item in the Inventory app so the Item sales COGS and gross profit columns stop lying. This gives you theoretical food cost per item.
- Use the arrows for like-for-like period comparison, and screenshot or export both periods when you need two custom ranges.
- Run custom dayparts for the windows you care about (pre-rush, rush, late night) instead of hunting for an hourly chart.
- Export the Sales and Item sales reports weekly to CSV and keep a folder. Requested reports expire; your files do not.
- Compute actual food cost outside Clover from net sales, invoices and counts (worked example below). The food cost calculator does the arithmetic.
- Get labor from your scheduling or payroll tool and divide by Clover net sales for labor %. Several scheduling apps already pull Clover net sales for this.
- Chain your locations through your Clover account manager if you need the multi-location dashboard, and move any Starter plan store up a plan.
- Use an integrated reporting tool when the spreadsheet starts eating your Monday. Orqestra's sales analytics reads your Clover sales and adds purchases, expenses and payroll so food cost and prime cost are computed, not estimated.
Worked example: actual food cost % from a Clover export plus invoices
Take a 55-seat neighborhood restaurant doing about $85,000 a month. For the week of October 13 to 19, 2026:
- Run the Sales report for the week and export it. Net sales (not amount collected, which includes tax and tips) is $21,400.
- Add up the supplier invoices dated that week: produce $1,420, protein $3,310, dairy $640, dry goods $980, beverage $800. Purchases = $7,150.
- Count inventory Sunday night before the week ($4,800) and the following Sunday ($4,950).
- Apply the formula:
Food cost = Beginning inventory + Purchases minus Ending inventory = $4,800 + $7,150 minus $4,950 = $7,000
Food cost % = Food cost divided by Net sales = $7,000 / $21,400 = 32.7%
Compare that with what Clover's Item sales report would show for the same week if every item has a cost entered: say COGS of $6,400, or 29.9% of net sales. The 2.8-point gap between theoretical (29.9%) and actual (32.7%) is waste, over-portioning, theft or a stale recipe cost. Clover can give you the first number. Only your invoices and counts can give you the second, and the gap is the number worth managing.
| Week | Net sales (Clover) | Theoretical COGS (Clover) | Actual food cost (invoices and counts) | Gap |
|---|---|---|---|---|
| Oct 6 to 12 | $20,900 | $6,270 (30.0%) | $6,850 (32.8%) | 2.8 pts |
| Oct 13 to 19 | $21,400 | $6,400 (29.9%) | $7,000 (32.7%) | 2.8 pts |
| Oct 20 to 26 | $22,100 | $6,560 (29.7%) | $7,520 (34.0%) | 4.3 pts |
The third week is the one to investigate: sales went up, theoretical cost held, but actual cost jumped.
What to do next
Decide which of the walls above you actually hit. A single-location owner who only wants to reconcile the day may never need more than the Sales Overview and a weekly CSV. If the question is "what is my food cost or prime cost," pick a method from the workaround list this week: either enter item costs and accept theoretical cost, or set up the invoice-and-count routine from the example. If you run two or more stores, confirm with Clover support that they are chained under one enterprise before you expect a roll-up. And whichever route you take, save every export the day it arrives, because requested reports disappear after two weeks.