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

# Consolidated analytics

> Compare sales, mix, and channel performance in one view — not three platform exports.

Every aggregator dashboard tells you how *that* marketplace performed. Your app vendor has another slice. Finance still wants the POS report. **Consolidated analytics** is the commercial answer: *how did we do everywhere*, with the same definitions and time ranges.

## The pain without consolidation

| Scenario                              | Cost to the business                       |
| ------------------------------------- | ------------------------------------------ |
| Monday morning spreadsheet merge      | Hours lost; errors in channel attribution  |
| “Delivery is up” but margin is down   | Cannot see owned vs aggregator mix quickly |
| Store manager swears kiosk is winning | No cross-channel view by location          |
| Marketing cannot prove a test worked  | Test data trapped per platform             |

Fire spark already routes **all channel orders** through one hub. Analytics becomes a natural extension — same orders, same stores, same channel labels.

## What you can see together

| Dimension       | Questions it answers                             |
| --------------- | ------------------------------------------------ |
| Channel         | App vs Uber Eats vs web — volume, ticket, growth |
| Store           | Which locations over-index on delivery vs pickup |
| Menu / category | What sells where after a composition change      |
| Fulfillment     | Delivery fee impact, pickup share, custom types  |
| Time            | Lunch peak across channels; promo lift windows   |

This supports **commercial decisions**, not only finance close: where to invest app spend, which aggregator to prioritize, which store needs operational help.

## How it fits your workflow

1. **Operate normally** — Orders flow POS ← Fire spark ← channels.
2. **Review in one place** — Marketing and ops align on the same numbers.
3. **Act** — Adjust [menu composition](/docs/concepts/menus), shift promos, or fix a store-channel mismatch.

Pair analytics with [menus A/B testing](/docs/case/menus-ab-testing) to close the loop: hypothesis → result → rollout.

## Reassurance

You are not exporting CSVs from five portals every week. You are not re-keying revenue into a master sheet. The hub that syncs menus and routes orders is the same hub that **makes performance readable** across the network.

<CardGroup cols={2}>
  <Card title="Orders" icon="receipt" href="/docs/concepts/orders">
    Unified order model across channels
  </Card>

  <Card title="Real-time monitoring" icon="radar" href="/docs/case/realtime-monitoring">
    Live operational visibility
  </Card>

  <Card title="Omnichannel strategy" icon="route" href="/docs/case/omnichannel-strategy">
    Plan channel mix with data
  </Card>
</CardGroup>