Every rider, every bike, every repair.

Most shop software treats the customer as the thing you service. In a bike shop the thing you service is the bike, and one rider can own four of them: a road bike, a gravel bike, a kid's bike and an e-cargo bike that does the school run. A rental operator can own sixty. When someone rings and says 'the blue one', you need to know which blue one.

The Service plan splits this cleanly. The person, their phone numbers, email, communication preferences, tags and lead source live in the erp.io CRM, which is live today. Service stores a link to that person and never keeps a second copy. The bike is a Service record of its own, attached to the rider.

That split matters when a bike changes hands. The frame serial, the build and the history stay with the bike. The new owner gets linked to it, and the old owner keeps their own record of what they paid for.

The plan gives Service an equipment record with a type, serial, install date and full service history. For a bike shop that equipment is the bike. Make, model, year and frame serial are the basics. On top of that sit fields you define with erp.io's shared custom fields: frame size, wheel size, drivetrain, brake type, fork and shock model, tire setup, and for e-bikes the motor system, battery serial and display.

Custom fields in the plan come with real types (text, number, true or false, dropdown, link, date) and default values, and they can be transferable, meaning a value set on the bike follows it onto the quote, the work order and the invoice as a snapshot. When a mechanic opens a work order they see 'Shimano XT 12-speed, 180 mm rotors, tubeless' without asking.

Service history is every job, every checklist, every note and every photo on that bike, in order. The plan includes a media library that gathers photos from notes and checklists in one place, which is the fastest way to show a rider how their chain looked last spring.

The frame serial is the one fact about a bike that does not change. It is what a manufacturer asks for on a warranty claim, what an insurer asks for after a theft, and what tells you that the carbon frame on your stand is the same one you inspected after a crash last year.

Keeping it on the record from the first visit makes the rest easy. A warranty claim starts with the serial, the purchase date and the service history already in one place. A recall notice becomes a search. A rider who asks 'when did I last have the fork serviced?' gets an answer from the counter instead of a shrug.

The same record is what will drive service reminders later: a suspension service at a set interval or an annual safety check for a fleet, sent through the CRM's automations. That part depends on the rest of the roadmap and is not available today.

Most shops have years of customer data in a POS or a spreadsheet. Customers import into the erp.io CRM, which supports CSV import today. The Service plan includes an importer for work history, built first for moving shops off Jobber, and the same approach will apply to bike records once they exist.

Until then, the practical first step is to get your customers into the CRM and start running real repairs through Service: a site for the rider, a quote, a job with a required inspection checklist, and an invoice. Put the frame serial in the checklist as a short answer. The submissions are kept, with their photos and signatures, and they are ready to hang off the bike when the bike record arrives.