> 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/route-pricing.md).

# Route Pricing

Set special prices between two zones, per kilometre or as a fixed price.

**Route Pricing** sets special prices for trips between two zones, for example a fixed price from the airport to the city centre. Open it with **Fleet & Pricing → Route Pricing**.

The list shows each route price with **Zone A**, **Zone B**, the **Vehicles** with their prices, the **Priority**, and whether the price **Is fixed** and **By request (Auction)**. Click **Add new** to create a route price, **Edit** to change one.

## Add or edit a route price

<figure><img src="https://3342310576-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FCGCbj77Uf83iIZ9ZIqRp%2Fuploads%2FY8GIpJTYhCErh94qCr3D%2Froute-edit-v2.webp?alt=media" alt="Route pricing form with Zone A, Zone B, Priority, options, payment methods and the pricing table"><figcaption><p>A route price with per-kilometre rates by distance.</p></figcaption></figure>

| Field                    | What it does                                                                                                                                                     |
| ------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Zone a** / **Zone b**  | The two zones of the route. Zones are drawn in [Custom Zones](/documentation/locations-and-rules/custom-zones.md).                                               |
| **Priority**             | Required. If several route prices could match the same trip, the priority sets their order.                                                                      |
| **Is both directions**   | When on, the price applies from A to B and from B to A.                                                                                                          |
| **Is fixed**             | When on, the table shows one **Fixed price** per vehicle class instead of per-kilometre rates.                                                                   |
| **By request (Auction)** | Trips on this route are priced by request instead of automatically. See [Price offers](/documentation/bookings-and-dispatch/assigning-bookings.md#price-offers). |
| **Payment methods**      | The payment methods offered for this route, for example *Cash*, *Credit card*, *Bancontact* or *PayPal*.                                                         |

### The pricing table

The **Pricing** table has a column for every vehicle class:

* **Minimum fare** — the lowest price on this route.
* **Distance rows** — the price per kilometre from a distance onwards, for example *0– km*, *35– km*, *50– km*. Click **Add new** below the table to add a distance row, and the bin icon to remove one.
* **Fixed price** — with **Is fixed** turned on, a single fixed price per vehicle class.

{% hint style="info" %}
Fields you leave empty use the base rates of the vehicle class. See [Vehicle Classes](/documentation/fleet-and-pricing/vehicle-classes.md).
{% endhint %}

## Watch the video

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

Learn more about [custom zones](https://codico.io/taxi-dispatch-software/custom-zones/) and the [pricing system](https://codico.io/taxi-dispatch-software/pricing-system/).


---

# 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/route-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.
