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

# Channels

> Every surface where customers discover your brand and place orders.

A **channel** is a sales surface — not a store, but the path the customer uses to order. Fire spark connects your operation to **owned channels** you control and **aggregators** where customers already search for food.

## Owned vs aggregator

| Type       | Examples                                              | Who controls the experience                     |
| ---------- | ----------------------------------------------------- | ----------------------------------------------- |
| Owned      | Mobile app, web ordering, in-store kiosk, call center | Your brand, your UX                             |
| Aggregator | Uber Eats, Rappi, PedidosYa                           | Marketplace app; your menu and offers inside it |

Commercial teams care about channels because each one is a **revenue and reach lever**. Operations care because each one must send accurate orders to the same kitchen — with the **menu** configured for that surface.

## Channel type

Every channel record includes a **`type`** that classifies the ordering surface.

| `type` value  | Surface                               |
| ------------- | ------------------------------------- |
| `APP`         | Branded mobile app                    |
| `WEB`         | Web ordering                          |
| `KIOSK`       | In-store kiosk                        |
| `POS`         | Point-of-sale ordering surface        |
| `CALL_CENTER` | Phone or call center ordering         |
| `AGGREGATOR`  | Marketplace or third-party aggregator |

Set `type` when you create a channel. It cannot change after creation — create a new channel if the surface classification changes.

In the dashboard, channels are grouped by `type` so you manage app, web, kiosk, and aggregator channels in separate lists.

## Menus per channel (and beyond)

Channels rarely need identical catalogs. Your app might carry the full menu; an aggregator might list a delivery-friendly subset; a kiosk might emphasize combos. Fire spark composes **different menus per channel**, and also per **store**, **fulfillment type**, or **schedule** — all rooted in the same POS sync, without standing up a separate integration per variation.

That is the commercial sweet spot: **strategic flexibility** on what each surface sells, **operational discipline** on where item data comes from.

## Planning channel mix

| Question                                  | Why it matters                                                   |
| ----------------------------------------- | ---------------------------------------------------------------- |
| Where do customers already find us?       | Aggregators for discovery; owned channels for margin and loyalty |
| Which stores go live on which channels?   | Not every location may be on every marketplace                   |
| Should this channel’s menu differ?        | Fees, UX, and assortment strategy vary by surface                |
| Do hours or fulfillment change the offer? | Breakfast hours or delivery-only items affect what you expose    |

## Related concepts

<CardGroup cols={2}>
  <Card title="Menus" icon="utensils" href="/docs/concepts/menus">
    How catalogs are composed per context
  </Card>

  <Card title="Stores" icon="store" href="/docs/concepts/stores">
    Locations fulfilling channel orders
  </Card>

  <Card title="Orders" icon="receipt" href="/docs/concepts/orders">
    Purchases placed per channel
  </Card>
</CardGroup>