> For the complete documentation index, see [llms.txt](https://bikecheck.gitbook.io/guide/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://bikecheck.gitbook.io/guide/shop-owners/set-up-your-shop.md).

# Set up your shop

Open **Settings** to set up your shop's profile and what it does.

## Business modules

Your shop can do three things. Turn on the ones you need under **Modules**, then **Save modules**:

| Module       | What it gives you                                                                       |
| ------------ | --------------------------------------------------------------------------------------- |
| **Service**  | Service bookings from riders, walk-ins, the **Catalogue** and the **Kanban** task board |
| **Fleet**    | Bikes your business owns and uses — rental, demo or staff bikes — and fleet riders      |
| **Showroom** | Bikes your business sells, listed on the marketplace                                    |

Modules you turn off disappear from the menu. Keep at least one on. Your subscription price is built from the modules you use: see [Billing](/guide/shop-owners/billing.md).

![Modules in Settings](https://3342305839-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FUV849rO8Um1JqzscvFEf%2Fuploads%2Fgit-blob-8db20869d570508618c8d43cd5a4dabd6ea6fa36%2Fsettings-modules.jpg?alt=media)

## Business details

Under **Business details**, set the shop's public profile: name, description, phone, address and location. The location is how riders find you when they book a service. Choose **Save details**.

The **owner's first and last name** are required. When you take a job yourself (**Me** on the Kanban board), the card, the bike's service log, your metrics card and the team list show this name. Until it is filled in, **Me** is unavailable and your work shows as *Owner*.

## Display currency

**Display currency** sets the currency label on your catalogue prices and showroom bikes. It is a label only: the numbers you enter don't change.

## What owners see in the menu

| Item                     | What it's for                                                   |
| ------------------------ | --------------------------------------------------------------- |
| **Dashboard**            | Incoming bookings, bikes in service, team, holidays, shop score |
| **Catalogue**            | Your services and prices                                        |
| **Kanban**               | The task board your mechanics work on                           |
| **Fleet** / **Showroom** | Your own bikes, if those modules are on                         |
| **Metrics**              | Work and money per month                                        |
| **Billing**              | Your BikeCheck subscription                                     |

Next: [Build your service catalogue](/guide/shop-owners/build-your-catalogue.md).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://bikecheck.gitbook.io/guide/shop-owners/set-up-your-shop.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.