Net sales = gross sales − discounts − returns, according to Shopify’s sales-report definitions. That formula is a useful check, not proof that a Sidekick answer is ready to guide a business decision.

Treat every Shopify Sidekick 2026 sales report as an analysis result to verify—not as a completed data audit. Confirm the business question, store and market scope, date range, filters, metric definition, and exported fields. Then compare the same view in Shopify Analytics. If results differ, investigate the scope and metric before drawing conclusions from Sidekick’s explanation.

This runbook is for Shopify operators checking sales data before changing a store or campaign; finance and data collaborators reviewing exports; and store owners who need a repeatable handoff process. If you only need a quick summary and will not act on it, you may not need the full review.

Set the decision target before interpreting the report

Start with the decision, not the summary. Write down what you need to establish: for example, whether sales changed for a particular market during a defined period, or whether a named product group met a sales target. A question such as “How are sales doing?” leaves too much room for the report to select a scope or metric that does not answer your operational question.

Shopify describes Sidekick as a tool that can help with analytics and reporting tasks, including creating or editing data explorations. Those capabilities can speed up analysis, but they do not make the result an independent audit. Keep the official Sidekick guidance in view when you decide what to ask and what the generated result can establish.

Before you read a conclusion, capture these items in a review note:

  • Decision: What action might follow from this report?
  • Store and subject: Which store, products, customers, or other group does the question cover?
  • Market: Which sales market or region should the analysis represent?
  • Period: What start and end dates do you need?
  • Metric: Which measure answers the decision?
  • Filters and dimensions: What conditions or groupings must remain consistent?
  • Evidence: Which report view and exported file will you use to check the answer?
If the question does not identify the relevant store, market, or period, stop and refine it before interpreting the output. A polished summary cannot repair an undefined query.

**Review boundary:** Sidekick’s written explanation, the report’s displayed values, and the data in an export are separate pieces of evidence. Record which one supports each conclusion.

Check scope before comparing results

A report can appear inconsistent simply because the two views answer different questions. Confirm that the Sidekick result and the comparison report refer to the same store and subject. Then check the date range, market, filters, and dimensions. Keep the original question or prompt with the review record so a colleague can see how the report was requested.

Shopify’s report documentation explains that reports can use filters and different ways of grouping data. Its guide to report time ranges also covers setting and comparing periods. Use those controls deliberately: a comparison is meaningful only when the selected dates and comparison settings match the business question.

For cross-border operations, a market filter and date selection can change what the report represents. A report for one market is not a substitute for a whole-store view. Similarly, two reports that use different date boundaries should not be treated as a like-for-like performance comparison.

Use this scope check before you evaluate any metric:

  • Confirm the store or account shown in the report.
  • Check that the products, customers, or other subject group matches the request.
  • Confirm the market and every active filter.
  • Verify the start date, end date, and any comparison period.
  • Preserve those conditions in the handoff note, even if the export does not include them.
If you cannot reconstruct the original scope from the report or your notes, mark the result **Needs evidence**. Do not fill gaps with assumptions about what Sidekick probably selected.

Match the metric to the decision

The report’s metric must answer the question you started with. “Sales” can mean different things depending on whether you need gross sales, net sales, orders, or another measure. Read the report label and its definition before using the value in a decision or a financial handoff.

Shopify’s sales-report documentation distinguishes the components that make up its sales measures. For example, gross sales are adjusted by discounts and returns to produce net sales; shipping and taxes are also represented in the sales-report definitions. Confirm which measure appears in your report rather than treating these components as interchangeable.

Keep three layers separate:

  • Metric definition: What Shopify says the selected measure includes.
  • Report result: The value and dimensions displayed in the report.
  • Sidekick explanation: The natural-language interpretation of that result.
An explanation that says sales fell because of returns is not evidence of that cause unless the report or supporting records show the relevant return data. The same rule applies to discounts, market changes, and other possible explanations. Treat an unsupported cause as a hypothesis to investigate, not as a report finding.

When a team uses a custom query, review the measure and grouping in the query itself. Shopify’s ShopifyQL syntax reference can help you inspect how a query expresses fields and conditions. Do not assume that two reports are equivalent because their titles sound similar.

Assign a status to each metric before sharing it:

  • Pass: The definition and dimensions answer the original question.
  • Needs evidence: The label is unclear, the grouping differs, or a required condition is missing.
  • Fail: The selected measure does not answer the business question.
This status is a review aid, not a Shopify certification or audit result.

Inspect the export as a separate artifact

An exported file needs its own check. A report view can be understandable while the downloaded file is missing context, has unexpected columns, or opens with a display issue in your spreadsheet application. Shopify’s report export guidance explains the supported export process. Check the current instructions for the report you are using rather than assuming that every report offers identical export options.

Keep the report view and the file connected. Save the report name, query or source, date range, filters, market, and export filename together. If the file does not retain those settings, put them in a separate note with the file. A teammate should be able to identify which report produced the export without guessing.

For a file review, use this sequence:

  • Compare the exported headers with the report’s metric names and dimensions.
  • Check whether expected rows and fields are present before editing the file.
  • Confirm that the file opens with the intended columns and readable values.
  • Preserve an untouched copy before sorting, removing fields, or adding formulas.
  • Test a small copy in the target spreadsheet application before using the file for handoff.
If you use Mac Numbers, follow [Apple’s instructions for importing files into Numbers](https://support.apple.com/en-mide/guide/numbers/tan9f3c54bdc/mac). Import behavior can depend on the file and the import choices. Verify the displayed columns and values in your own file; do not assume compatibility or formatting based on the file extension alone.

**Do not repair the evidence in place.** If a file looks incomplete, keep the original and document the problem first. Re-export only after you have checked the report settings and export procedure.

Cross-check the same view in Shopify Analytics

Use Shopify Analytics to reproduce the result when the report will support a consequential decision, a finance review, or a handoff that another person must be able to repeat. Shopify’s reports overview describes report controls such as filters. Use the matching report or data exploration, and align its scope and measure with the Sidekick result.

Compare these elements before comparing the values:

  • Store and subject group.
  • Market and active filters.
  • Date range and comparison period.
  • Metric definition and dimensions.
  • Export headers and the report view they represent.
If a difference remains, narrow it down in that order. First recheck scope. Then inspect the metric definition and grouping. Next compare the visible report with the exported fields. Shopify also provides guidance on [investigating sales discrepancies in Analytics](https://help.shopify.com/en/manual/reports-and-analytics/discrepancies/sales-discrepancies). Use it to investigate the mismatch; do not use a difference alone to infer a cause.

Mark an unexplained difference Needs evidence and keep it open. Do not average the values, choose the one that looks more plausible, or add a causal explanation that neither report supports. If the reports use different conditions, correct the comparison and repeat the check before handing off a conclusion.

Choose the next action by evidence status

Use these decision branches to decide whether the report can move forward:

  • If the business question, scope, metric, and export all match, mark the result Pass and share the report context with the value.
  • If the date range, market, or filters are missing or inconsistent, return to the report settings and recreate the comparison before interpreting the result.
  • If the metric label or definition does not answer the decision, select a suitable measure and review the result again; do not rely on the summary wording.
  • If the export is incomplete or displays unexpectedly, preserve the original file, inspect the export procedure, and test a fresh copy before editing or handing it off.
  • If Sidekick and Shopify Analytics still differ after scope and metric checks, mark the difference as pending and follow the Shopify discrepancy guidance rather than inventing an explanation.
A report is ready for a business handoff only when another person can reproduce the question and understand what the result measures. If your evidence does not support that, pause the decision and request the missing context.

FAQ: reviewing Sidekick sales exports

Confirming the report period

Keep the original question beside the report’s selected date range. Reopen the corresponding Analytics report or data exploration and inspect its date controls and comparison period. If the exported file does not preserve those settings, record them separately before sharing. Do not compare reports until their periods and relevant time-zone assumptions match.

Comparing a Sidekick export with Analytics

Compare the export with Shopify Analytics when the result will inform a financial review, a store change, or a team handoff. Recreate the same metric, dimensions, period, and filters. If values differ, investigate scope, definitions, and file contents. A mismatch alone does not prove which result is wrong or establish why the difference occurred.

Investigating missing export content

Check the exported headers and visible rows against the report view. Verify that filters and dimensions did not change, confirm that the file opened with the expected columns, and check whether the export completed. Preserve the untouched original. Test a copy in your spreadsheet application before sorting, editing, or passing it to another person.

Reviewing metrics across time zones

Create a shared record with the store, market, date range, filters, metric, source report, and export filename. Ask the next reviewer to recreate the comparison in Shopify Analytics rather than relying on a written summary. Keep unexplained differences marked as pending and include enough context for a colleague in another time zone to repeat the review.

Hand off the evidence, not just the conclusion

A useful handoff includes the business question, report context, selected metric, exported file, comparison result, and any unresolved differences. Keep the file’s original state available, and make edits in a separate working copy. This lets the next reviewer distinguish the Shopify report from later spreadsheet work.

If your team regularly reviews exports in macOS, a remote Mac can be an optional shared work environment for opening files in Numbers and coordinating a handoff. It does not change Shopify’s report data or make a result more accurate by itself. You can review MACGPU’s remote Mac environment options if you need that kind of workspace; use your existing local setup if it already meets your team’s access and collaboration needs.

A remote Mac is not the right answer for every team. If you need a dedicated machine for continuous, heavy workloads or physical connections, evaluate owning and operating a Mac instead. For short-term review work or a team that needs a macOS environment without buying hardware, compare the ongoing access and handoff needs with MACGPU’s available Mac plans. Keep the decision about the workspace separate from the decision about whether the sales report itself is verified.