> 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/fleet-and-showroom.md). # Fleet and showroom Your business can own bikes too. Turn on the **Fleet** and **Showroom** modules in Settings to use them (see [Set up your shop](/guide/shop-owners/set-up-your-shop.md)). ## Fleet Fleet bikes are bikes your business owns and uses: rental, demo or staff bikes. 1. Open **Fleet**. 2. Use the first card, **Add a bike**, to register one — the same form a rider uses. The card shows how many fleet slots you use, for example *0/1 in use*. ![An empty fleet with its first slot](https://3342305839-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FUV849rO8Um1JqzscvFEf%2Fuploads%2Fgit-blob-ddf64c480538e462c03e4b511bee0216d5bdc336%2Ffleet.jpg?alt=media) 3. Click a fleet bike to open its page: parts, service, log, and actions such as **Sell** and **Transfer**. 4. To give a bike to one of your fleet riders, open it and choose the **Fleet rider**. The rider is notified, and can view the bike's log, request service for it and report it stolen. Each fleet bike uses a fleet slot. The page shows how many you use and how many you have. ## Showroom Showroom bikes are bikes your business sells. 1. Open **Showroom** and use **Add a bike** to register and list one, with its price, description and photos. Each showroom bike uses a marketplace stall. 2. Or sell a fleet bike: open it in **Fleet** and choose **Sell**. It is listed and moves to the showroom. 3. **Move to fleet** takes a showroom bike off the marketplace and back into the fleet. When a buyer is interested, anyone on your team can accept the interest. The buyer then sees your **business** contact details. ## Receiving a bike by transfer or sale When someone transfers or sells a bike to your business, the code is bound to the business. Your owner or a receptionist can redeem it, and chooses whether the bike goes to the **Fleet** or the **Showroom**. If that module has no free slot, the bike is still added but locked, like any bike over capacity, until you free a slot or upgrade. ## Turning a module off If you turn Fleet or Showroom off, those bikes stay, but they become read-only — you can only open their logs. Turn the module back on and everything returns. --- # 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/fleet-and-showroom.md?ask=&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.