Scarab OS

From drop-off to paid.

Every screen exists because someone in the shop needs it at a particular moment. Here is the order they get used in.

A job, start to finish

  • Front desk takes it in

    Customer, vehicle, VIN and what the customer says is wrong. The work order records who wrote it up.

  • It lands on the board

    Sixteen stages from intake to pickup, including waiting on a customer, waiting on parts and finding something else. Every move records who made it, so the board answers where a car is without anybody opening it.

  • The technician picks it up

    Signed in as themselves, the technician takes the job. Diagnosis, labor lines and parts land against their name, at the labor rate the VIN already chose for that class of vehicle.

  • They inspect it properly

    A courtesy multi-point, a billed diagnosis or a deep diagnostic — different jobs, different sheets. A truck is asked about its air system and DEF; a car never is. A half-finished sheet cannot be passed off as a clean bill of health.

  • An estimate comes off the job

    Labor and parts at your rates, with the inspection findings and photos beside them. The customer answers “Yes, do it” or “Not now” on each line and signs.

  • The job is sealed

    Everything freezes, fingerprinted with SHA-256 and signed, naming the technician and whoever sealed it. Nobody can change it afterwards without it showing — not your staff, not you, not us. If something is wrong, you seal a correction, and the original stays. Repairs involving parts file a warranty token against that record.

    Each seal is also linked to the one before it, so a repair or a payment cannot later be removed from your books without the gap showing. Publish that chain's fingerprint and the date stops being yours to move.

    The sealed record, explained

  • It goes onto the car's record

    Once the job is sealed it goes onto the vehicle's permanent record, a register that outlives any one shop, as long as the four things below are met. It goes on once and stays: a refund afterwards does not take it off. What travels is the work, the parts and your shop's name. What never travels is your pricing, your cost, your vendors or anything about the customer.

    So when that car is sold, or turns up at another garage in four years, what you did is on its record with your name against it. Four things gate it: you accept the publishing terms, we verify your shop is a real business before it can publish at all, your customer has not refused, and the invoice for the repair is paid in full.

  • Invoice and payment

    The invoice is generated from the sealed record rather than from anything still editable. Owner or front desk records the payment.

    Sealing also files the parts warranties, queues the customer's next service, and — if you use QuickBooks — leaves the invoice ready to push across. The repair is published to the vehicle's history when those four things are met, the invoice being paid in full among them.

Meanwhile, the customer

They get your shop code. From any phone browser they enter it with their VIN or the phone number on file and see the current status of their repair.

  • No account to create, no app to install
  • They see status, vehicle and shop — not other customers, and not their own file
  • Lookups are rate limited, so the page cannot be trawled

Meanwhile, the owner

Who is here, what they are doing, and whether the numbers work.

  • A live roster of who is clocked in right now
  • Hours on the floor against labor hours sold, per person, and billed hours divided by clocked hours
  • Which vehicles each technician worked on today
  • Everything written up today and who wrote it
  • Parts that have fallen below their reorder threshold

Your shop is yours

Every record carries the shop it belongs to, and the app looks records up by shop as well as by id, so a record belonging to another shop is not visible, not editable and not reachable, including by its id.

  • Everyone signs in as themselves: Google or a link to their own email, or their own PIN on the shop's device
  • PINs are stored as scrypt hashes, never in plain text
  • Sessions are signed and expire after twelve hours
  • Personal PINs must be unique within your shop, so hours and work cannot be misattributed

Ready?

Setting up takes a few minutes, and your shop starts empty.

Or open the demo shop — a working copy filled with sample data you can run as if it were yours.

How it works — from drop-off to a sealed record · Scarab OS