Repair quotes with line items, options and a clean yes.

A rider drops off a bike for a tune-up. On the stand you find a chain at 0.75, a cassette that will skip with a new chain, a sticky rear pivot and brake pads down to the backing plate. That is a very different bill from the one they expected, and how you write it up decides whether you do the work or send the bike home with a note on the tag.

The worst version of this is a price scribbled on the tag and read out over the phone. Nobody can find it later, the mechanic is not sure what was agreed, and the counter rings up something different at pickup. A written quote fixes that, because every line, every price and the rider's answer sit on one numbered record that the job and the invoice are built from.

That is what Service does today. The quote is not a PDF you make on the side. It is the first link in a chain that runs from the request, to the quote, to the job, to the invoice, with the same lines carried forward at each step so nothing is retyped.

Each quote gets its own number and is attached to a site in Service, which today means a name and an address for the customer. You add line items with a description, a quantity, a unit price and a taxable flag. Labor for a standard tune-up, a chain, a cassette, a set of pads and half an hour for a rear bleed each go on as a line, and the total builds as you type.

Any line can be marked optional. That is how you handle the parts you found on the stand: the tune-up is the core of the quote, and the new chain and cassette sit underneath as optional lines. When the rider tells you what they want, you record which optional lines they took, and only those carry into the job.

The quote takes a discount as a percentage or a fixed dollar amount, and a tax rate. The arithmetic is done in whole cents, tax is worked out after the discount, and rounding goes half up, so the total on the quote is the total on the invoice. When you mark the quote Sent, Service freezes a copy, so a price edit next week cannot quietly change what the rider was quoted.

Be clear with your counter staff about one thing. Marking a quote Sent in Service does not send anything. No email or text goes out, there is no link the rider can open, and there is no quote PDF. The status exists so the shop knows which quotes are waiting on an answer. For now the price reaches the rider the way it does today: a call, a conversation at the counter, or an email you write yourself.

The same goes for approval. The rider cannot tick options and approve on their phone. Someone at the shop records the yes or the no, along with the optional lines the rider chose. The customer-facing quote view, approval from a link and a signed approval through erp.io Sign are on the roadmap, alongside the customer portal.

Tiers are also not built. You cannot lay out a basic, standard and overhaul side by side as three packages for the rider to pick from. The practical way to quote tiers today is one core line for the service the rider asked for, with the step-up work on optional lines. And because the price book has no screen yet, your common services and parts are typed in each time. A price book with saved items is part of the plan.

The quote on its own is a nicer tag. What makes it worth using is what happens after the yes. The accepted lines become the job's lines. The job's visits get a date and a mechanic on the week schedule. A required safety checklist has to be submitted before the visit can close. And once every visit is closed, the job bills in one click from the same lines. At no point does anyone type the chain price in again.

That chain is also what keeps arguments at pickup short. If the rider says they never agreed to the cassette, the quote shows which optional lines were accepted and the frozen copy shows what the price was when it was marked Sent.