Stores

A store is a real place — restaurant, dark kitchen, kiosk site, or pickup point — where your team prepares orders and customers collect or receive them. In Fire spark, every order ties to a store so menus, hours, and fulfillment rules stay accurate per location.

​

Why stores matter for commercial teams

​

Stores and channels

Channels are where customers tap to order. Stores are where the order is made and completed. The same store often appears on several channels; Fire spark keeps one record of that location so you do not configure it separately per aggregator.

​

Stores and your POS

Your POS or RMS usually already defines locations. Fire spark maps those stores to channels so menu sync and order injection stay aligned with what happens on site.

​

Labor: employees and roles

Under Stores → Labor you manage the people who work in your stores.

• Employees have a name, one role, and one or more stores. Email and phone are optional.
• Roles describe the job (for example Waiter or Cook). Every new merchant starts with Waiter, Manager, and Cook. You can rename or delete Waiter and Cook and add your own roles.
• Manager is a system role. It can’t be renamed, edited, or deleted. Managers need a PIN, which they use to authorize sensitive actions on the POS.
• One manager per store. A store can have only one active employee with the Manager role. Stores that already have a manager are hidden when you assign stores to another manager.
• Deleting a role in use is blocked. If any active employee still has the role, the delete fails with EMPLOYEE_ROLE_IN_USE. Move those employees to another role first.

​

Related concepts