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

# Integrations

> How Fire spark connects your operation to POS systems, aggregators, and owned channels.

Fire spark is built so you **do not replace what already works**. You connect the systems you have, sync menus outward, and grow channels from one place. Most merchants follow the same path.

## How connection works

<Steps>
  <Step title="Connect your POS or RMS">
    Link your operational system with **credentials in the dashboard** — no custom
    middleware to stand up before you see value. Fire spark reads menus, pricing,
    and availability from the source your team already trusts.
  </Step>

  <Step title="Go live on aggregators">
    Once your operation is linked, **menus sync automatically** to marketplaces
    like Uber Eats, Rappi, and PedidosYa. Price changes and 86s flow from your
    POS; you are not maintaining a separate copy per partner.
  </Step>

  <Step title="Build owned channels">
    For app, web, kiosk, and more, Fire spark helps you ship the channels you
    want with the [Storefront API](/docs/storefront-api/introduction) (customer
    experience) and the [Admin API](/docs/admin-api/introduction) (operations, bulk
    data, and migration). Same menus and orders; your brand, your UX.
  </Step>
</Steps>

You do not need three integration strategies. One hub sits between your kitchen and every surface customers order from.

## What we connect

<CardGroup cols={2}>
  <Card title="POS & RMS" icon="cash-register" href="/docs/integrations/pos-rms/fire-pos">
    Toast, Aloha, Symphony, and Fire POS — our own RMS
  </Card>

  <Card title="Aggregators" icon="store" href="/docs/integrations/aggregators/uber-eats">
    Uber Eats, Rappi, PedidosYa
  </Card>

  <Card title="Owned channels" icon="mobile" href="/docs/integrations/channels/app">
    App, web, kiosk, WhatsApp, call center, and more
  </Card>

  <Card title="Integrations API" icon="plug" href="/docs/integrations-api/introduction">
    For POS partners and deep operational sync
  </Card>
</CardGroup>

## Common concerns

| Worry                          | Reality with Fire spark                                                                                                                                  |
| ------------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------- |
| “Integration will take months” | POS connection starts with credentials; aggregators reuse the same menu sync                                                                             |
| “We will double-manage menus”  | Your POS stays source of truth; channels receive updates automatically                                                                                   |
| “We need a custom app team”    | Storefront API covers ordering flows; you focus on brand and UX                                                                                          |
| “Our POS is unusual”           | Supported systems connect through standard patterns; [Fire POS](/docs/integrations/pos-rms/fire-pos) is available if you want one stack built for omnichannel |

<Note>
  Partner-specific setup details are documented per integration. Your Fire spark
  contact can confirm availability and timelines for your stack.
</Note>