How connection works
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.
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.
Build owned channels
For app, web, kiosk, and more, Fire spark helps you ship the channels you
want with the Storefront API (customer
experience) and the Admin API (operations, bulk
data, and migration). Same menus and orders; your brand, your UX.
What we connect
POS & RMS
Toast, Aloha, Symphony, and Fire POS — our own RMS
Aggregators
Uber Eats, Rappi, PedidosYa
Owned channels
App, web, kiosk, WhatsApp, call center, and more
Integrations API
For POS partners and deep operational sync
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 is available if you want one stack built for omnichannel |
Partner-specific setup details are documented per integration. Your Fire spark
contact can confirm availability and timelines for your stack.