Polygons work great for airport transfers pricing – but they quickly fall apart when rides aren’t strictly to or from airports.

Most operators rely on polygons for the classic lanes:
Airport → City or City → Airport.

But once you start pricing in-city and out-of-town rides, you can stuck with some bad options:

• One flat city rate (e.g., Milan–Milan) → less competitive and harder to protect margins
• Missing zones for real geography (need for numbers of polygons in each city, and outside that – Excel) → back to manual quoting

The result: slower response times, inconsistent quotes, and profit leaking through exceptions and pricing mistakes.

We’re excited to introduce a brand-new rate type in iTransfers: Transfer by mileage. This pricing model is based on distance and is designed specifically for scenarios where polygon-based logic doesn’t fit.

What it solves:

• Automated pricing based on configured parameters, such as price per km, pickup fee, included mileage etc.
• Flexible pricing for both in-city and out-of-town trips when zone pricing isn’t relevant
• The option to limit pickup areas: the rate only applies within your defined radius
• Advanced settings for long-distance rides (rules for extended mileage)

You set up a rate for each city and then define parameters for each vehicle class:

• Pickup radius
• Base price with included mileage
• Optional: pickup fare, rate for extra pickup radius
• Dynamic pricing for extra kilometers

When creating a ride, iTransfers also displays whether the rate was calculated by destination or mileage, so dispatchers and sales can instantly verify the logic and avoid mistakes.

This type of calculation is available along with other rate types such as Transfer by directions and Hourly rent.

Sales
Faster, consistent quotes for any address → higher conversion.

Ops/Dispatch
Less manual work, fewer errors during peak hours.

Management
Stronger margin control without flat city pricing or Excel exceptions.