A customer portal for quotes, history and invoices

Most bike shop customers do not need an account. They drop a bike off, get a text, pay and pick it up. But some customers do: the commuter who brings the same bike in four times a year, the parent with three kids' bikes, the rental fleet, the corporate bike program, the racer who wants to see exactly what was done to the fork last season.

For those customers, a portal answers questions without a phone call. What did I approve? When was the last bleed? Which chain is on it? What do I owe? It also gives them one place to approve a quote with options and pay a deposit, instead of a chain of texts.

erp.io does not build a separate portal for Service. The Service plan puts customer self-service in erp.io Portal, the suite's customer portal module, and Service supplies the views: quotes, visits and history, invoices and booking.

The most useful thing a portal can show a rider is the history of their bike. In the plan, each bike is a record with its serial number, size and owner, and every work order on it is attached. Because checklists are already live and every submission renders as a PDF with photos and signatures, the portal can show not just "tune-up, April" but the inspection that went with it.

That history also helps you. When a customer asks whether their fork service is due, or whether the shop replaced the chain last time, the answer is on the record instead of in somebody's memory. When a bike is sold, the new owner can see what was done.

For fleets and rental operators, the same view becomes a fleet list: every bike, when it was last serviced, and what is due next.

Portal is brand-scoped: the customer sees your shop, your logo and your colors, not ours. The Scale plan also includes white-label.

You choose which features to show. Some shops will want customers to pay invoices in the portal; others will only want quote approvals and history. Feature visibility settings in Portal are partly built today and are part of the plan for the Service views.

Quote approvals can also be signed through erp.io Sign, which is live, for jobs where you want a signature on record, such as a warranty claim, a custom build or an expensive e-bike motor replacement.

If you start a trial now, you can turn on Portal and see how customers sign in and what a branded portal looks like. You will not see quotes, jobs or invoices from Service in it yet: those exist in Service, but the portal views for them are not built, and bike records are still on the roadmap.

The order matters here. The portal views depend on quotes, work orders and invoicing existing first. Those are now live in Service, so the portal views are the next layer, together with sending quotes and invoices to the rider. The roadmap page shows where each piece is.

We would rather you knew that before you tell your fleet customer they will have a portal login next month.