> For the complete documentation index, see [llms.txt](https://codico-dispatch.gitbook.io/documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://codico-dispatch.gitbook.io/documentation/fleet-and-pricing.md).

# Fleet & Pricing

Set up your vehicle classes and every price the booking form calculates.

**Fleet & Pricing** holds your vehicle classes and all the price rules CodiCo Dispatch uses to calculate the price of a booking — in the admin console and in the website booking form.

| Menu item                      | What you set up there                                            | Read more                                                                                    |
| ------------------------------ | ---------------------------------------------------------------- | -------------------------------------------------------------------------------------------- |
| **Vehicles**                   | Vehicle classes, their capacity and base prices per kilometre.   | [Vehicle Classes](/documentation/fleet-and-pricing/vehicle-classes.md)                       |
| **Route Pricing**              | Special prices between two zones, per kilometre or fixed.        | [Route Pricing](/documentation/fleet-and-pricing/route-pricing.md)                           |
| **Additional services prices** | Extras such as child seats, meet & greet, pets and waiting time. | [Additional Services](/documentation/fleet-and-pricing/additional-services.md)               |
| **Day & Night Pricing**        | Different prices per weekday and for night hours.                | [Day & Night Pricing](/documentation/fleet-and-pricing/day-and-night-pricing.md)             |
| **Period pricing**             | Special prices for a date range, for example a high season.      | [Period Pricing](/documentation/fleet-and-pricing/period-pricing.md)                         |
| **Vehicle Availability Rules** | Which vehicle classes can be booked between which zones.         | [Vehicle Availability Rules](/documentation/fleet-and-pricing/vehicle-availability-rules.md) |

## How a price is calculated

Every vehicle class has **base rates** per kilometre. CodiCo Dispatch uses them for a booking when no special rate applies. Special rates — route pricing, period pricing and day & night pricing — override the base rates for the trips they cover. Extras from **Additional services prices** are added on top.

```mermaid
flowchart LR
    A["Base rates<br/>per vehicle class"] --> B{"Special rate<br/>for this trip?"}
    B -->|Route · Period ·<br/>Day & Night| C["Special price"]
    B -->|No| D["Base price"]
    C --> E["+ Additional services"]
    D --> E
    E --> F["Booking price"]
```

{% hint style="info" %}
In route pricing, period pricing and day & night pricing, a field you leave empty falls back to the base rates defined in the vehicle class.
{% endhint %}

Zones and airports used in route pricing and availability rules are set up in **Locations & Rules**. See [Locations & Rules](/documentation/locations-and-rules.md).

## Watch the videos

{% embed url="<https://www.youtube.com/watch?v=kl2qPfepigY>" %}
Flexible Pricing Settings — CodiCo Taxi Dispatch Software
{% endembed %}

{% embed url="<https://www.youtube.com/watch?v=GybWfdctUr8>" %}
Custom Zones and Smart Pricing — CodiCo Taxi Dispatch Software
{% endembed %}

Read more about the [CodiCo pricing system](https://codico.io/taxi-dispatch-software/pricing-system/) and compare the [CodiCo Dispatch plans](https://codico.io/wizard/).


---

# 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://codico-dispatch.gitbook.io/documentation/fleet-and-pricing.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.