Channels

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

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

​

Related concepts