One stop ticketing solution for bus and coach operators

Bus Fare Validation Software: 7 Key Checks Before You Buy

offline-bus-ticket-validation-scanner

Written by

in

Bus fare validation software is the part of your ticketing setup that decides, at the door, whether a passenger has paid the right fare for this ride. It reads the ticket, checks it against your records and tells the driver or agent to let the passenger on or to stop and ask.

This guide is for bus company owners and operations managers who are choosing or replacing the tool at the door. It sets out seven checks to run before you buy. We quote no figures or results, because every operation is different.

Where we mention United Bus Tech (UBT), we rely only on what its site states. Anything else is a question to put to a vendor before you rely on it.

What Bus Fare Validation Software Actually Does

At its simplest, bus fare validation software answers one question: is this ticket good for this boarding? To answer it, the software has to know the ticket, the departure and the rules that connect them.

It also does a second job that owners often forget. Every check leaves a record, and that record is what your finance team later uses to match sales to boardings.

UBT lists ticket validation alongside point of sale, inventory control and real-time reporting as part of its core capabilities. That pairing is deliberate, because validation only works well when it shares data with the other three.

Our guide to bus ticket validation options for operators compares the ways a ticket can be checked. This article focuses on the software side of the decision.

bus-fare-validation-software-scan-at-the-door

Check One for Bus Fare Validation Software: Which Tickets It Can Read

Start with the media your bus fare validation software must read. Can the software read a printed code, a code on a phone, a booking reference typed by hand? List every form of ticket your passengers actually carry today, including the awkward ones.

A tool that reads only one format will push your staff back to manual checks on a busy day. Ask to see each format scanned live, not described on a slide.

UBT states that it offers flexible ticketing validation options to meet your needs. When you evaluate any bus fare validation software, ask which options are included and which ones need extra hardware.

Check Two of Bus Fare Validation Software: Fare, Not Just Ticket

A ticket can be genuine and still wrong for the ride. It may be for another date, another route or another stop. Good bus fare validation software compares the ticket to the specific departure.

Fares can differ by passenger type, by stop pair or by date. Ask how the software handles each case and what the driver sees when the fare does not match.

The driver needs a clear, short message, not a code to decode. A red screen that nobody understands at the door slows the whole queue.

Test an upgrade case too. A passenger who boards at a different stop than the one on the ticket is common. See what your staff would be able to do in the software.

Check Three of Bus Fare Validation Software: When the Signal Drops

Buses travel through tunnels, valleys and rural stops. Validation that needs a live connection for every scan will fail exactly where you cannot afford it.

Ask what the software does when it cannot reach the back office. Can it check against a recent copy of the manifest, and does it sync later? Ask for the behaviour in writing, not in a sales call.

Ask also how conflicts are resolved afterwards. If the same ticket is scanned twice while offline, who finds out, and when?

A short pilot on your most remote route will answer this faster than any specification sheet.

Check Four: Duplicate and Reused Tickets

A ticket that can be used twice is a leak in your revenue. Bus fare validation software should mark a ticket as used the moment it is scanned, and all devices should learn about it quickly.

Ask how fast that update travels between devices, and what the device shows if it sees a ticket that was already used. The answer should be plain enough for a driver to act on.

Also ask about screenshots and shared codes. A passenger might send a screenshot to a friend. Your software needs a rule for the second scan.

This is also where sales channels matter. UBT states that its shared APIs sync instantaneously across all sales channels, including third party websites. A ticket sold on a partner site should validate the same way as one sold at your counter.

bus-fare-validation-software-offline-check

Check Five for Bus Fare Validation Software: Speed at the Door

Boarding is a race against the clock. Every extra second per passenger adds up across a full coach. Watch a real scan from start to finish, including the time it takes for the result to appear.

Test with a full queue, not a single passenger. Try bright sun and a dim terminal as well, because cameras and screens behave differently outdoors.

Ask what the device does when the battery is low. A dead scanner at 6 a.m. is a bigger problem than a slow one.

Also ask how staff correct a mistaken scan. A wrong tap should be easy to reverse, with a note saved for later review.

Check Six of Bus Fare Validation Software: Reconciliation and Reports

Every scan is data. Good bus fare validation software passes that data to your reports, so you can match tickets sold to passengers boarded without a spreadsheet.

UBT lists real-time reporting as part of its core offer. Ask which validation figures appear in those reports, and how soon after a scan they show up.

Think about your end of day with bus fare validation software in place. If your counter closes and you can see sold, validated and no-show tickets in one place, the reconciliation takes minutes. Our guide to bus ticket reconciliation explains the routine.

If the software keeps scans in a separate silo, someone has to copy numbers across. That is where errors and arguments begin.

Check Seven: Who Can Override, and How Is It Logged

Staff will sometimes let someone on without a clean scan. A child with a lost code, a passenger whose phone died, a driver who knows the regular. The question is whether the override is recorded.

Ask who can approve an override in the bus fare validation software, and what is saved. A reason, a time and a name make a pattern visible. An unlogged override is invisible revenue loss.

Be wary of any tool where overrides are easy but unrecorded. The kindness of one driver becomes a hole in your numbers across a season.

Our article on common bus ticket scanning problems lists the situations that most often lead to overrides, so you can plan the rules in advance.

How to Compare Bus Fare Validation Software Fairly

Build a scorecard with the seven checks above. Score each vendor on the same scale, and write down the evidence, not the impression. A table with seven rows will keep the discussion honest.

Run the same five scenarios with every vendor: a clean scan, a wrong date, a used ticket, an offline scan and an override. Watch the driver’s side of the screen, not the manager’s.

Avoid long lists of features. The question is whether the tool handles your worst morning. A shorter list that works on that morning beats a long one that fails.

Do not compare on price alone. A cheaper tool that adds ten seconds to every boarding costs you in delays across the whole timetable.

Start With a Trial, Not a Contract

UBT states on its site that its service is free and with no obligations, and that if you do not like it there will be no cost and no obligations. Confirm the current terms with the vendor before you plan around them.

Whatever the terms, insist on a trial on a real route with real staff. Pick a route with a mix of channels and at least one awkward stop.

Agree beforehand what success looks like. For example, whether staff can validate a full coach without help, and whether the evening report matches the manifest.

Keep your old process for the first weeks, so a failed trial does no damage to passengers.

Choosing bus fare validation software is a small decision with large effects on your revenue and your queues. Run the seven checks, keep the evidence and let the results guide the choice.

If you would like to see how UBT handles validation on your own routes, request a conversation with United Bus Tech and bring your five most awkward boarding cases to test.