Log it once. Never type it twice.

No. Robur Repairs runs in the browser, so the PC at the counter and the laptop in the office open the same shop, with nothing to install or update on either. When a new version ships, the one you open is already it.

A job can be marked done the moment you take it in, so the quick tyre change at the counter never has to travel across the board, and the finished job prints as a receipt in one click with the labour and the parts on it.

That receipt is a private one, not an invoice — no VAT is broken out on it, deliberately, because a receipt stating VAT it should not state creates a liability under § 14c of the German VAT Act. When the customer needs a real invoice, make the invoice instead. The same job produces either one.

Robur Repairs is built for one person — the one who takes the car in, writes up the job and hands over the invoice. One login, nothing to administer: no accounts to create, no permissions to set. A login per mechanic is not part of it; if your shop needs that, tell us.

No, and that is deliberate. The moment a job becomes an invoice it locks — the complaint, the hours and the parts are fixed, so the invoice and the job behind it can never drift apart. Invoice numbers are gap-free and sequential, which is what the GoBD rules ask of invoice numbering. Before it is invoiced a job can be cancelled outright; afterwards neither editing nor cancelling is possible, and a correction is made with a credit note on the invoice instead.

There is no public price list yet — Robur Repairs is being priced with the first shops running it. The shape is already settled: one amount per month, no setup fee, no minimum term, cancelled at the end of any month.

On Google Cloud servers in Germany, encrypted in transit and at rest. Robur Repairs processes it under GDPR — the details are in our privacy policy.