· Orqestra Team · 8 min read
How to Export Clover Sales Data: CSV, PDF and API
How to export Clover sales data step by step: report CSV and PDF exports from the Web Dashboard, item-level exports, and the Clover REST API for developers.
To export Clover sales data, open a report in the Web Dashboard (Reports, then Sales report, Item sales, Order types or Employee sales), set the date range and filters, and select Options then Export for a spreadsheet file (CSV on the Order types report), or Print for a PDF. For raw order and payment records, a developer or an integrated app uses the Clover REST API, which returns up to 1,000 records per page and limits date filters to 90 days per request. This guide walks through each path, what you get from it, and what you can build in a spreadsheet afterward.
All Clover behavior described here is taken from Clover's help center and developer docs as of 2026-10-27.
Export methods at a glance
| Method | Where | Format | Granularity | Best for |
|---|---|---|---|---|
| Sales report export | Reports, Sales report, Options, Export | Export file (Print gives PDF) | Daily or monthly totals, or a summary, with employee, device, order type and daypart filters | Weekly reconciliation, week-over-week |
| Item sales export | Reports, Item and Service sales, Export | Export file | One row per item (optionally modifiers), with quantity, net sales, COGS if costs are entered | Menu mix, top sellers |
| Order types export | Reports, Order types, Export | CSV (stated on Clover's help page); Print gives PDF | Payments and net revenue by order type | Channel mix (dine-in, online, delivery) |
| Employee sales export | Reports, Employee Sales, Export | Export file | Sales, refunds, charges and tips per employee | Server performance, tip reporting |
| Requested report | Any report with a range over 3 months | Emailed link, then export | Same as the report | History up to 5 years, one year per pull |
| Accounting Sync | Item sales and Sales Overview reports | Direct to QuickBooks Online | Summarized | Bookkeeping |
| REST API (orders, payments) | docs.clover.com, v3 endpoints | JSON | Every order, line item and payment | Custom dashboards, integrations |
| Export API | docs.clover.com, exports endpoint | Files, up to 1,000 objects each | Bulk orders or payments, 30 days per request | Backfilling history into another system |
Clover's help pages document search and filters for the Sales activity, Transactions and Orders screens, but not an export button on those lists, so for payment-level detail use a report export or the API.
Method 1: export a report from the Web Dashboard
These steps follow Clover's Sales report page and Item sales report page.
- Log in to the Clover Web Dashboard with an account that has the Access Reporting permission.
- From the left menu, select Reports, then the report you want.
- Choose a date range. Anything under three months opens immediately. You can reach back five years, but only one year per report.
- Set a Time range (business hours, a daypart, or a custom daypart such as 5:00 PM to 9:00 PM) if you want a window rather than full days.
- Apply filters: Employee, Device, Order type, and Section if you use Clover Dining.
- On the Sales report, set View by to Daily if you want one row per day in the file. Summary gives you one row for the whole range.
- Select Options, then Export, to download. Select Print to save a PDF instead. Clover's Order types report page states that Export is CSV and Print is PDF. The Sales and Item sales pages describe the same Print and Export buttons without naming the file type, so check the extension on your first download.
For the Item sales report, Clover adds two choices worth setting before you export. Revenue Items or Non-revenue Items picks which items appear. Display lets you add columns such as SKU, product code and Modifier Details, so one export can carry modifier quantities under each item.
Method 2: request a report for longer ranges
Select a range over three months and Clover opens a Request a Report dialog instead of running it. Confirm the range and filters and submit. Clover emails you when it is ready; open it from the link or from Reports, Requested Reports, then export as usual. Clover's Item sales page states that a requested report is viewable for 7 days and listed in history until day 14, after which you must request again. Download the CSV the day it arrives and file it.
Method 3: Accounting Sync to QuickBooks Online
On the Item sales and Sales Overview reports, Clover's help pages list an Accounting Sync button that syncs the report's data with QuickBooks Online. This is a summarized push rather than a file, so it suits bookkeeping, not analysis. If you want line-level detail in QuickBooks, a sync app from the App Market is the usual route; our list of Clover apps for restaurants covers the options.
Method 4: the Clover REST API
When a spreadsheet is not enough, a developer or an integrated app reads the data directly. The pieces you need:
A merchant ID and a token. The merchant ID appears in your dashboard URL and in every API path. For testing, Clover's merchant-specific API token page describes creating a token from a test merchant's dashboard under Settings, View all settings, API tokens, with permissions scoped per endpoint. Clover states that production apps use tokens obtained through OAuth, which is what an App Market app does when you install it.
The orders endpoint. GET /v3/merchants/{mId}/orders returns orders, per Clover's orders reference. Add expand=lineItems,payments,discounts to get items and payments in the same response, and a filter such as createdTime>=1760932800000 to bound the range. Times are in milliseconds since the epoch and amounts are integers in cents, so total: 4250 is $42.50.
The payments endpoint. GET /v3/merchants/{mId}/payments lists payments with amount, tender, employee and timestamps, per Clover's payments guide.
Paging. Clover's pagination page states the default page is 100 elements and the hard limit is 1,000, controlled with limit and offset. Nested lists (for example line items inside an order) are capped at 100.
The 90-day rule. Clover's filter documentation says time-based filters on orders, payments and refunds are restricted to a 90-day range per request. For a year, loop through four or five windows.
Rate limits. Clover's rate limits page lists 50 requests per second per app and 16 per token, with 10 concurrent requests per app, and recommends the Export API for data older than two months.
The Export API. For bulk history, Clover's Export API lets an app POST an export of ORDERS or PAYMENTS for a UTC window of at most 30 days, poll until the status is DONE, then download files of up to 1,000 objects each. It is not real-time, and files are deleted after 24 hours. Clover asks developers to request this permission during app review.
A simple nightly job that pulls yesterday's orders with line items and payments, converts cents to dollars, and appends to a table is a few dozen lines of code. That is what tools like Orqestra's Clover connection do on your behalf, so you see dayparts and item mix without running the job yourself.
Worked example: sales by weekday and daypart from one export
Take a 48-seat cafe doing about $62,000 a month that wants to know whether its new 3:00 PM to 5:00 PM menu is worth the extra cook. One Sales report export, View by Daily, for the four weeks of October 2026, gives 28 rows with net sales per day. Add a Weekday column in the spreadsheet (a WEEKDAY or TEXT formula on the date) and build a pivot: rows by weekday, values as average net sales.
| Weekday | Average net sales | Share of week |
|---|---|---|
| Monday | $1,640 | 11.1% |
| Tuesday | $1,720 | 11.6% |
| Wednesday | $1,890 | 12.8% |
| Thursday | $2,050 | 13.9% |
| Friday | $2,560 | 17.3% |
| Saturday | $2,780 | 18.8% |
| Sunday | $2,150 | 14.5% |
For the daypart question, run the same Sales report three more times with a custom daypart (7:00 AM to 11:00 AM, 11:00 AM to 3:00 PM, 3:00 PM to 5:00 PM), export each, and divide each daypart's net sales by the day's total:
Daypart share = Daypart net sales divided by Daily net sales
Over the four weeks the 3:00 PM to 5:00 PM window averaged $214 a day, or 10.4% of net sales. The extra cook costs $19 an hour for the two hours, or $38 a day plus payroll taxes, so labor in that window runs about 19% of its sales. That is high for a cafe but the window also sells about $1,498 a week it did not sell before, so the question becomes whether the gross margin on $214 covers $38 of labor plus the food, which it does at any normal food cost. A fuller breakdown by service period is in restaurant sales by daypart, and the daily sales report template gives you a sheet already laid out for the daily export.
Keeping exports useful
- Name files by report, range and store, for example
sales_daily_2026-10-01_2026-10-31_main.csv. - Export net sales, not amount collected, for any percentage. Amount collected contains tax and tips.
- Keep one running sheet per report and append each week rather than starting over.
- Note the business time zone and business hours in effect, since Clover reports use the business time zone and the default time range is your business hours.
- For item files, export with Modifier Details on so add-on sales are not lost.
Common mistakes
- Exporting amount collected and calling it sales. Tax, tips, service charges and gift card loads are in it.
- Pulling a year in one report. Clover allows five years of history but one year per report, and over three months becomes a requested report.
- Letting a requested report expire. It is gone after 14 days.
- Reading API amounts as dollars. They are cents.
- Hitting the 90-day filter limit and assuming the data is missing. Split the range.
- Forgetting the employee attribution rule. The order taker gets net sales, the payment taker gets amount collected; an export filtered by employee inherits that.