AutoRide

Three service types, and the configuration each one demands

The most consequential setting in AutoRide is not a colour or a layout. It is which service types you switch on. The vendor's booking engine supports Distance (point-to-point), Hourly and Flat Rate, and you can run all three or only the ones your operation sells.

Each one carries its own pricing logic. Distance handles unlimited waypoints with custom stopover durations, takes locations from Google autocomplete or a predefined list, and prices on distance, time and passenger count. Hourly bills a set number of hours against duration and passenger count. Flat Rate runs a predefined route picked from a list with pickup and drop-off fields.

For a chauffeur or transfer business, this is the first decision because it sets how much rate data you have to maintain. Distance suits airport transfers and ad-hoc passenger work; Hourly suits wedding hire and event transport sold in blocks; Flat Rate suits tour operators running the same itinerary repeatedly. Switching on all three means three full sets of rates, and every one of them has to agree with the others or your quotes will look arbitrary to customers comparing options.

The fare is assembled from components, and you choose which apply

The vendor lists a long price structure, and its length is the useful part: a fare is built from parts you enable rather than typed into one field. Fixed prices exist for a ride, for a return ride, and for a return treated as a new ride. Initial fees follow the same three variants. Delivery fees are charged per kilometre from your base to the pickup, with a separate return delivery rate per kilometre from the drop-off back to base. Per-kilometre and per-hour rates each appear in all three ride variants, plus a per-hour rate for extra time. Waypoints, adults and children can each carry their own charge.

Payment surcharges sit at the end of the chain: PayPal and Stripe each accept an optional flat fee or percentage fee that is added once the customer selects that method. Because the vendor describes these as additions to the order amount, they read as charges on the booking rather than a hidden padding of the base rate — which matters if corporate clients ask how a total was reached.

Treat the list as a menu to prune. A flat-rate airport operator can leave kilometre pricing empty. A distance-based operator may never touch the per-adult and per-child fields. What you cannot do is skip the decision, because contradictory components switched on at once produce quotes you would not quote yourself.

Geofence areas matter only when they feed a pricing rule

Geofence areas and pricing rules are described separately, but they are worth reading together. The geofence module lets you draw polygons on a map — airports, cities, custom regions — with a tool for adding, removing, moving and reshaping points. Drawn on its own, that is decoration. The vendor says these areas can serve as criteria inside pricing rules, producing either a distance-based rate or a fixed total for transport between two defined areas.

The rule engine accepts factors including booking form, vehicle type, service type, route, day of the week, date range, time and ride distance. The vendor's own example is a higher fare for weekend trips over 50 km, and it states there is no cap on the number of rules.

That pairing is what makes an airport-to-city fixed price possible on top of a per-kilometre baseline, which is the shape most transfer operators are asked for. It is also where mistakes concentrate: overlapping rules with no obvious precedence will return fares nobody intended. Sketch the rule set before you enter it.

Fleet data and add-ons feed the same booking form

Vehicles are records, not gallery entries. The vendor's field list covers name, description, type, location, make and model, passenger and baggage capacity, standard, owner, base location and rates, plus image galleries, taxes, fees and excluded dates. Unlimited attributes — text, single-choice or multi-choice — can be defined and assigned per vehicle, so colour, engine type or whatever you track becomes filterable data rather than prose in a description.

Extras are where the theme gets unusually specific. An add-on such as a child seat, an alcohol package or a bodyguard service can be limited to particular services, vehicles and transfer types, made repeatable up to a maximum quantity, marked mandatory or optional, and given its own tax rate. If a bodyguard only makes sense on hourly executive hires, that restriction is a setting rather than a note to staff.

Four simplified booking widgets (one vertical, three horizontal) drop the map, navigation and driving details. They fit sidebars, sliders and homepage slots, and they are not a substitute for the full step-by-step form when the ride is complicated.

Availability rules do more than open and close the diary

Business hours per weekday, blocked dates and booking limits by day, date or time range are the baseline. The vendor then describes a separate availability rules module that adjusts vehicle availability, booking extras and payment methods based on the selected form, service type, location, date and time.

That is wider than an opening-hours schedule. It means the same bookable fleet can present different vehicles, different add-ons and even different payment methods depending on which form the customer is using and where and when the ride happens. Useful if you run one fleet across two service areas with different hours, or if some payment options should not appear for far-future bookings.

The operational side sits alongside it: a monthly calendar listing reservations with booking times and assigned vehicles, filterable by status and opening a detail view per booking. Drivers can be assigned manually or automatically with notifications on new reservations and status changes, a driving zone restricts bookings to defined areas, and bookings can sync to Google Calendar.

Payments, currency and coupons in one engine

The booking system accepts cash, Stripe, PayPal, wire transfer and card on pickup on its own. If WooCommerce is installed, the vendor says the full range of WooCommerce payment methods becomes available to bookings, making the shop plugin an optional extension of the payment layer rather than a requirement for selling rides. The marketplace lists WooCommerce 5.x through 10.x as compatible — a vendor statement, not a tested result on your install.

Multi-currency works through an exchange-rate importer that converts a base currency into others, so one form can quote in several currencies. Coupons are fixed or percentage based, with usage limits and activation dates, and can be generated in bulk from a built-in tool.

For chauffeur work, cash and card-on-pickup options matter more than they first appear. Many operators take a deposit online and settle the balance in the vehicle, and the fare components above leave room to charge only part of the total through the gateway.

WPBakery, theme options and the declared compatibility ranges

Page content is composed in WPBakery Page Builder, which the vendor includes, with 40+ AutoRide elements. Some are fleet-specific rather than generic — Vehicle List, Drivers List and Features Carousel are named. Theme options under Appearance handle header and footer layouts, logo, blog and page settings, social profiles, custom CSS or JS, a colour panel and a font panel with access to over 800 Google Fonts. Slider Revolution is bundled for sliders, and layered PSD and PNG files are listed alongside PHP, HTML and CSS.

The marketplace marks Gutenberg Optimized as "No", which describes the vendor's intended editing path rather than a claim that the block editor cannot be used.

Declared compatibility covers WordPress 5.0 through 7.1, WooCommerce 5.x through 10.x, WPBakery and WPML, with browsers from IE10 to Chrome and Edge. Those were vendor and marketplace statements recorded on 4 November 2026, not tests of your hosting or plugin stack, and a version range never guarantees that a specific combination behaves. The booking flow is the part to exercise on staging first, since it touches payments, mapping and notification APIs at once.

Questions & answers