> 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/build-your-catalogue.md).

# Build your service catalogue

Your catalogue is the list of services riders can book at your shop. You have two: one for bikes (standard, e-bike and cargo) and one for scooters (scooter and e-scooter). Services are grouped by part — the same layout as a bike — so when a rider books a specific part, only the services for that part are offered. Use the **Bikes | Scooters** switch at the top to move between your bike services (with their bike, e-bike and cargo price and time) and your scooter services (scooter and e-scooter price and time, laid out like a scooter: deck, folding mechanism, the e-scooter's electrical parts). These are two separate catalogues: a bike is always booked from the bike catalogue, a scooter or e-scooter from the scooter catalogue. A part both have, like a tire or a brake, has its own services in each — so you can name and price scooter work differently from bike work.

![Radwerk Bergmann's catalogue](https://3342305839-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FUV849rO8Um1JqzscvFEf%2Fuploads%2Fgit-blob-4f76f04bf5f1153904e0cad07e17c9243c74ef9d%2Fcatalogue.jpg?alt=media)

## Built-in services

Each of your two catalogues starts with its own set of **built-in** services that BikeCheck needs to keep bike records right:

* **Install**, **Remove** and **Replace** for each part — when the job is done, the bike's parts list is updated;
* **Wheel relacing** for each wheel;
* **Lower Legs Service** and **Full Service** for forks;
* **Serial number check** (free, always present);
* **Weight the bike**.

You can set the price and time of a built-in, but you can't rename or delete it.

## Add a service

1. Open **Catalogue** and pick **Bikes** or **Scooters** with the switch at the top.
2. Under the part the service applies to, choose **+ Add service**.
3. Give it a **name** — what riders will see, for example *Drivetrain service*.
4. Set **Bike pricing**: a price range and a time range (in minutes) for a standard bike. Use a range — *from* and *up to* — when the price depends on the bike's condition.
5. Set the other prices the same way — **E-bike** and **Cargo** on the Bikes side, **Scooter** and **E-scooter** on the Scooters side. Riders with those vehicles are quoted these. Existing services started with the scooter price equal to the bike price and the e-scooter price equal to the e-bike price — adjust them if scooter work costs you differently.
6. Choose **Save service**.

The pencil icon edits a service, the bin removes it (after a confirmation).

## Back up or copy your catalogue

* **Export data** downloads your catalogue as an XML file.
* **Import data** loads services from such a file. New names are added; names you already have are listed so you can choose to import a second copy or skip them. Built-in services are never exported or imported.


---

# 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/build-your-catalogue.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.