---
sidebar_label: 'Overview'
sidebar_position: 1
---

# Stores

:::note
These articles use the stores import formats to describe stores, most important for producers of the store data (e.g. POS system integration creating stores). Since a store can contain tenant-specific extensions, use the Stores schema endpoints in your specific tenant to understand details on consuming store data.
:::

A **store** is the unit against which orders are placed in Future Ordering.

In practice, a store is a fixed location such as a restaurant, coffee shop, or bar. The store defines what can be ordered there, when it is open, when orders can be placed, and more.

At a high level, a store configuration answers four questions:

- **What can guests order?** Through order types, which connect the store to menus.
- **When is the store open?** Through opening hours rules.
- **How is the store represented operationally?** Through fields such as location, and mapping details.
- **(Optionally) How does the store production operate?** Through production stations and capacity schedules.

## Store documentation map

Use these articles to configure stores in detail:

- [Store configuration](./store-configuration) for top-level fields and store metadata
- [Opening hours](opening-hours) for condition-based opening schedules
- [Production and capacity](production-and-capacity) for slot duration, estimators, and capacity rules
- [Stations](stations) for kitchen/fulfilment station definitions

## Relationship to menus

The store does not define menu content directly. Instead, the store references menus order types, so each order type can present the correct menu for that location.

See [Menus overview](../menus/overview) for more information about menus.