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

# Fire POS

> Fire spark's RMS — inventory, kitchen, and operations built for omnichannel.

**Fire POS** is Fire spark’s own **restaurant management system**. When you run on Fire POS, operations and omnichannel are designed together — not bolted on after the fact.

## What it covers

| Area           | What merchants get                                                       |
| -------------- | ------------------------------------------------------------------------ |
| Inventory      | Stock and item availability tied to what customers can order             |
| Kitchen        | Tickets and workflows your line already expects, fed from every channel  |
| Stores & menus | The same catalog that powers aggregators and owned channels              |
| Orders         | One queue whether the ticket came from Uber Eats, your app, or the kiosk |

You are not syncing *around* a legacy gap. Fire POS is the **operational home**; Fire spark is the **channel layer** on top.

## Connection

There is no fragile handoff to configure. Fire POS and Fire spark share the same platform DNA — menus, stores, and orders align by default. You focus on running service, not reconciling two vendors.

## When to consider it

* You are **starting fresh** and want inventory, kitchen, and omnichannel in one story.
* You are **tired of middleware** between POS and delivery marketplaces.
* You want **deeper features** (composed menus, custom fulfillment, intelligence) without asking an old RMS to catch up.

<Card title="Get started" icon="rocket" href="/docs/quickstart">
  Connect your merchant and explore channels
</Card>