FEZA innovation – Home
← All products

Development on request

Car Rental & Fleet

Car Rental Software

Link vehicle availability, handover records and return accounts to the same rental. We will define the scope of the vehicle rental software we will build around your own fleet, partner vehicles and branch operations.

  • Scope shaped around your workflow
  • Roles and record design
  • Integrations subject to conditions
Cars and a car key beside a tablet showing vehicle cards and inspection cards
  1. Discovery
  2. Scope and quote
  3. Development

A vehicle free in the calendar but in maintenance or late back

A vehicle may look free in the calendar while undergoing maintenance; a late return can disrupt the next handover. If photographs stay on phones, contracts in folders and deposits in separate spreadsheets, differences at return are hard to explain. A toll violation received later also requires finding the contract valid at that time.

In the software we will build, vehicles, reservations, handovers and returns will be linked through one rental. You will define reservation rules, maintenance blocks and additional driver details. Calendar availability and physical readiness for handover will be scoped as separate checks.

Your current process

  • Reservations, maintenance and handover documents are tracked in different places.
  • Old photographs and contracts must be found to explain return differences.

In the software we will build

  • Maintenance and rental periods will be considered in one availability model.
  • Handover and return records will be linked to the contract.

Vehicle rental from reservation to handover and return

Consider handing over a reserved vehicle and checking it on return. We will ask for a blank contract, handover form and return checklist. The same example will establish which records change when the vehicle is replaced, the rental extended or another driver added. Business rules will be documented as part of the development scope.

  1. 01

    Reservation and vehicle selection

    Dates, vehicle class, branch and maintenance blocks will be considered together. Your rules will define separate statuses for provisional vehicle holds and confirmed reservations.

  2. 02

    Contract and handover

    The renter, additional drivers and chosen services can be linked to your contract template. Mileage, fuel, accessories and handover photographs will be scoped within the same rental.

  3. 03

    Return and account settlement

    Return mileage, fuel and damage assessments will be comparable with handover records. Proposed additional charges, disputes and deposit settlement will be treated as separate decision steps.

Start with fleet scheduling and photographed vehicle handovers

Choose the first version around your most frequent rental model. Daily hire, long-term contracts and vehicles from partner fleets may need different accounting rules.

Using the fields in your handover documents, we will identify mandatory checks and authorised decisions. Automatically assigning damage liability, making legal decisions and unconditionally retrieving external penalty records are outside this proposed initial scope. Recording, review and authorised decision workflows can be designed for these matters.

  1. For the first version

    Fleet and calendar
    Vehicle records, classes, branches, reservations and maintenance blocks can form the initial scope.
    Handover and return
    Contract links, photographic checks, mileage, fuel and deposit status will be defined together.
  2. Added as needed

    Long-term hire and transfers
    Corporate customer accounts, vehicle replacements, branch transfers and maintenance lists can be added as needed.
  3. Dependent on external systems

    Tracking and invoicing
    Vehicle tracking, payment and Turkey's e-archive invoice system connections can be scoped separately if your provider offers API access.

Renting from your own fleet or a partner fleet

Creating a partner fleet vehicle record does not mean it is always available. We will define who confirms availability, who informs the customer about replacements and who prepares handover documents. Maintenance and branch transfers may take priority in your own fleet. If you use both models, renter accounts and accounts for the vehicle-owning company will be scoped separately.

Reserving vehicles

Your own fleet
Your business determines maintenance and reservation status.
Partner fleet
Availability and confirmation from the vehicle owner will be considered separately.

Handover records

Your own fleet
The branch checklist can be linked to the same vehicle record.
Partner fleet
The partner's handover document and responsible person will be scoped.

Accounts

Your own fleet
Renter accounts and deposits can be tracked.
Partner fleet
Partner reconciliation will be defined separately from the renter account.

Branch handover and deposit correction permissions

Driving licences, identity details, handover photographs and financial records need different access. The software we will build will let branch staff handle daily handovers while treating deposit corrections as a separate permission. Branch changes, document downloads and editing old contracts will be defined separately during discovery.

Branch and fleet staff

Branch reservations and handovers can be available within the role. Fleet staff can have separate maintenance, transfer and vehicle withdrawal permissions.

Accounts and management

Fields needed for payments, deposits and disputed accounts will be selected. Changing damage assessments and reopening settled accounts will be scoped separately.

Documents and permissions

KVKK, Turkey's personal data protection law, document retention, access logs and any location data processing will be assessed. Your business is the data controller; contracts and privacy notices will be discussed with your authorised adviser.

Evidence and decision history for disputed rental damage

When a renter disputes a mark found on return, handover and return records need to be reviewed together. The software we will build will scope links between photographs, explanations, inspectors and disputes in separate records. You will define the account status while the review is pending.

Later documents can be linked without changing the original handover record. If the vehicle is to be rented again, maintenance decisions and dispute accounts will proceed separately. For later fines or toll records, an authorised person will decide after checking the registration plate and time.

What makes the decision difficult

  • Photographs and explanations remain in separate messages during a dispute.
  • Deposit decisions and putting the vehicle back into use become confused.

Workflow to define in the project

  • Disputes, evidence and decisions can be linked to the same rental.
  • Vehicle status and an open dispute account will be tracked separately.

Matching registrations, mileage and deposits

We will review vehicle records, registration plates and old contract dates together. Open rentals, deposit balances and planned maintenance will be checked separately during migration. Sample files will show which handovers photographs belong to. Tracking or penalty service connections will be scoped only if your provider offers API access and the necessary data sharing can be defined.

  1. 01

    Review the source records

    We will map registration numbers, handover mileage and deposit records to contracts in a sample with renter details removed. Vehicles with changed registration numbers and rentals still open will be assessed separately.

  2. 02

    Trial transfer and review

    The trial transfer review will be scoped to compare departure and return mileage, open contracts and deposit balances together. Duplicate vehicles linked to the same registration and deposits with unclear refunds will be examined separately.

  3. 03

    Establish the connection requirements

    If API access is available for payment or vehicle records, we will review contract and registration matching and error responses. Otherwise, vehicle and rental file transfers or entry by your team will be considered.

Proposal scope from open rental records

Prepare blank contracts, handover and return forms, plus a damage dispute example. Remove identity and driving licence details. Add maintenance schedules and your partner fleet confirmation steps so we can define the first version's boundaries together.

  • Distinguish vehicle handover, return inspection and deposit decision roles.
  • Choose mileage discrepancy and open-contract priorities for the initial scope.
  • Prepare vehicle and deposit examples with renter details removed.

Registration matching, mileage discrepancies and open deposit examples will inform the proposal scope. The usage model, support and limits of payment connections under consideration will be discussed in writing.

How we work

We do not sell an off-the-shelf package: we design the software around your workflow, build the first version in short steps and keep running it after launch.

  1. 01

    Discovery

    We listen to how your business works, your team and the tools you use today.

  2. 02

    Scope and quote

    Modules, priorities and price are set out in a written quote.

  3. 03

    Development

    We show working versions at short intervals and move on with your feedback.

  4. 04

    Setup and migration

    We move your existing records across and help your team get started.

  5. 05

    Support

    We run the software on a subscription and keep it up to date and secure.

Frequently asked questions

Do traffic fines arrive in the software automatically?

If you use a service that looks up fines and it allows data transfer, an import is assessed within the project scope. Otherwise you enter the fine, and the software finds the agreement that was active at that time from the registration. The real value lies in the matching: when a fine arrives months later, finding out who was driving is hard work.

Can photo handover forms be made mandatory?

Yes. You define the angles to be photographed. Because a handover record without photos carries little weight in a damage dispute, we recommend setting it up so that a handover cannot be closed while any of these photos are missing.

Can bookings from our website be imported?

That depends on how your site is built; whether it will be a direct connection or a file import is settled during scoping. If you do not have a website, a simple booking form can be added to the scope.

Can we use data from our vehicle trackers?

If your tracking provider allows data sharing, mileage and location can be connected. Location tracking requires informing the hirer; how your rental terms cover this is a legal matter that we recommend reviewing with your legal adviser.

Can we manage corporate and long-term rentals separately?

This can be included. Vehicles assigned to a corporate customer, driver allocations, vehicle swaps and consolidated monthly invoicing are designed as a structure separate from daily rentals.

We have several branches. How are vehicles tracked between them?

Each branch sees its own fleet and availability; transfers between branches and one-way rentals are recorded. Head office sees all branches together.

Can a vehicle be rented again while a damage dispute is open?

Vehicle availability and an open dispute account can be scoped as separate processes. Your business will designate who makes technical inspection and maintenance decisions; dispute evidence will retain its link to the previous rental.

What happens to the first handover record when a vehicle is replaced?

The first vehicle's return and the replacement vehicle's handover can be separate records linked to the same contract. We will define the exchange workflow together so mileage, fuel and photographs remain attributable to the right vehicle.

How is the price set?

After a discovery meeting we prepare a written quote covering the scope, the modules and the setup work. The software is provided on a monthly or annual subscription.

Do we receive the source code?

In our standard model the software is provided on a subscription and the source code is not transferred. If you need a different model, it is agreed in a separate written contract.

Who is responsible for what is done with the software?

We build and operate the software. The business using it is responsible for how it is used, the data entered and the content published; the details are set out in the service agreement.

Related products

Let us define vehicle return checks

Share handover and return documents with renter details removed so we can prioritise registration, mileage and deposit checks for the first version.

  • Scope shaped around your workflow
  • Roles and record design
  • Integrations subject to conditions