Taking bookings

The core Velobook pattern: a customer books a day and arrival window to drop in, you work to your own schedule, rush is an optional surcharge.

One list across every booking your shop takes, with search across every date, filters, arrival check-in, CSV export and a printable day sheet.

Cap each day with a simple job count, or switch to filling the day by how long the work takes within your opening hours.

Cap your booking page to a rolling window, or stop it at a set date, so nothing gets locked in for a season you have not priced yet.

Pause new bookings with one switch, hold each booking for your approval before anything fires, and decide when customers can move their own booking.

Set your weekly booking hours as a week table, close specific days or ranges over the top, and let Velobook offer to tell the customers a closure affects.

Run classes with a fixed number of spots, a waitlist, and automatic reminders.

Hire items out by the hour, half day, day, week or month, with combined pricing, extras, and per-item hire lengths.

Run a repair day from a fixed spot on set dates: set up the location once, publish its dates, and work the day off a printed day sheet.

The daily rack screen for hire bikes: which are on the rack, which are out with a customer, which are overdue, and the one action each row needs.

Sell tickets by tier for rides, race days and open days, then scan people in at the door.

Publish guided rides with departure times, a guide, a meeting point and optional hire bikes from your fleet.

Publish 1:1 fitting appointments with a fitter, a duration, an intake questionnaire and a fit report PDF.

The Service areas tab: switch mobile servicing on, mark out the areas you cover, and charge for travel. Plus collect & return.

Sections, per-service questions and small print, "from" prices, skills, rush, and the work you keep off the booking page.

The shop-wide side of hire: how customers can book, how bikes get to them, and what you take as security.