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

# Omnichannel strategy

> Plan reach, channel mix, and brand consistency without multiplying integration projects.

Growing today usually means **more surfaces** — your app, your web, Uber Eats, Rappi, kiosks — not more operational chaos. An omnichannel strategy answers *where* you want to sell, *what* each channel is for, and *how* the customer experience stays coherent while operations stay sane.

## The problem teams hit

| Symptom                                             | What it usually means                         |
| --------------------------------------------------- | --------------------------------------------- |
| “We are on three delivery apps and nothing matches” | Separate menu copies per aggregator           |
| “Direct ordering is an IT project”                  | Owned channels treated as greenfield builds   |
| “Marketing wants a promo; ops needs a week”         | No single place to compose offers per channel |
| “We do not know which channel actually wins”        | Reporting trapped inside each platform        |

Strategy without infrastructure becomes slide decks. Fire spark turns channel decisions into **configuration** on one hub.

## How Fire spark supports the strategy

**One operational connection.** Connect your POS or RMS with credentials. That single link feeds aggregators and owned channels — you are not negotiating a new integration every time commercial wants another surface.

**Intentional channel mix.** Use aggregators for discovery and margin where it makes sense; use [owned channels](/docs/integrations/channels/app) for loyalty and direct revenue. Fire spark lets both coexist on the same stores and menus.

**Composed menus per surface.** Your app can carry the full catalog; Uber Eats a delivery subset; the kiosk combo-forward items — [composed from one POS source](/docs/concepts/menus), not three spreadsheets.

**Fulfillment that matches the promise.** Pickup on the aggregator, delivery on your web, drive-thru only where you have a lane — [rules per store and channel](/docs/concepts/fulfillment), not one-size-fits-all.

## A practical planning frame

| Question                              | Strategic lens                                     |
| ------------------------------------- | -------------------------------------------------- |
| Where do new customers find us?       | Aggregators, SEO, app store                        |
| Where do we earn margin and data?     | Web, app, kiosk                                    |
| What can each store actually fulfill? | Store + fulfillment matrix in Fire spark           |
| What should differ by channel?        | Menu composition and promos, not operational truth |

## Outcome

Commercial teams get a **roadmap they can execute**: turn on a channel, compose the menu, set fulfillment, measure in one place. Operations keep one kitchen workflow. That is omnichannel strategy that ships — not another year of middleware.

<CardGroup cols={2}>
  <Card title="Overview" icon="book-open" href="/docs/overview">
    Platform value and intelligence
  </Card>

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

  <Card title="Channels" icon="monitor-smartphone" href="/docs/concepts/channels">
    Owned vs aggregator surfaces
  </Card>

  <Card title="Comparison" icon="scale-balanced" href="/docs/comparison">
    Fire spark vs fragmented approaches
  </Card>
</CardGroup>