> 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/check-bikes-in-and-out.md).

# Check bikes in and out

The handover at the counter uses two one-time codes, so the bike's record shows exactly when your shop took it and when the rider got it back. The owner and receptionists do this.

## Check in

1. When the rider arrives, open the booking in **Waiting check-in** on your **Dashboard**.
2. Ask the rider for their **check-in code** — 8 digits, shown on their booking card.
3. Type it under **Check in** and press **Check in**.

The bike is now in your custody. The booking moves to **Open**, and its jobs appear on the **Kanban** board for your mechanics.

![Sophie types Lena's check-in code](https://3342305839-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FUV849rO8Um1JqzscvFEf%2Fuploads%2Fgit-blob-87a47b9af75b594a9b58c7bb15e0211023a07b4c%2Fshop-checkin-code.jpg?alt=media)

The bike moves to **In the shop** under **Bikes in service**. Walk-in customers' bikes don't appear there — see [Walk-in customers](/guide/shop-owners/walk-in-customers.md). A wrong or expired code is refused.

![The Turbo Levo is now in the shop](https://3342305839-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FUV849rO8Um1JqzscvFEf%2Fuploads%2Fgit-blob-f6aa5f2f0b71271f402d370efe37c60ca770096a%2Fshop-checked-in.jpg?alt=media)

{% hint style="info" %}
A code works once and is valid for 10 minutes. If it has expired, the rider's card already shows a new one.
{% endhint %}

## While the bike is with you

The booking card shows each job — its part and service, its status and the mechanic on it. Found more work? Choose **Add task**: pick the part and the service, and it lands in the Open column for your mechanics.

**Bikes in service** on your Dashboard lists every customer bike tied to your shop: the ones on their way in and the ones already with you.

## Check out

1. When every job is **Done**, the booking moves to **Waiting check-out**, the bike shows **Check-out ready**, and the rider is notified. A bike can't be handed back while any of its jobs is still open.
2. Open the booking. It shows the **pickup code**.
3. Read the code to the rider. They type it on their booking card.

The booking is completed and the bike returns to the rider. Everything your team did — services, new parts, torques, weight — is written into the bike's permanent log.

![The pickup code for Lena's Turbo Levo](https://3342305839-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FUV849rO8Um1JqzscvFEf%2Fuploads%2Fgit-blob-5105c4376766ecc224a203e5606a985e468588a3%2Fshop-pickup-code.jpg?alt=media)

For customers without a BikeCheck account, see [Walk-in customers](/guide/shop-owners/walk-in-customers.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/check-bikes-in-and-out.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.