> For the complete documentation index, see [llms.txt](https://docs.reportpundit.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.reportpundit.com/knowledge-base/settings/mcp-connector/how-to-run-a-report-for-a-different-date-range-in-claude.md). # How to run a report for a different date range in Claude You can run any of your reports for any period you like just by saying so. The report's own saved date range stays exactly as it is, so you never have to duplicate a report or edit it to look at a different month. This is the difference between a report and a question. The report is fixed. The question changes every time you ask it. ### Before you start Report Pundit connected to Claude, and the connector switched on for your conversation. See [How to connect Report Pundit to Claude](https://claude.ai/connect-report-pundit-to-claude). ### Ask for the period you want Include the period in the same message as the report. **A specific range:** > Run my Sales by Product report for 1 August to 31 August 2026. **A named month or quarter:** > Run my Sales by Product report for July. > Run it for Q2 this year. **A relative period:** > Run my Sales by Product report for the last 30 days. > Run my Refund report for year to date. Claude works out the actual start and end dates and runs the report for those. If the period matters, have it confirm: > Which exact dates did you use for that? This is worth asking for anything you are going to act on or share. "Last quarter" and "the last three months" are not the same range, and it is better to catch the difference before the analysis than after. ### Compare two periods A comparison is two runs, so it takes about twice as long. It is usually worth it, because the comparison is where the insight lives. > Run my Sales by Product report for August, then for July, and tell me what changed. > Compare this month against the same month last year and tell me which products moved most. Once both are in your conversation, keep asking. Claude has both sets of rows and does not need to run anything again. > Which products grew and which shrank? > Was the change driven by units or by price? ### What the date range does not change Only the period changes. Everything else comes from the report as you built it: * the fields it includes * the filters applied, and how they combine * the sort order * the report type So if your report is filtered to one sales channel, running it for a different month still gives you one sales channel. To change any of that, edit the report in Report Pundit. Your saved report is also untouched by this. The next time you open it in the app, or it runs on a schedule, it uses its own saved range as before. ### Date ranges follow your Shop Time Zone Reports are run against your store's time zone, which you can see under **Settings**, then **Account Details**, next to **Shop Time Zone**. This matters at the boundaries. An order placed late in the evening on 31 August may fall on 1 September for a store set to a different time zone than the one you are sitting in. If you are reconciling a report against Shopify or against your accounts and the totals are off by a small amount at the start or end of a period, this is the first thing to check. ### Reports where a date range does not apply Some reports describe a current state rather than a period. An inventory on hand report tells you what is in stock now, so asking for it "for July" does not have an obvious meaning. For these, ask for the report without a period and analyse the current picture: > Run my Inventory on Hand report. If you want inventory over time, use an inventory snapshot report instead, which records stock levels on a recurring basis and does respond to a date range. > **TO CONFIRM:** what happens if a user passes a date range to a Product Variant or inventory report? Is it ignored, does it filter on a different date field, or does it error? The answer belongs here, because merchants will try it. ### Common problems **The dates came back in the wrong order.** Give the range explicitly as `1 August 2026 to 31 August 2026` rather than a numeric format like `08/01/2026`, which is read differently in different countries. **No rows returned for a period you know has sales.** Check the report's filters first, since a filter can exclude everything for a given period. Ask Claude: > What filters does that report have, and what date range did you just use? **The period is outside your available data.** If you ask for a range earlier than your store's data goes back, or earlier than Report Pundit has synced, the report will come back empty or partial rather than wrong. Ask Claude what the earliest date in the results is if you are unsure. **A long range is slow or comes back incomplete.** Wide reports over long periods produce a lot of rows. Narrow the range, or ask for a summary rather than every row. See [Getting accurate results from large reports in Claude](https://claude.ai/claude-large-reports-best-practices). ### Related articles * [How to pull a report into Claude](https://claude.ai/pull-saved-report-into-claude) * [Questions to ask Claude about your Shopify reports](https://claude.ai/claude-analysis-questions) * [Getting accurate results from large reports in Claude](https://claude.ai/claude-large-reports-best-practices) * [Report Pundit and Claude: troubleshooting](https://claude.ai/claude-connector-troubleshooting)