> ## Documentation Index
> Fetch the complete documentation index at: https://help.atlas.kitchen/llms.txt
> Use this file to discover all available pages before exploring further.

# Explore Atlas Data Intelligence

> Ask questions about your restaurant data and explore insights through charts, tables, and summaries.

Atlas Data Intelligence helps you find insights in your restaurant data.
Ask for charts, tables, and summaries that compare performance and explain patterns.

Use it for questions such as "Which outlets grew last week?" or "Which products drove the change?"

## Start an analysis

> [!NOTE]
>
> Your account needs Atlas Data Intelligence permission.
> Contact your administrator or Atlas account manager if you cannot open it.

**1. Open Atlas Data Intelligence**

Sign in to the [Atlas Merchant Portal](https://portal.atlas.kitchen).
Select **Atlas Data Intelligence** from navigation, or [open it directly](https://portal.atlas.kitchen/atlas-data-intelligence).

**2. State the question and scope**

Name the outlets, dates, and measure you want to compare.
Specify net sales, order count, or product quantity rather than just "performance."

**3. Choose how to see the answer**

Ask for a line chart to show a trend, or a table to compare exact values.
Request a short summary of the main findings.

**4. Follow up on a finding**

Ask about a particular outlet, product, or date range in the same conversation.
For example: "Break the largest decline down by product. Show the values behind your explanation."

You should receive an analysis of the requested data, with the chart or table you asked for.
If the result is too broad, narrow the outlets, dates, or metric and ask again.

## Questions to try

| Goal | Example question |
| - | - |
| See a trend | "Show daily net sales at Tanjong Pagar for 1–7 October 2026 as a line chart." |
| Compare outlets | "Compare net sales and order counts by outlet for 1–7 October 2026. Show a table." |
| Investigate a change | "Compare those outlets with the previous week. Break the largest sales decline down by product." |
| Summarise results | "Summarise the main findings. Separate facts in the data from possible explanations." |

## Check the analysis

> [!NOTE]
>
> AI can misread a question or draw the wrong conclusion.
> Reporting data can lag behind live operations. Do not use this page to confirm an immediate stock or order change.

Before acting on a finding:

* Check the outlets, exact dates, and comparison period.
* Check the metric definition. Net sales and gross sales are different measures.
* Ask for the table behind a chart or summary when the totals are unclear.
* Compare important figures with the [matching report](https://help.atlas.kitchen/reports/overview.md), using the same filters.
* Treat explanations as hypotheses unless the data supports them. A sales drop alone does not explain its cause.

For help with a live product or order, return to its page and open [Ask Atlas](https://help.atlas.kitchen/ai/ask-atlas.md).
For report filters, exports, and scheduled report deliveries, see [Using reports](https://help.atlas.kitchen/reports/using-reports.md).

## If you get stuck

| Problem | What to do |
| - | - |
| The page is missing or access is denied | Ask your administrator to check your permissions. |
| The analysis page fails to load | Use the retry control if shown. If loading still fails, refresh and sign in again. |
| The answer has no data | Narrow the dates and outlets. Check whether the matching report has data for those filters. |
| A total differs from a report | Match dates, outlets, metric definitions, and other filters. Ask for the underlying values before comparing again. |
| The result uses the wrong scope | Restate the outlet names and exact dates. Ask for one comparison table rather than separate unrelated answers. |

If the problem continues, contact [hello@atlas.kitchen](mailto:hello@atlas.kitchen).
Include the question, outlets, date range, and any error message.
For a mismatch, include the report name and filters too. Do not send passwords or access tokens.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.