What shops ask before they sign up. Not here? Email us; a founder reads it.
A dollar a booking, every feature included. Priced locally: 70c in the US, 50p in the UK, 60c in the Eurozone, a dollar in Australia, Canada and New Zealand. Capped at 100 bookings a month in every market (A$100, US$70, £50, €60, C$100, NZ$100), and the rest of the month is free. Billed monthly through Stripe. No tiers, no per-seat charge. The one extra is text messaging, where it's available (Australia, the UK, the US and Canada) and only if you switch it on.
A booking is confirmed when the customer completes the booking flow. A repair, a workshop seat, a hire, a tour spot and a fitting each count as one. Cancel before the appointment and the charge is reversed on your next bill (except for shops billed through Shopify, which can't take a credit). No-shows count, because the slot was held.
Only texts, and only if you turn them on. Texting is prepaid: you load a balance, the rate depends on your market and the message type, and Messaging shows how many texts your balance buys. Customer payments, at the counter or as a deposit at booking, go straight to you.
Past 100 bookings in a month, the rest are free. The one exception is very high volume: a shop consistently taking more than about 2,000 confirmed bookings a month is past what a single-shop plan was built for, so we'd get in touch and agree terms, with at least 90 days' notice before anything changes.
No. Catalogue Copilot, the Bike Builder, the Wheel Builder, Events and the daily printing bridge are included while they're in beta.
Yes. 30 days from signup. Bookings come through and the booker works the same; they aren't billed. No card at signup: adding a payment method is the last step of onboarding, and you need one on file before your booking page publishes. Cancel inside the 30 days and you pay nothing.
Open billing portal from the Billing tab and cancel in Stripe's portal, or email alex@velobook.app. No contract, no retention call.
If our costs rise a lot, the price may too. You get 90 days' notice in writing, and existing shops stay on the rate they signed up at for that notice period.
An afternoon. Enter your services, your hours, your reminder wording and a couple of colours. Then paste your booking link in your Instagram bio, on Google Maps and on your website.
Your shop name, your weekly hours with a couple of drop-off windows per day, three or four services with prices and rough durations, and an email for booking notifications. That's enough to take real bookings.
Both, self-serve. Customers: upload a CSV under Catalogue, then Import, match the columns, check the preview, import. Presets for Lightspeed R-Series and X-Series exports, a dry run first, and an undo. Calendar: connect Google Calendar or Microsoft 365 and Velobook keeps a bookings calendar up to date. Apple Calendar and anything else can subscribe to your shop's read-only iCal feed.
No. If you can write a service description and a price, you can run Velobook. Stuck? Email us; a founder walks you through it.
Yes. Integrations has a Website embed tab with a copy-paste snippet for each thing you offer (services, hire, workshops, tours, fittings, plans, community days), plus one combined snippet. The frame resizes itself as the customer moves through the steps. Only what you sell is offered.
Yes. Until you publish your link, nobody but you can reach the shop. Book a fake bike with your own email, then delete it before you go live.
No cap. Most shops run 3 to 12 (tune-up, flat fix, brake bleed, full overhaul). Each service has a name, a price, a duration, an optional blurb and an optional rush surcharge.
Yes. Each service has a "price is a starting point" toggle. On, the booker shows "from $80" instead of "$80".
Optional extras a customer can add to a service: new brake pads, a parts bag, a quick clean. Each has its own price and optional extra minutes.
A loading the customer opts into for a same-day turnaround, offered only on today's date. Default 25% on the service and add-ons; set your own rate under Integrations, then Payments & POS, down to zero. Never automatic.
Yes. Set a flat e-bike surcharge under Integrations, then Payments & POS. It's added whenever the customer says their bike is an e-bike, and choosing rush lifts it with the rest of the job. The amount is frozen on each booking, so changing your rate later never re-prices past work. Leave it at zero to charge e-bikes the same.
Yes. Hidden services stay off the booker but keep their name on old bookings.
Not yet. One price per service, shop-wide. Most shops add a separate service ("Senior tech tune-up") with its own price.
Yes. Fittings are their own booking type, with tiers, an intake questionnaire the customer fills in at booking, and a fitter on the slot. Upload the fit report afterwards and the rider gets it as a PDF.
Yes. Bundle a set of credits a customer buys up front (a season of services, say) and they redeem them against bookings.
Booking hours, under Admin. Your week is one table: each row is a window with a name ("Morning") and a start and end time (09:00 to 12:00), and the columns are Monday to Sunday. Fill in a cell with how many jobs that window takes on that day; leave it empty for a day it doesn't run. One tap copies Monday across the working week.
How many jobs you'll take in that window. A Morning window with capacity 4 lets 4 customers pick it before the booker marks it Full. The number lives in the cell, so the same window can take 4 on Tuesday and 2 on Saturday.
Your choice. By default a window holds a set number of jobs, whether a puncture or an all-day rebuild. On Booking hours you can switch to "Fit within opening hours", which adds up each service's duration against the hours you're open, so a day of long jobs fills sooner. In that mode a mechanic's day off lowers the day's capacity on its own.
Yes. A date override changes the windows for one date (a public holiday, a special Sunday). A closure period marks a range of dates closed (a holiday week, a renovation).
Yes. Add a Day off or a Closure period. Existing bookings on those dates stay; the booker stops taking new ones.
No limit by default. Under Shop profile, set a Booking horizon: a rolling window from 2 weeks to 12 months ahead, or a fixed last bookable date for winding down a season or moving premises. It's read in your shop's timezone and holds on the calendar and again when the booking is placed. Clinic sessions, tour and workshop dates aren't affected.
Set under Shop profile. Default is Australia/Sydney. It drives reminder timing and the past-date gate on the booker.
Yes. A workshop has a title, a list of dates and times, a seat cap per session and a price per attendee. One customer can sign up several people. A full session takes a waitlist.
Yes. Tours have scheduled departures, a rider cap per departure and a hire-bike option: none, as an add-on, or included. A hire bike on a tour holds real rental stock, so a bike can't be promised twice. Waitlists are built in.
Yes. Each item has a name, a quantity, an optional deposit, and rates for the hire modes you offer: full days, AM or PM half-days, or by the hour. The booker enforces availability per bike, per day, including same-day out-and-back hires if you allow them. Add per-bike extras (helmets, locks, a child seat), set a turnaround buffer so a returned bike stays offline while it's checked, and take online payment up front if you want. Each bike can carry a QR sticker your team scans to hand it out or take it back.
Your call. A hire/rent toggle under Booking page re-words the customer rental flow, emails and texts. Default is "hire".
Yes. Turn on delivery in Rental settings, set your fee (free, flat per area, or by distance) and your delivery and collection windows. Customers choose pickup or delivery at checkout. Velobook can plan the driver's day across deliveries, collections and mobile repairs as one route.
Optional, off by default. Turn on ID capture and staff sight a licence or passport when the bike goes out. Velobook stores only the last four characters, and purges them on a schedule.
They're off by default. The booker only shows a category with at least one published item in it. A pure repair shop never sees them.
Yes. Mark a service as mobile and draw where you'll travel: radius rings, areas sketched on a map, or a list of postcodes. Each area has its own working days and travel fee (free, flat, or by distance). Customers see a coverage map and their address is checked before they can book.
Yes. Set a location and dates (a café, a co-op, a weekly market) where customers bring bikes to you. They pick the clinic and a window at booking, like a normal drop-off.
Team tab. Name, email, a colour chip for the Schedule, and optional skill tags. They get an email invite and set their own password.
Yes. Pick a staff member on the booking, or let Velobook auto-assign by skill tags, working days and a daily booking cap.
Yes. On each service, pick who's qualified for it. Auto-assign respects the list. Leave it blank for anyone.
No. Add as many as you like.
Yes. Each staff member can link their own Google or Microsoft calendar so their jobs show on their phone. Off by default.
Yes. The staff app has the schedule, job cards, messages and fleet, with a push notification when a booking lands. iPhone: search Velobook on the App Store. Android and desktop: install it from the browser, push included. A native Android app is in a closed trial on Google Play; ask us to add you. Customers never need any of it.
Yes. Each staff member adds their own days off from My roster; managers and admins can set time off for anyone from the Team tab. Velobook won't auto-assign someone jobs on a day they're off, and in time-based capacity a day off lowers that day's bookings.
Yes. Templates for Basic service and Full service, plus M-Check and e-Bike M-Check safety checks. Apply one to a booking in one click and tick items off. Edit them, or build your own, under Safety and checklists.
Yes. Every bike carries its past bookings and work, for the mechanic and for the customer.
They're flagged on the Workboard and in Schedule's Today view, with how long each has been waiting.
Yes. Inventory is a table of your parts, accessories, apparel and bikes, showing how much stock is booked against open jobs and what's still free. Filter by supplier, product type, your own tags or what's on order, and download as CSV. Connect a POS and your counts copy in read-only; Velobook never writes back. No POS? Keep the counts in Velobook, split by location if you run a van.
Yes. Add your suppliers (contact, order email, lead time, minimums), then the Ordering board batches the parts your approved quotes need, by supplier. Draft a purchase order and send it from Velobook or from your own email app. Note your own PO number against it, and Velobook tells the mechanic on the job when the parts arrive.
Yes. Use the device camera or a USB or Bluetooth scanner to put a part on a quote, count it in against a purchase order, or find it in Inventory. UPC, EAN, Code 128 and Code 39 all read. An unknown code is bound to a product once.
Yes. When you add a part to a job, tick Chargeable and it goes on the quote at your catalogue price. Leave it off for warranty, goodwill or shop-stock parts.
Yes. From a bike's history, send a service reminder now or on a chosen day, using your own template plus a note. A customer who has unsubscribed shows as not sent.
Yes. Each booking gets a code like JOB-0007, unique to your shop, and purchase orders get a matching PO-0007. It's on the booking, in search and on the customer's confirmation, so either side can find the job fast. The letters in front are yours to change.
Mark the booking as a no-show. Velobook keeps a count on the customer's profile. No-shows are billed like any confirmed booking, because the slot was held. A deposit at booking is the best deterrent.
Yes. Set what each mechanic can do and prefers, and the skills each service needs. Auto-assign picks a mechanic who prefers or can do the work, inside their working days and daily cap. Assign by hand and you get a warning if they're over the limit or short a skill, never a block.
Check them in from the admin in a few taps and they land on the Workboard with the rest. There's also a kiosk mode for a tablet at the counter, so customers check themselves in.
Two by default: a week before and 24 hours before. The confirmation goes at booking, a "your bike is ready" email when you mark the job ready, and cancellation and reschedule emails the moment the customer hits the button.
Yes. Every email and text has an editable subject and body, under Messaging, then Templates.
Not yet. Emails go out from a Velobook sender under your shop's name. Replies to repair bookings land in your Velobook Inbox; replies to everything else go to the reply-to address you set.
Yes, in Australia, the UK, the US and Canada, with other markets following as each sender approval clears. Turn on texts under Messaging, then Settings, then Channels, and customers with a mobile get an SMS alongside the email for confirmations, reminders, cancellations and reschedules. It's two-way: texts go from a real Velobook number, replies land in your Inbox, and you can text back or send a quote link. Photos go to Australian, US and Canadian numbers; UK is text only. Prepaid: load a balance under Funds, the rate depends on your market and message type, and sending pauses when the balance runs out. Email works everywhere regardless.
Click your link, pick a service, pick a window, type their details, confirm. About 40 seconds. No account, no app, no password.
Never. Velobook is a web link and works in any phone browser, including a 10-year-old Android. The Velobook app is for your staff only.
Yes. Every confirmation carries a manage link to change the date or window, or cancel. The shop is told every time.
Yes. The manage link shows the job moving from booked in, to on the bench, to waiting on parts or approval, to ready for pickup. Reschedule and cancel drop away once the job is under way.
If they opt into a Velobook account at booking, their next visit prefills the form and they can see their service history at every Velobook shop in one place.
Yes. Each service shows its price (or "from $X"), add-ons show their own price, and the total is on the Confirm step.
No. In-shop payments stay on your POS. Deposits at booking go through your own Stripe or Square account and settle to you. Velobook never touches the money and adds no percentage.
Yes. Optional, off by default. Turn them on in your payment settings and the booking confirms once the deposit goes through. Refund from your payment provider's dashboard.
Only if you leave it that way. Switch on inline checkout under Integrations, then Payments & POS, and the card fields sit in your booking flow, drawn by Stripe or Square. Off by default, with hosted checkout as the fallback. Shops billed through Shopify keep the redirect.
Optional. Some shops charge a daily storage fee if a bike isn't collected within a week. Set the amount and the booker shows the policy at booking with a tick to acknowledge it.
Yes. Percentage or fixed-amount codes, entered in any booking flow: services, workshops, fittings, tours or hire. A code can come off the booking, a hire's delivery fee, or both. Travel surcharges are never discounted.
Yes. Build a quote, send it by email or text with an approve-and-pay link, and once accepted it becomes a booking.
Every confirmed booking is counted and charged monthly through Stripe, up to your cap. The Billing tab shows this period's usage and the next bill. Shops that installed through Shopify are billed by Shopify, in their local currency.
Live today: Google Calendar and Microsoft 365 / Outlook (plus a read-only iCal feed), Shopify, Stripe and Square for online payments, GoHighLevel for CRM, and Lightspeed (R-Series and X-Series) and Ascend RMS at the counter. Your POS also feeds the Inventory page. Add your own Google Analytics, Meta Pixel or Google Tag Manager, and switch on Google or Yelp review requests. Xero, QuickBooks and Mailchimp are on the roadmap, shipped in the order shops ask.
Connect once under Integrations, then Calendars. Velobook creates a calendar just for your bookings: new ones appear straight away, cancellations disappear. It's one-way. Velobook writes to that calendar and never reads your other events. Microsoft's permission screen asks for more than Google's, because Microsoft has no narrower option; Velobook still only writes to the one it creates. Staff can link their own Google or Microsoft calendar too.
Yes. Switch on draft orders and every booking becomes a Shopify draft order you charge at the till. Your services and add-ons mirror as Shopify products, and Shopify stock shows when you quote.
In the Bookings tab. You can also subscribe to your shop's iCal feed from any calendar app.
Built, waiting on Strava's approval. A rider links their account so their mileage can trigger a service or chain-wax reminder. Not switchable on yet.
Yes. Set your primary, accent and background colours under Booking page, and your logo sits in the header.
Yes. Under Booking page, pick a heading font and a body font from the list. Public Sans is the default body. Booking page only; the admin never changes. There's a lower-case option for brands that never use capitals.
Yes. Your link starts as velobook.app/your-slug. Add a custom domain (book.yourshop.com) under Shop profile, point a CNAME at us, and the secure padlock is handled for you.
Yes. The terminology editor swaps a handful of nouns (item, service, class) for your trade's words. Set "item" to "watch" and the booker follows.
Yes. Pick Australian, British or American under Booking page. American turns colour into color and tyre into tire, and defaults the hire wording to "rent". It carries through emails, texts and the customer pages.
Yes. Hero copy, under Booking page: title, subtitle and the button on the first screen.
Yes. Bookings, the analytics ledger, quotes, customers, inventory, suppliers and purchase orders all download as CSV from the admin, on day one and the day you leave.
In a Supabase database in Sydney, Australia, encrypted at rest. We don't sell, share, or train models on your customer data.
Export what you need as CSV before you go. Your data stays available for 30 days after cancellation, then we delete it in line with the Privacy Policy.
Yes. From the customer's profile, archive them (hidden, reversible) or erase their personal data. Erasing anonymises name, contact details and messages and removes their bikes, while past bookings stay as anonymous rows for your financials. Erasing can't be undone.
As long as you choose. Photos on a customer's job are deleted once they reach the age you set, counted from when the job finished. Default two years; anything from 3 months to 10 years. Fleet and catalogue pictures are never touched, and erasing a customer removes their photos straight away.
Yes. Analytics covers revenue, volume, customers, utilisation, health and conversion across every booking type, up to 12 months with a comparison to the previous period. Export the bookings to CSV from there, and quotes or invoices from Quotes & invoices.
Optional, off by default. After booking, the customer can save the booking to a Velobook account. It works at every shop on Velobook, so they see their service history in one place.
No. Each customer belongs to your shop. The customer can choose to share their history with other shops they book at. Off by default.
Yes. Shops under one brand form a network, which gives the parent a read-only roll-up: combined bookings, a shared fleet view, revenue and a scorecard per shop, plus customer history that follows a rider between locations. Each shop keeps its own catalogue, staff and billing. Networks are set up with us, so get in touch.
Share customer and bike history, spend referral credit earned at one shop at another, move rental bikes between shops, copy a catalogue or push prices and policies to chosen shops, and send a job to another location. Each shop keeps its own day to day.
Yes. A network gets a public location finder: the customer enters a postcode and lands on the right shop's booking page. Link to it or embed it on your site.
Yes. Any shop where the customer leaves the thing with you: watch repair, motorbike workshops, luthiers, cobblers, tailors, framers, jewellers, camera repair. Terminology, window lengths and reminder wording are all yours to set.
We started in a Sydney bike shop and the name stuck. Booking a repair works the same whether the thing on the bench is a road bike or a 1962 Omega.
Email alex@velobook.app. We reply within one working day, usually within a few hours during Sydney business hours.
Velobook uses essential browser storage to keep you signed in, remember which shop you are working in, and route custom domains. With your permission, we also use Google Analytics to understand how people use Velobook. Advertising trackers are always off. Choose what is okay with you.
Read our privacy policy.