Revenue control and revenue management are not the same department

PARCS stands for parking access and revenue control system. The two halves of that name are two different jobs, and most operators buy the first while believing they bought the second.

Revenue control is making sure the money you took reaches the bank. It is a chain of custody problem, solved with names, timestamps and records nobody can quietly edit. Revenue management is deciding what to charge, to whom, and through which channel, for a date that has not happened yet. That is a forecasting problem, and no barrier has ever solved one.

The question that separates the two

One question tells you which of them you actually have. Can you say, this afternoon, without asking anybody, who took the 40 euros a customer paid at 06:10 on 14 July, and which bank deposit that 40 euros ended up in?

If the answer comes back in five minutes, you have revenue control. If it involves phoning the person who was on that shift, you have a cash drawer and goodwill. Notice what the question does not ask. It never asks whether 40 euros was the right price. That is the other job, and a business can be excellent at one while completely blind to the other.

Revenue control is a chain of custody with six links

Control is not about totals. It is about the path each amount took, with a name against every hop.

1. Collection. The amount, the method, the moment it was taken (at check-in, at check-out, or on its own) and the operator who took it, by name.
2. Correction. A mistake is voided with a reason and superseded by a new line. Never edited, because an edit destroys the evidence you will want in November.
3. Blind count. The operator counts the drawer without being shown what the system expects, and the variance is computed and frozen at that moment. A count taken against a figure already on the screen is not a count. It is copying.
4. Handover. Named operator to named supervisor, with an amount and a time.
5. Deposit. Date, amount, the reference on the slip.
6. Recap. Per car park, per period, exportable, so somebody outside operations can read it without being trained.

Every one of those is a place money can leave. Five of the six are people-shaped, which is why equipment on its own never closes the gap.

What ParkAgenda does here, and what it is not

ParkAgenda carries an append-only ledger for money taken at the counter. One line is one amount, one method, one moment, one named operator. A void carries a reason and supersedes the original line rather than overwriting it. Around the ledger sit the parts operators actually use at 6am: outstanding balance per booking, deferred collection, a list of departures that left without paying, blind counts with a snapshotted variance, handovers between operators, bank deposits, the opening float, cash on hand, and a per parking recap with a CSV export.

Two limits, stated now rather than discovered in week one.

• Card is a declaration, not a capture. ParkAgenda does not process payments and has no payment provider integration. When an operator marks a line as card, that records that the customer paid on the car park's own terminal. You reconcile card lines against the terminal's own settlement, never against ParkAgenda.
• It is not accounting software and does not replace one. There is no invoice, no fiscal receipt and no VAT document for your customers anywhere in the product. The ledger exports to CSV, and that export is what your accountant receives.

Revenue management asks a different question, at a different time

Revenue management is about a date in the future, and its inputs are pace, mix and cancellation rather than takings. Nothing at the barrier can see any of them.

Four numbers carry most of it. How many bookings are on the books for a future arrival day, against the same lead day last year. Revenue and commission by channel. Cancellation rate by source, because a channel that books well and cancels at 14 per cent is not the channel you think it is. And what you actually achieved per space per day over a period, against a matched previous period.

ParkAgenda reports all four, and here is the honest boundary. There is no rate engine, no tariff grid, no seasonal price list and no yield engine in the product. Pricing Trends is a lookback: average booking price, average daily rate and revenue per available space day over a window you choose, compared with a length-matched previous window. It is not a forecast and it will never propose a price. You set the price. The system tells you what happened the last time you set it.

A worked example: 400 spaces, 60 per cent through resellers

These figures are constructed to show the relative size of the two jobs. Put your own in.

• 400 spaces, 300 occupied on average across the year, average stay 8 days. Roughly 13,700 stays.
• Average booking value 70 euros, so about 960,000 euros gross a year.
• 60 per cent through resellers at 22 per cent commission: 576,000 euros of reseller revenue and 126,700 euros of commission.
• At the desk, 6 per cent of stays pay something (an overstay, an extra, a balance left open), average 28 euros. About 820 payments, 23,000 euros a year, roughly half of it in cash.

Revenue control governs that 23,000 euros. One per cent shrinkage on the cash half is around 115 euros a year. Real, worth closing, and closed by named lines and blind counts rather than by equipment.

Revenue management governs the 126,700 euro commission line. Move two points of the book from reseller to direct and you keep the commission on 19,200 euros of revenue, which is 4,224 euros. That is thirty-six times the shrinkage figure, and it comes from a decision nobody makes on a Tuesday.

The caveat, because it is real: direct is not free. Advertising and your own booking page cost something, call it 10 per cent of a direct booking in this example, so the true gain is well under 4,224 euros. It is still a different order of magnitude from the drawer. The full channel arithmetic sits in parking revenue management starts with channel mix.

That is the whole argument in two paragraphs. The equipment you were sold protects the smaller number, and it protects it well.

Why the confusion costs money

Because nobody ends up owning the second job. Operations owns the cash and usually does it properly. The barrier supplier owns the equipment and the reporting that comes with it. Pricing stays where somebody put it three seasons ago, and the mix drifts towards whichever reseller sends the most volume, which is also the one taking the most commission.

Watch the upsell as well. When your barrier supplier offers you their booking software, the question is not what the screens do. It is where your data lives afterwards and what you can take with you, which we went through in your barrier supplier now sells software.

Who owns which, and how often

• Revenue control belongs to operations, weekly. A blind count at every shift end, a recap read on Monday morning, a variance nobody has to chase.
• Revenue management belongs to whoever signs. Monthly out of season, weekly in it, with pace against last year and commission by channel on the same screen.

Different people, different rhythm, different evidence. Trying to run both off one dashboard is how one of them stops happening.

Six questions for any vendor selling you either one

• Can I export every payment line with the operator's name, the method and the moment it was taken?
• Does a correction overwrite the original line, or supersede it and leave both?
• Is the cash count blind, or does the screen show the expected total before the operator counts?
• Does reporting split revenue and commission by channel, or only give me a total?
• Is the occupancy figure cars on site or reservations? They are different numbers, and only one of them should ever stop a check-in.
• If I leave, what do I get, in what format, and how far back? Settle that before signature, not after.

FAQ

Is ParkAgenda a PARCS?

No. No barriers, no readers, no pay stations, no hardware of any kind. ParkAgenda runs the booking and operations side and carries the cash ledger on top of it. It sits alongside a PARCS rather than replacing one, and it connects to the access equipment you already run through a connector our team builds with your supplier.

Does ParkAgenda take my customers' payments?

No. There is no payment processing in the product and no payment provider integration. Stripe appears only to bill your own ParkAgenda subscription. Your customers' money reaches you exactly as it does today, and the ledger is the record of it.

Does ParkAgenda set my prices?

No. There is no rate engine and no price list in the product. Prices arrive on the booking from the reseller or are typed by an operator. The one figure the system computes is the overstay surcharge, from a grace period and an hourly rate you configure, and an operator confirms, edits or waives it before anybody is charged.

One thing to do next

Pick a day from last month and try to answer the 06:10 question at the top of this page. If it takes longer than five minutes, the fix is a naming convention and a blind count, not a purchase. Then, on a different afternoon, open commission by channel for last summer and see which of your two jobs has been going unattended. What each of those levers is worth on a real car park is the next piece, and what ParkAgenda records on the operations side is on the features page.