FEZA innovation – Home
← All products

Developed on request

Car Park & Valet Operations

Car Park Software

Track entry, permit status and exit payment within the same parking visit. We will define tariffs, valet handovers and shift changes for the software we will build using your operating documents. Capacity decisions and permit validity will be scoped separately.

  • Cash records linked to visits
  • Permits and capacity distinguished
  • Valet handover responsibility
Car at a barrier and a key board beside a tablet showing parking spaces
  1. Discovery
  2. Scope and quote
  3. Development

When departing vehicles and shift payments do not reconcile

Keep records from entry to exit so shift-end differences can be traced. Lost tickets, verbal discounts and missing exit times can obscure the day’s accounts. Valet services add questions about key custody and vehicle location. Checking the permit book is another task during busy arrivals.

The software we will build will link visits to registration numbers, times and attendants. Payments, cancellations and manual adjustments could be scoped as separate movements within the visit. You will define the cash and card records used at shift handover. With multiple car parks, the design can identify which location each capacity and cash summary belongs to.

A ticket-based shift

  • Permit records, valet notes and payments are kept separately.
  • Discount reasons may be unavailable at closing.

Actions linked to visits

  • Tariffs, permit decisions and payments could share one parking record.
  • Cancellation and adjustment movements could be separated for cash reviews.

From entry and key handover to exit and shift reconciliation

We will build the sample day around a paid visit and a permit holder’s arrival. Share your entry fields and exit tariffs. If you offer valet parking, explain when key labels and parking locations change. In the project we will build, an ongoing visit, fee calculation and payment will be defined as separate states.

  1. 01

    Check registration and permits

    Entered registrations, arrival times and permit matches could be included. Validity and available spaces will be separate checks at entry.

  2. 02

    Valet and vehicle requests

    Key number, parking location and receiving attendant could be linked. Vehicle requests could include queue order and the attendant retrieving the car.

  3. 03

    Fees and shift closing

    Calculated fees, payment methods and discount reasons could be retained. Handover comparisons with cash and card totals will be planned.

Start with registration records and scope valet and multiple sites separately

Camera connections can be considered separately from daily records. The first release could use attendant-entered registrations for arrivals and departures. Hourly, daily and overnight tariff periods will follow your rules. Permit renewals, contracted vehicles and free periods can be designed separately from tariffs. For multiple gates or sites, we will discuss central management and each shift’s own cash records.

  1. Initial entry and exit scope

    Visits, tariffs and cash
    Registration, arrival time, fee calculation, permit status and shift comparisons could be selected together.
  2. Operational additions

    Valet and central overview
    Key tracking, vehicle requests, multi-site summaries and occupancy reports could be added as needed.
  3. Device-dependent scope

    Cameras, barriers and payments
    If existing devices offer connections, protocols, permissions and error conditions will be reviewed before inclusion in the project.

Different checkpoints for timed parking and permit holders

A valid permit and an available space are separate matters. Timed parking focuses on the entry-to-exit tariff; permit holders require checks of registered vehicles and contract periods. If you accept corporate vehicles, define their permit groups. The software we will build will handle timed visits, permit checks and capacity assessments separately. Scope can then associate each applied rule with the relevant arrival.

Entry information

Timed parking
Registration, arrival time and applicable tariff are defined.
Permit vehicle
Registered vehicle, permit period and validity are checked.

Exit calculation

Timed parking
Parking duration and discount decisions could link to payment.
Permit vehicle
Covered use and additional-fee rules will be discussed.

Full-site decision

Timed parking
Acceptance or waiting could be selected for a new visit.
Permit vehicle
Capacity decisions will be scoped independently of valid permits.

Separate gate access from cash adjustments

The information an entry attendant needs to check a permit differs from management’s payment reports. Gate, valet and cash responsibilities will be selected in the project. Correcting an exit time, applying a discount or reopening a closed shift could require separate permissions. You can specify when explanations are required and which records should be reviewed at handover.

Gate and valet tasks

Registration, parking locations and key handovers could follow task scopes. Access to permit holders’ contact details will be assessed separately.

Cash and management decisions

Discounts, cancellations, payment-method changes and explanations of shift differences could be linked to authorised people.

Registration and device data

KVKK, Turkey's personal data protection law, image retention and access records are considered in scope. Turkish fiscal-device, payment-terminal and document requirements will also be discussed.

Record a separate decision when a permit holder arrives at a full car park

A permit can still be valid when no spaces remain. A positive validity check should not itself decide admission. The project we will build could keep permit matches and capacity results separate. You will define when to wait, notify a supervisor or use another direction established by your business.

The attendant’s decision and reason could be linked to the attempted entry. We will discuss recording the actual entry time if the vehicle later enters. Valet key acceptance will also be treated separately from capacity decisions. If permits include reserved-space conditions, their fields will be scoped around your contracts.

Checks become mixed

  • A valid permit can override occupancy information.
  • Actual entry and key handover times become unclear for waiting vehicles.

Two separate decisions

  • Permit results and capacity status could be shown separately.
  • Waiting explanations and actual entry could be linked through distinct records.

Transfer permits, open visits and shift balances separately

We will review registration formats and permit start and end dates together. You can define how several vehicles relate to one permit holder. Vehicles inside at migration time will not be treated like old closed visits. The open shift’s cash and active tariff version will also be checked separately during migration preparation.

  1. 01

    Organise the permit list

    Duplicate registrations, missing periods and corporate arrangements will be reviewed in a sample. Anonymised records can guide matching fields.

  2. 02

    Check open parking visits

    Vehicles inside, entry times and valet keys could be compared in a trial transfer. Opening cash will be linked separately to its shift.

  3. 03

    Review gate connections

    Camera or barrier access will be assessed if the provider offers it. Records during outages and later matching will be discussed separately.

Explore application and automation approaches for gate operations

Car park scope involves entry decisions, device data and shift closing alongside tariffs. Our automation service offers a starting point for these relationships. The article below explores websites and applications that manage daily records. Use these resources to consider which gate and cash actions need to share a workspace.

Start with a tariff schedule and shift-handover example

Share tariff periods, permit types and a blank closing form. For valet services, explain key labels and vehicle-request order. Camera, barrier and payment-device models can inform connection reviews. We will define the first entry and cash scope using these inputs, then discuss multiple sites and reports as separate quotation items.

  • Explain today’s decision for permit holders arriving at full capacity.
  • Identify roles approving discounts and exit-time corrections.
  • Include open-visit transfers and outage needs in the discussion.

Scope will distinguish manual registration entry from device connections. Subscription use and support terms will be considered in writing after discovery.

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 we need number plate recognition cameras?

No. We design the software to work without cameras: the attendant types the plate, and tariffs and the cash-up work in the same way. If you want ANPR cameras, they can be connected as part of the project scope; which devices are suitable is clarified in the discovery meeting.

Can we keep our existing barriers and turnstiles?

That depends on the connection method the equipment offers. We review your barrier and turnstile models during discovery and tell you clearly, before development starts, whether a connection is possible.

Does recording stop if the internet goes down?

We address outages in the scope from the start. The software can be designed to keep recording entries and exits locally and to sync them when the connection returns; an accurate shift cash-up depends on that.

Can an attendant change the calculated fee?

Only the people you authorise. We set discount and void rights by role; every action is recorded with the name of whoever made it and appears as its own line at shift handover.

Can receipts or invoices be issued?

Payments are recorded in the software. Connections to cash registers (ÖKC) and card terminals are scoped per project and made only with devices that meet the regulations; e-Archive invoice flows can also be connected if needed. Your accountant advises on which document must be issued.

How could entry time be recorded when a permit holder waits for a space?

Waiting and actual admission could be scoped as separate fields. We will determine which time governs charges and permit assessment around your operating rules.

Could valet keys pass to another attendant during a shift?

Key handovers could link previous and new custodians within the same visit. Location changes and ongoing vehicle requests can be defined independently of that handover.

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 discuss entry and shift procedures

Use your tariff, permit and valet examples to select the development scope for your car park.

  • Cash records linked to visits
  • Permits and capacity distinguished
  • Valet handover responsibility