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

# Quickstart

> Connect your operation to Fire spark and activate your first sales channels.

## Set up your account

Create a Fire spark account and open your merchant workspace in the [dashboard](https://firespark.cloud). From there you manage stores, channels, menu sync, and order routing across your network.

<Note>
  Detailed setup guides are being published. Use this quickstart for the
  recommended sequence; step-by-step walkthroughs will be linked as they ship.
</Note>

## Configure your omnichannel operation

<AccordionGroup>
  <Accordion icon="plug" title="Connect your POS or RMS">
    Link the system where your team already runs menus, pricing, and orders.
    Fire spark uses it as the source of truth and keeps every sales channel
    aligned with what happens in the kitchen.

    Learn more in [Connecting a merchant](/docs/guides/connecting-a-merchant) and
    browse supported systems in the [integrations catalog](/docs/integrations/index).
  </Accordion>

  <Accordion icon="store" title="Map stores and activate channels">
    Register each location and choose which surfaces it serves — owned channels
    (app, web, kiosk, call center) and aggregators (Uber Eats, Rappi,
    PedidosYa).

    See [Stores](/docs/concepts/stores) and [Channels](/docs/concepts/channels) for how
    locations and surfaces fit together.
  </Accordion>

  <Accordion icon="utensils" title="Sync menus and compose per channel">
    Pull menu structure, items, pricing, and availability from your operation
    into Fire spark. Operational updates stay tied to the POS; configure
    different menus by channel, store, fulfillment type, or schedule where strategy
    calls for it.

    Start with the [Menus](/docs/concepts/menus) concept and the [Integrations API
    introduction](/docs/integrations-api/introduction) for menu sync.
  </Accordion>

  <Accordion icon="truck" title="Set fulfillment options">
    Define how orders complete per store and channel — pickup, delivery,
    dine-in, and partner-specific rules. Fulfillment stays consistent with your
    operational stack while customers see the right options on each surface.

    Read [Fulfillment](/docs/concepts/fulfillment) for the model behind these
    settings.
  </Accordion>
</AccordionGroup>

## Validate before you go live

<AccordionGroup>
  <Accordion icon="radar" title="Monitor in the dashboard">
    Use the dashboard to confirm stores, channels, and menu sync status before
    customers place orders. Watch that orders from test surfaces route back into
    your POS or RMS as expected.
  </Accordion>

  <Accordion icon="code" title="Exercise the APIs">
    Technical teams can validate flows against the API references:

    * [Storefront API](/docs/storefront-api/introduction) — owned app, web, and
      kiosk experiences
    * [Integrations API](/docs/integrations-api/introduction) — POS and RMS
      partners, webhooks, and order injection
    * [Admin API](/docs/admin-api/introduction) — bulk customer data and operational
      queries

    Authentication endpoints are documented; full guides for each flow are
    rolling out on the roadmap.
  </Accordion>
</AccordionGroup>

## Next steps

You have connected your operation to Fire spark. Explore these areas to launch channels, optimize performance, and hand off to product and engineering.

<CardGroup cols={2}>
  <Card title="Omnichannel strategy" icon="route" href="/docs/case/omnichannel-strategy">
    Plan reach and consistency across owned channels and aggregators
  </Card>

  <Card title="Owned channels" icon="mobile" href="/docs/storefront-api/introduction">
    Build app, web, and kiosk on the Storefront API
  </Card>

  <Card title="POS and RMS integration" icon="link" href="/docs/integrations-api/introduction">
    Sync menus and inject orders from your operational stack
  </Card>

  <Card title="Core concepts" icon="book-open" href="/docs/concepts/index">
    Brands, stores, menus, orders, and fulfillment in one model
  </Card>
</CardGroup>