> ## 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.

# Real-time monitoring

> See orders and operational signals as they happen across every connected channel.

Spreadsheets tell you yesterday. **Real-time monitoring** tells you whether lunch service is holding right now — across app, aggregators, kiosk, and call center — before guests churn and before the kitchen discovers a surprise backlog.

## When live visibility matters

| Situation                           | Why waiting hurts                              |
| ----------------------------------- | ---------------------------------------------- |
| Aggregator surge during bad weather | Prep and staffing misaligned                   |
| New menu rollout                    | Early error rate on modifiers or 86 gaps       |
| Store offline on one channel only   | Sales leak silently                            |
| Promo day                           | Need instant read on mix, not next-week report |

Operations leaders should not refresh three tablets and a POS screen to answer “how are we doing?”

## What Fire spark surfaces

* **Order flow by channel** — Volume spikes and quiet stores as they occur.
* **Store health** — Which locations are accepting orders on which surfaces.
* **Menu sync status** — Confidence that what customers see matches what the POS can produce.
* **Fulfillment load** — Pickup vs delivery pressure during peak ([fulfillment types](/docs/concepts/fulfillment)).

Monitoring complements [consolidated analytics](/docs/case/consolidated-analytics): live for **triage**, historical for **strategy**.

## Who benefits

| Role            | Use                                                             |
| --------------- | --------------------------------------------------------------- |
| Operations / GM | Spot bottlenecks and channel outages during service             |
| Marketing       | Watch promo day performance without begging ops for screenshots |
| Support         | Answer “where is my order?” with shared channel context         |
| Leadership      | Pulse check during expansion or new aggregator launch           |

## Peace of mind for commercial teams

Launching a new channel or marketplace does not mean flying blind for forty-eight hours. You see tickets enter the same operational path your kitchen already uses — **as they happen** — not buried in a partner email tomorrow.

<CardGroup cols={2}>
  <Card title="Orders" icon="receipt" href="/docs/concepts/orders">
    How purchases route to your POS
  </Card>

  <Card title="Integrations" icon="plug" href="/docs/integrations/index">
    Connected POS and channels
  </Card>

  <Card title="Quickstart" icon="rocket" href="/docs/quickstart">
    Connect and validate before go-live
  </Card>
</CardGroup>