> ## 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. # Stores > Physical locations where your operation runs and orders are fulfilled. 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 | Use | What it enables | | ---------------- | --------------------------------------------------------------------------- | | Local presence | Customers order from the store nearest them | | Menu and pricing | Items and prices can vary by location when your POS does | | Channel mix | One store can serve app, web, Uber Eats, and kiosk at once | | Operations | Kitchen and staff work against a known location, not a vague “brand online” | ## 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. ## Related concepts Sales surfaces linked to stores Pickup and delivery per store and channel Catalog available at each store