How to run a multi-location bike shop

The second shop is where a lot of good bike businesses come unstuck. What worked as one bench and one diary becomes two of everything, and suddenly nobody can answer a simple question: how did the group do this week? The trick is not to merge your shops into one blob, it's to let each run itself while a thin layer on top rolls the numbers up and lets a customer be recognised wherever they walk in.

Keep each shop independent

Resist the urge to standardise everything on day one. Each location has its own opening hours, its own mechanics, its own local pricing and its own float of hire bikes, and those should stay local. A branch manager who can't set their own Saturday hours or add a service without ringing head office will route around your system within a month. The aggregation should sit read-only over the top: see everything, override little.

Roll the numbers up where you can read them

You need one view that answers "how are we doing" across the group without exporting five spreadsheets: today's bookings by shop, how much of each fleet is out, capacity against demand, and revenue with a scorecard per site so a quiet branch stands out early. In Velobook, a shop group becomes a network with exactly this roll-up, combined bookings, a shared fleet view and per-shop revenue, while each shop keeps its own admin underneath.

Let customers belong to the brand, not the branch

A rider who bought the bike at your north store and gets it serviced near work should not be a stranger at the second counter. Cross-shop customer history means their bikes and past visits follow them between your locations, so any mechanic in the group starts from what was done last time. It also lets loyalty travel: referral credit earned at one shop can be spent at a sibling, which only makes sense if the customer record is shared in the first place.

Move stock to where the demand is

• Rebalance hire bikes. A fleet that's overbooked at the beach shop and idle in town is a transfer, not a lost booking. Move rental units between sites, and let the system suggest what to shift.
• Share a catalogue. When one shop gets its service menu and pricing right, copy it to the others rather than rebuilding it by hand, then push a price or policy change out to the sites you choose.
• Send the work, not the customer. A job booked at one shop can be done at a sibling that has the tech or the time, while the original shop keeps the customer relationship.

Make it easy for customers to find the right door

Once you have more than one location, "which one" becomes a real question. A public location finder that takes a customer's postcode and routes them to the nearest shop's booking page turns that question into a booking, and you can embed it on your own website so the whole thing happens on your brand.

Pitfalls to avoid

• Centralising the diary. One shared calendar for every shop reads as chaos by Tuesday. Keep booking and capacity per site; roll up the reporting, not the diary.
• Forcing one price everywhere. Rent and wages differ by suburb. Local pricing per shop is a feature, not a mess to clean up.
• Letting customer records silo. If history doesn't follow the rider between shops, you've built two businesses that happen to share a logo.
• Waiting for perfect before you roll up. Even a rough per-shop scorecard beats finding out at quarter's end that a branch has been quietly sliding.