Every repair you take in, from the counter to paid.

A repair in a bike shop is not complicated, but it has a lot of handoffs. Someone calls or walks in. Someone writes the bike up and guesses at a price. The bike goes on a hook, then on a stand, then maybe back on a hook while a derailleur hanger ships. Someone calls the rider, someone else rings them up, and somewhere in there a mechanic's time should have been written down and usually wasn't.

Most shops run those handoffs on a paper tag, a whiteboard, a retail POS that treats service as an afterthought, and a phone that never stops. BIKE.co is built to put every one of those steps in one place: the booking, the quote, the bike's history, the work order, the checklist, the parts, the invoice and the payment. One record per repair, one login for the whole shop.

The software is the erp.io Service module, set up for bike shops. Service owns the work itself. The customer, the phone, the books and the signatures live in other erp.io modules that are already running, and Service connects to them instead of keeping its own copy. That is why the product is described below in five groups, following the order a bike moves through your shop.

Win work covers everything before the bike is on a stand. Today a rider can fill in a repair request form you publish, or the counter can type a request in, and it lands in the Requests inbox to be triaged into a quote. Quotes are live, with line items, optional parts, a discount and tax, and an approved quote turns into a job in one step. Picking a drop-off slot online, sending the quote to the rider for approval, and bike records with serials and history are on the roadmap. The phone is handled by Phony, the erp.io AI receptionist, which answers calls today.

Shop floor is the bench, and most of it is live. Work orders are numbered jobs with one or more visits, each with a named mechanic, and a visit cannot close until its required checklist is submitted. The week schedule lists visits by day with an unscheduled queue for bikes that have no day yet. Mechanics clock time against the visit they are working on, and a manager approves the week. Service checklists give you tune-up, safety and e-bike checks you build yourself, with photos, signatures and a PDF for the rider. New: the field app installs from the browser and keeps working with no signal, queueing checklist answers and finished visits until it can send them. The bench board by status, drag-and-drop scheduling, bench capacity and van routing are on the roadmap.

Parts and inventory is where most bike shop software stops being honest. The Service plan includes real stock locations, including each van, usage recorded against the job, reorder points that write the purchase order, and job costing that sets labor and parts against what you charged. All of it is on the roadmap; parts and purchase orders are a later phase of the build.

Getting paid already runs from the work order: once every visit on a job is closed, one click creates the invoice from the job's lines, with discount, tax, due date and terms. Payments are recorded by hand against the invoice today, including part payments. A Stripe payment link or QR code at pickup, delivering the invoice by email or text, and a 'your bike is ready' text are on the roadmap. Running the shop covers monthly reports on work, money, hours and checklists (live), team permissions by role (live), and, on the roadmap, a customer portal, accounting sync and reports on bench throughput, comebacks and margin.

Nothing inside Service is gated by plan. When a roadmap feature ships, every shop on every plan gets it. The price is per user, and the 30-day trial includes every module without a card.

General field-service software is built around a truck going to a house. A bike shop is the reverse most of the time: the job comes to you, sits in your building, and waits for a stand, a mechanic and sometimes a part. The work order has to know about a bike, not just an address. The checklist has to know the difference between a tune-up and a hydraulic bleed. The customer record has to hold three bikes for one rider and forty for one rental fleet.

Service is not all the way there yet, and it is worth saying plainly. Today a job belongs to a site, which is a name and an address, so a work order does not carry a frame serial or the bike's history. Bike records, a bench board with shop statuses and bench capacity are the roadmap items that close that gap. What is live already covers the core of a repair: the request, the quote, the job and its visits, the safety check, the hours and the invoice.

The field app is a web app you install on the phone, not an App Store app, so there is no Tap to Pay and no background GPS. When you are ready to try it, run one real repair through it: a request, a quote with an optional chain, a job with a required safety check, and the invoice at the end.