> ## Documentation Index
> Fetch the complete documentation index at: https://docs.chift.eu/llms.txt
> Use this file to discover all available pages before exploring further.
# Location
### Definition
A location is a physical or logical point of sale. It represents a store, a restaurant, a counter, or any place where sales happen.
### Purpose
Locations group sales, orders, and closures by place of business.
### Relationships
* A location contains orders, sales, closures, and products.
### Endpoints
| Method | Endpoint | Description |
| ------ | --------------------------------------------------------------------- | ------------------------------ |
| GET | [Get locations](/api-reference/endpoints/point-of-sale/get-locations) | Retrieve the list of locations |
***
## Managing locations
Depending on the connector, one POS connection can be linked to one or multiple locations. Chift gives you the possibility to manage locations in your software or let Chift manage them for you. We typically recommend letting Chift manage locations for you.
Different possibilities:
1. The connector can be linked to multiple locations:
* **Chift manages the locations.** One consumer is linked to one connection which is linked to one location. You don't have to pass the `location_id` query parameter — Chift filters data for you.
* **Chift does not manage the locations.** One consumer is linked to one connection which might be linked to multiple locations. You must pass the `location_id` as a query parameter, otherwise the API returns data for all locations.
2. The connector can only be linked to one location: you can pass the `location_id` as a query parameter but it's not mandatory.
This implementation gives you the freedom to choose how to use Chift depending on your situation.
**How to let Chift manage locations for you?**
Activate the post-connection when you enable a connector:
This does not impact billing — billing is done at location level.