Run the entire rental cycle, from booking to deposit release, in one system

A rented car is the most expensive asset that leaves your branch. A photo not taken at handover turns a scratch found at return into an argument. Availability kept in a notebook or a spreadsheet leads to the same car being promised to two customers. A car rental app puts that chain on the record: availability, contract, deposit hold, condition report and post-return charges all live in the same rental record.

How many separate apps does this need?

  • 01

    Customer Mobile App (iOS + Android)

    Date and pickup location selection, availability by vehicle group, add-on and waiver options, deposit pre-authorisation, digital contract signing, plus toll and traffic fine notifications throughout the rental period.

  • 02

    Handover and Return Staff App

    Vehicle handover flow at the branch or the customer's address: mandatory exterior and interior photo capture, odometer and fuel level entry, existing damage marking, customer signature, offline operation with later sync.

  • 03

    Fleet and Reservation Management Panel (Web)

    Vehicle records, calendar by licence plate, seasonal pricing and minimum-day rules, service, inspection and insurance due dates, post-return extra charge invoicing, blacklist and rental reports on a single screen.

What the app includes

  • In-app rental extension with fare-difference charge
  • Additional driver setup with licence record
  • Add-on stock: child seats, winter tyres, navigation
  • One-way drop fee and inter-branch fleet balancing
  • Hourly late-return fee tiers before a full day
  • Fuel gauge photo and missing-fuel charge
  • Cleaning and prep task card with ready-to-rent status
  • Class upgrade offer with price difference at pickup
  • Excess-reduction packages plus tyre and glass cover
  • Service, roadworthiness test and insurance due-date alerts
  • Blacklist and past-rental damage history per renter
  • Manual plate assignment and shifting on the fleet calendar

State of the sector

In car rental, the competition is no longer the branch down the street — it is the comparison sites that come first in search results. Customers see the price there, book there, and arrive at your company with a commission attached. A regional firm without its own booking channel rents out the same car for less margin and never even gets the customer's contact details. Phone reservations, meanwhile, stay in one person's notebook; idle days, forgotten returns and uncollected damage charges never become visible. For most operators, making utilisation and collection visible pays back faster than growing the fleet.

Metrics that matter here

  • Fleet utilisation rate (rented days per vehicle) — Group-based availability and online booking make idle days visible and let you fill them with last-minute rentals.
  • Vehicle turnaround time (from return to being rentable again) — Digital return reports and a preparation task flow shorten the cleaning and inspection wait so the car can go out again the same day.
  • Damage and extra charge collection rate — Photo-backed condition reports, deposit holds and delayed fine/toll matching stop disputed amounts from being absorbed by the company.
  • Share of direct reservations (commission-free channel) — Your own app and a repeat customer database move part of your rentals off broker commission and into the direct channel.

Common mistakes in this sector

  • Building availability around individual cars instead of groups Customers pick a class, not a licence plate. Once stock is tied to a plate, one late return locks up the chain and staff end up swapping plates by hand. Build a group pool and leave the vehicle assignment until handover.
  • Making the handover photos optional On a busy day staff skip the step, and the scratch dispute at return has no evidence behind it. The photo flow must be mandatory, with a fixed number of angles and offline capability; a rental should not be able to start with an incomplete report.
  • Charging the deposit as a payment Taking real money off the card drags out the refund process and creates complaints and lost commission. The deposit should be held by pre-authorisation, its validity monitored, and released the same day on a damage-free return.
  • Ignoring charges that arrive after the rental closes Tolls and traffic fines land after the car has been returned; in a system where a closed rental cannot take new charges, those amounts stay with the company. The rental record must remain open for later invoicing.

Regulation and compliance

Car rental is a licensed activity with reporting obligations: details of the rented vehicle, the renter and the driver must be reported to the relevant public system, so the app has to keep contract data complete and exportable. Images of ID cards and driving licences are personal data under KVKK (Turkey's data protection law, aligned with GDPR): the lawful basis is performance of a contract rather than explicit consent, a retention period is defined, and the data is deleted when it expires. Vehicle location data must also be disclosed in the privacy notice. e-Arşiv invoices (Turkey's mandatory e-invoicing system) must be issued for rental fees and extra charges.

The real challenges in this sector

  • Group-based availability and the double-booking risk

    Customers rent a vehicle group, not a specific licence plate, so stock has to be calculated against a group pool rather than individual cars. A late return must not cancel the next reservation; the system should be able to swap plates automatically within the group. A buffer period is defined per group for cleaning and preparation, and when several people try to book the last car in a pool at once, a locking mechanism reduces those attempts to a single reservation.

  • Making the handover and return report hold up as evidence

    What ends the argument over a scratch found at return is the photo taken at handover. The app enforces a guided, angle-by-angle mandatory photo flow, stamps every frame with time and location, and has damage marked on a vehicle diagram. There is no connectivity in an enclosed car park, so records are held on the device and uploaded once there is signal. On the return screen the handover photos are shown side by side, and the report is locked with the customer's signature.

  • Deposit holds and pre-authorisation validity windows

    Payment collection in car rental is not a single step: the rental fee is charged, while the deposit is only held on the card. Pre-authorisation validity varies by bank; if it lapses, the hold drops off by itself and the security is gone. The flow is built to renew the hold on extended rentals, release it the same day when the return is damage-free, and capture only the relevant amount when there is damage.

  • Charges that arrive after the rental has ended

    Toll crossings reach the company days later and traffic fines weeks later, long after the car has been returned. The system matches every toll and fine record to the rental in effect at that date and time, notifies the customer along with the service fee, and issues the e-Arşiv invoice (part of Turkey's mandatory e-invoicing system) afterwards. If a card is on file, collection is attempted; if not, a payment link is sent and the item stays open on the follow-up list.

  • Tracking mileage and usage with telematics data

    Location and odometer data from the OBD or GPS unit in the car is useless if it does not match the rental in the app. Device data is linked to the vehicle record; daily mileage limit overruns are calculated automatically, and leaving the city or breaching a cross-border restriction triggers an alert. Vehicle location is exposed only to authorised staff, within the scope stated in the contract, and historical trail data is retained for a defined period.

Required integrations

  • Virtual POS pre-authorisation / deposit holds (iyzico, PayTR or Craftgate — Turkish payment providers — or a bank virtual POS)
  • e-Arşiv and e-Fatura integrator (Turkey's mandatory e-invoicing system, GİB-compliant, for post-return extra charge invoices)
  • Importing HGS/OGS motorway toll records into the system by vehicle licence plate
  • Telematics / OBD-GPS device provider (location, mileage, ignition data)
  • SMS OTP or e-signature infrastructure for rental contract approval
  • Reservation transfer for car rental marketplaces and broker channels (channel management)

Who this page is for

  • Regional rental company with one branch and 10-30 cars

    The priority is the availability calendar and photo-backed handover forms. Phase 1 alone is enough; telematics and channel links can wait, and payment can stay at the desk for a while.

  • Seasonal operator at an airport or holiday region

    Seasonal pricing, flight-time meet-and-greet, multilingual contracts for foreign renters and online payment come first. Phase 2 should be pulled forward and channel links planned before the season.

  • New company entering long-term and corporate fleet rental

    Instead of a daily-rental flow, the need is contracts, monthly invoicing, driver assignment and maintenance-due tracking. Deposit holds matter less; telematics and mileage reporting belong in scope from the start.

A phased plan that splits the budget

  1. 1

    Phase 1 — Booking and handover core for a single branch 6-8 hafta

    Vehicle records, group-based availability calendar, rate and minimum-day rules, one shared booking pool for phone and web reservations, and a staff app with photo-backed handover and return forms. Payment still happens at the desk. This alone ends double bookings and undocumented damage, and works as a standalone system.

  2. 2

    Phase 2 — Online payment, deposit hold and customer app 5-7 hafta

    Card payment for the rental, a pre-authorisation hold for the deposit with expiry tracking, e-Arşiv invoicing (Turkey's electronic invoice for retail customers), post-rental toll and traffic-fine pass-through, plus a customer app for booking, contract approval and extension requests. Money flows are added only once Phase 1 has made record-keeping reliable.

  3. 3

    Phase 3 — Multiple branches, telematics and sales channels 5-8 hafta

    A second branch with one-way rentals and fleet balancing, mileage and location feeds from OBD-GPS units, automatic excess-mileage calculation, broker and marketplace bookings flowing into the same pool, long-term corporate contracts and utilisation reporting. This layer earns its cost once the fleet and the number of channels grow.

Typical scope and timeline

Typical scope: a customer mobile app, a handover and return staff app, and a web management panel. Included are a group-based availability engine, seasonal pricing, rental collection and deposit pre-authorisation via virtual POS, photo-backed digital condition reports, digital contract approval, e-Arşiv invoicing integration (Turkey's mandatory e-invoicing system), post-return extra charge recovery and core fleet reporting. Telematics and channel integrations are added depending on scope; scope and budget are set after a scoping call.

Estimated timeline: 12-18 weeks

Off-the-shelf or custom build?

Topic Off-the-shelf Custom build
Time to start Off-the-shelf rental software can be live the same week; for a small fleet it genuinely covers calendar and contract needs with low setup risk. A custom build takes weeks before the first working version, but from day one it runs on your own vehicle groups, rate rules and handover flow.
Company-specific rental rules Thresholds such as minimum age, licence years and deposit amount exist as settings in most packages and suffice for a standard rental flow. Your own exceptions — different licence thresholds per class, out-of-city permission, account-specific corporate rates — become an actual rule engine.
Cost model Usually a monthly fee per vehicle or user: cheap while the fleet is small, a permanent cost line as vehicles and branches multiply. A one-off development cost plus hosting and maintenance; adding vehicles costs nothing extra, while scope changes are separate work.
Data ownership and export Rental, contract and inspection data sit in the vendor's system; export is usually possible, but photo and signature archives often travel incompletely. The database and photo archive stay on your own servers, so exports can be shaped for statutory reporting duties and your accounting software.

Sector glossary

Vehicle group / SIPP code
What the customer buys is not a plate but a class described by a four-letter code: body type, doors, transmission, air conditioning. Availability and pricing run on the group; the plate is assigned at handover.
Pre-authorisation (deposit hold)
The deposit is not charged but held against the card limit. The hold has a bank-dependent validity window; when it lapses the security simply disappears. It is released on a clean return, or partly captured if there is damage.
Excess (damage liability limit)
The ceiling of damage the renter still pays. An excess-reduction package sold at booking lowers or removes it; tyres, glass and undercarriage are usually excluded and sold as separate cover.
One-way rental and fleet balancing
Returning the car at a different branch than pickup. A drop fee covers the price side, but the real issue is cars piling up in the wrong city; moving them back is planned as balancing.
No-show
A booking where the customer never turns up. The loss is real because the car was blocked that day; the system defines a grace period, a cancellation charge and automatic release back into the pool.

Frequently asked questions

Let us talk about your project

A free 30-minute call to scope it out, then an itemised quote within 48 hours.

Get a Free Quote

This page explains the problems an app must solve in this sector. We share references and comparable projects during the call.

Other sectors

All sectors →