Parking management software: one chain from the gate to the till
A day in a car park is one chain repeated: a vehicle arrives, its plate is recorded, the clock runs, the fee is worked out from the time spent, the money is collected, and in the evening the till is counted. If any link of that chain lives in a notebook, in someone's memory or in a separate app, the damage does not show up at that link — it shows up at the ends: the till does not balance, a subscriber's unpaid period is forgotten, and the "I already paid" argument cannot be settled.
This page does not start as a product pitch. It first describes where that chain breaks in a real car park, then what a software system genuinely has to solve. Our own app appears at the end; but the questions come first, because software chosen against the wrong question is abandoned six months later.
What does parking management software actually do?
Parking management software — also called a car park management system or a vehicle entry-exit system — brings the daily operation of a car park onto a single chain of records. Its core is this:
- Entry.The plate is recorded, the arrival time is stamped, the vehicle joins the "inside" list.
- Duration.Time runs by itself while the vehicle is in; nobody has to watch a clock.
- Tariff and fee.At exit the fee comes from the defined tariff, not from memory or negotiation.
- Collection.Cash, card or online payment; a subscriber's vehicle passes without being charged.
- Till.Collections and expenses accumulate during the day; one figure comes out in the evening.
- Reporting.End-of-day and period reports: revenue, cash/card, vehicles in and out, who collected what.
All six steps already happen in every car park. What software adds is not extra work but the opposite: never asking for the same information twice. The plate is recorded once, and the duration, the fee, the subscriber check, the till and the reports all feed from that one record.
Where does the day leak?
Ask an operator what the hardest part of the job is and the answer is almost never "parking cars". The hard part is remembering four things at once:
- Who came in when. At a busy hour arrival times do not stay in anyone's head, and the time written on paper is not read at exit.
- The fee. If the duration is disputable, so is the amount. A figure quoted from memory differs from attendant to attendant.
- Subscribers. An expired subscription is not remembered at the moment the car is at the gate. And then it is not remembered at all.
- The money. Was it cash or card; what should be in the drawer tonight. When the count does not match, the error is not found — it is covered up.
All four are record-keeping problems. Nothing leaks because people work less; it leaks because the records do not accumulate in one place.
What must parking software genuinely solve?
The following is not a marketing list. These are the things that stop the day when they fail. Asking them one by one makes evaluating a system much easier.
1. Vehicle entry has to take seconds
Nobody fills in a form while the driver waits at the wheel. The right flow is: record the plate, let the car in, let the rest run in the background. Reading the plate with the phone camera takes that step down to a few seconds — but typing it in must always stay open, because dirty plates, steep angles and foreign plates will happen. In a good system camera entry is not the "real" way and typing the "fallback": both are first-class, and the attendant decides which one to use at that moment.
Recording the plate in one consistent form also keeps a vehicle's history together. A plate entered two different ways looks like two different cars, and "has this vehicle been here before?" goes unanswered.
2. Duration and fee must be calculated automatically
In a car park the fee has a single source: how long the vehicle stayed. Wherever that calculation is done by hand, three things follow — it is slow, it is wrong, and it is argued about. The system should stamp the arrival time, produce the duration and the amount at exit, and leave the attendant only the confirmation.
3. The tariff must be flexible but still readable
Real parking tariffs are not a flat hourly rate. At least four parts are needed:
- Free period (grace): the first fifteen minutes free, for example. Charging for a short stop costs customers.
- Tiers: "up to this many minutes, this total". A tier is a total, not an hourly add-on — this distinction is the most common mistake when a tariff is written.
- Daily cap: the highest amount chargeable in a day. Without a cap, long stays produce amounts nobody intended.
- Beyond the last tier: what happens once the tiers run out. This is the field that quietly leaves money on the table when it is left empty.
Being able to keep several tariffs — weekday/weekend, day/night — and switch which one is active in one tap matters as well. One critical rule: changing the active tariff must not retroactively alter records that are already closed.
4. Subscribers are a separate line of business
Most car parks earn from two streams: casual vehicles and monthly subscribers. The second one needs its own structure in software: a subscriber record tied to the plate, a period (weekly, monthly, yearly), a period fee and a payment history. Letting a subscriber's car pass without being charged is the easy part; the real point is that the system remembers an expired subscription. The right behaviour is not to hold the car at the gate and start an argument, but to flag it in the list as "payment due" and queue the collection.
5. Till, expenses and end of day must collapse into one figure
Only one number has to be certain in the evening: what the cash in hand should be. That requires collections split into cash and card, subscription collections kept on a separate line from parking collections, and expenses entered the same day. Restricting who can enter expenses is a correct constraint, because invented expenses are the easiest way for money to leave.
6. Staff permissions should be narrow by default
An attendant does not need the till, the reports or the tariff screen to do the job. A good system has at least three roles — owner, branch manager, attendant — and the attendant cannot change the fee at will. Manual fee changes should not be banned outright either; what matters is that they leave a trail: who changed what, when, visible in the end-of-day report.
7. Multiple devices and multiple sites belong in the design
A tablet in the booth, a phone in the attendant's pocket, the owner's phone at home — all of them should show the same business, seconds apart. When a second car park opens, the system should need a new branch on the same account, not a new installation: capacity, till, occupancy and reports per branch, plus an all-sites total.
8. The work must not stop when the connection does
This is the item that splits field software in two. Connectivity in a parking booth is not always good — basement levels, metal cabins, mobile data. Entry, exit, fee calculation and the till have to run on the device itself and sync to the cloud once the line returns. Browser-only systems stop when the connection drops, and at that moment the records go back to paper — which is usually why the till does not balance that night.
An honest distinction belongs here too: working offline is a capability, not the product's category. Choosing parking software only because it "works offline" can mean settling for a weak tariff engine or no subscriber management at all.
9. The customer side can be digital too
"Parking software" usually brings only the operator's screen to mind, yet two simple things on the driver's side make a visible difference. First, a QR code tied to the individual parking record: the driver scans it and watches the arrival time and the running charge live in their own browser — with no app to install, no account and no phone number. Second, being able to pay by card: less cash changes hands in the booth, and less cash sits in the drawer on a night shift.
10. Do not leave the booth television blank
If the screen at the entrance shows live free spaces and the tariff, a passing driver does not stop to ask whether there is room; they see it and drive in. Plates and amounts must not appear on that screen — what someone paid is not public information.
11. Setup should finish in one evening
A car park operator has no time to run a project. If the tariff, the sites and the staff can be set up in an evening, the system gets used; if it needs an installation crew, cabling or an on-site server, that is a different decision with a different budget.
An honest section about hardware
Parking automation traditionally means barriers, ANPR cameras, payment kiosks and an on-site server. Those installations have their place: a busy shopping-centre car park, an unattended site, a turnstile entrance. But in most small and mid-sized car parks the day runs with one person in a booth, and what is actually missing is record-keeping.
The concrete difference of a phone-based approach is this: you can start without dedicated plate-recognition hardware. The phone or tablet you already have becomes the operating terminal, and the television in the booth becomes the information screen. That does not mean barriers or ANPR cameras are useless; it means they are not required to start. If you do run a barrier, a turnstile or a fixed ANPR camera, decide in the knowledge that a phone-based app does not drive that equipment.
Six questions to ask when choosing
- What happens when the internet drops?Get the answer by testing, not from the seller: turn the connection off, take a vehicle in, let one out.
- Does my tariff fit?Build your own tariff and check three cases: 10 minutes, 2 hours, a full day. If they do not match, the feature list means nothing.
- Is there a real subscriber structure?Without periods, period fees and payment history, "subscribers" is only a label on a customer list.
- What can the attendant see?Not seeing the till and the reports is the correct default, not a limitation. And does a fee change leave a trail?
- Whose data is it?Is there an export, and can you take your history with you if you leave? Ask on day one, not on the last day.
- What makes the price go up?Per vehicle, per device, or flat? Know how the invoice behaves in a busy season before you start.
The criteria list, and how OtoparkPro answers each one
The same criteria in a form you can hold against any system you are evaluating. Each row says how the requirement is met, not that it is met well; judge the how yourself.
| Criterion | How OtoparkPro meets it |
|---|---|
| Vehicle entry and exit | The whole day sits behind two buttons: VEHICLE IN and VEHICLE OUT. Arrival is time-stamped and the car joins the "inside" list; at exit the duration and the fee arrive already calculated and the record closes on confirmation. |
| Plate records and search | Search the vehicles inside by any part of the plate; case and spaces do not matter. The record detail lists earlier visits of the same plate. |
| Plate recognition with a camera | Read by the phone camera, on the device; the photo is not sent to a server to be read. At vehicle entry the camera and the keyboard are two separate buttons, so whoever is typing does not wait for a camera to open. Detailed page. |
| Duration | The arrival time lives in the record and the duration runs by itself; nobody computes a time difference at exit. |
| Fee calculation | Calculated at exit from the active tariff. Only the owner and a branch manager may change the amount; with the admin PIN enabled a PIN is required, and every change is written to the audit log and the end-of-day report. |
| Flexible tariff | Four parts: free minutes, tiers ("up to this minute, this total"), a daily cap, and a rate beyond the last tier. Several tariffs can exist with one active at a time; switching the active one does not alter closed records. Tariff guide. |
| Subscriber management | Subscribers are tied to the plate, with weekly, monthly or yearly periods. A subscriber's car passes at exit without being charged and is marked SUBSCRIBER on the record. An expired subscriber is not held at the gate — the record moves into the "payment due" section, and collecting it moves the validity one period forward and writes to the payment history. |
| Till and collections | The till screen keeps parking collections, subscription collections, expenses and net cash apart, with the cash/card split shown separately. Entering an expense is limited to managers and the owner. |
| Staff and roles | Three roles: owner (everything), branch manager (daily work, tariffs, reports, till, expenses), attendant (entry/exit and subscriber collection only). Staff join with a single-use six-digit invitation code; on a shared device, selecting "who is using this device" credits collections to that person. |
| Reporting | The end-of-day summary in one text: revenue, cash/card, expenses, net, vehicles in, out and still inside, who collected how much, and any manual fee corrections. Sent over WhatsApp or SMS; the recipient needs no app. Period reports add a date range, a daily revenue chart and averages. |
| Offline operation | Entry, exit, fee and till work on the device and sync to the cloud when the connection returns. Plate reading happens on the device, so it never needs internet. The receipt QR page and the TV board do need a connection, because both read from the cloud. |
| Multiple devices | Every device signed in with the same account sees the same business: a tablet in the booth, a phone in a pocket, the owner's phone at home. Changes sync within seconds; on a conflict the last write wins and the server prevents an older copy from overwriting a newer one. |
| Multi-site management | Capacity, location, till, occupancy and reports per branch, plus an "All branches" total in the till. Staff can be assigned to a branch. Detailed page. |
| Web access | The same account signs in from a browser: entry and exit (plate typed), the vehicles inside, tariffs, subscribers, till, reports, branches and the team. The web version needs a connection, and camera plate reading is not part of it — that is the phone's job. Web guide. |
| Customer updates | Every parking record carries its own QR code; scanning it shows the customer their plate, the arrival time and the running fee live, in their own browser. No app, account or phone number is required. Where supported, the same page offers an Apple Wallet pass or a browser notification. Detailed page. |
| Online payment | At exit the customer is shown a payment link or a QR code; the exit completes by itself the moment the payment lands. The money goes to the operator's own PayTR or Stripe account and never passes through the app. Payment account guide. |
| TV information screen | Live free spaces, occupancy and the tariff on the booth television. Setup happens once: the TV shows a six-digit code, you type it into the phone. Works with a browser TV, Apple TV or Android TV. Plates and amounts never appear on the board. TV setup guide. |
| Driver map | Optionally the car park's name, location and free spaces are listed on the driver map; plates and amounts are never shared, and you can switch the listing off at any time. |
| Hardware needed | A phone or a tablet. You can start with no dedicated plate-recognition hardware, barrier, terminal or on-site server. A television is optional, only for the capacity board. Barriers and turnstiles are not driven by the app. |
| Security and permissions | Device lock (Face ID or fingerprint) and an admin PIN. The attendant does not see till totals, expenses or reports; deleting a record is limited to managers and the owner. |
| Languages and currency | 27 interface languages and more than 60 currencies. Plate format is validated against the country selected for the business; a free format is accepted for countries outside the list. |
| Pricing transparency | No subscription is asked for during the first 24 hours and the first 10 vehicle records; after that a seven-day free trial granted once per store account, then a monthly or annual subscription. The price is shown in your own currency in the store, and cancellation happens in the store. |
One boundary worth stating: the Wallet pass on the customer side is an Apple feature; a customer on Android gets a browser notification instead, or simply opens the page. There is no such split on the business side — OtoparkPro is on the App Store for iPhone and iPad, on Google Play for Android phones and tablets, and also runs in a browser.
How OtoparkPro does this
OtoparkPro is parking management software that brings vehicle entry and exit, tariffs and automatic fee calculation, subscribers, the till, staff, reporting, multiple devices and sites, the TV information screen and the customer's QR tracking together in one app. The plate is read by the phone camera or typed in; the duration runs by itself, the fee comes from the active tariff, the collection lands in the till, and the evening report is shared in one tap. It also works without a connection and syncs across devices once the line returns.
The OtoparkPro product page has a screenshot of every section; the user guide walks through the same work step by step.
First 7 days free. The subscription is bought in the app store and can be cancelled at any time.