Skip to content

Repairshop

Repairshop covers vehicle-service workflows — an auto shop, equipment repair center, or similar appointment-and-repair-order business.

Each vehicle is its own record (make/model/VIN and similar), with a full history of every repair order raised against it — so a returning customer’s vehicle history is one click away, not something the front desk has to ask about.

A repair order tracks one job through a fixed lifecycle:

Estimate → Approved → In Progress → Completed → Cancelled

  • Send for approval — an estimate can be routed to the customer for sign-off before work starts (see the public approval flow below), or through Orbit’s internal Approvals for an internal sign-off.
  • Line items cover parts and labor; a completed repair order links to the Sales Order it billed through, so repair revenue flows into the same Sales/ Accounting pipeline as everything else.

Reusable job templates — a predefined set of line items (the parts and labor a common job always needs, like an oil change or brake job) that can be applied to a repair order in one action instead of re-entering the same lines every time.

Scheduling for incoming vehicles, separate from the repair order itself — an appointment can exist before a repair order is created for it.

A structured checklist run against a vehicle (safety/condition checks), attached to the repair order it was performed for.

Repairshop has its own public, unauthenticated page where a customer reviews and approves (or declines) a repair estimate sent to them — the customer doesn’t need an Orbit account to sign off on their own repair.

Repairshop-specific reporting on jobs, revenue, and turnaround time.

See also: Sales for how a completed repair order bills out, and Approvals for internal (not customer-facing) sign-off.