Job board & repair orders
LiveKanban stages with domain-enforced transitions — not a free-text status field.
Learn more →Loading
Loading
How it works
Workshop Wrench connects your front counter, workshop floor, and back office in one platform.
Customers book online or the advisor creates the appointment. The board fills automatically with scheduled jobs.
Technician completes a digital vehicle inspection with photos. Findings are sent to the customer for approval in seconds.
Labour and parts are quoted in the estimate. The customer authorises via SMS — work begins without delays.
The RO closes, a compliant invoice is raised, and payment is collected. KPIs update in real time.
Australia · workshop OS
From booking to paid invoice, every step of the vehicle lifecycle in one system — nothing falls through because someone switched apps mid-job. Workshop Wrench is multi-tenant workshop software for independent light-duty AU shops: bookings and check-in, repair orders on a kanban board with enforced stage transitions, DVI findings that become estimate lines, customer portal approvals, inventory that reserves on approval, GST-aware tax invoices, and owner KPIs with formulas you can actually read. Early access — honest roadmap, no fake customer logos.
Primary GTM language for AU/NZ is workshop (not only “shop”). GST invoice paths ship Live; Xero is Dry-run (stage + dryRunPush, staged OAuth) — we do not claim Connected or a live App Store push until sandbox proof exists.
Why this category matters
Category pages should not be synonym stuffing. Here is the operating rationale every serious shop platform must address.
Car count dies on missed calls, weak booking, and messy intake — the OS must own first contact through check-in.
ARO dies when findings never become priced, decided lines — DVI and portal approvals are margin features.
Throughput dies when AWAITING_AUTH and AWAITING_PARTS are invisible — board stages must mean something.
Cash dies when invoices are re-keyed and AR is a Friday spreadsheet — money path starts on the repair order.
Vehicle lifecycle
The Automotive Workshop Operating System (AWOS) maps every customer moment from first contact to retention — so software follows how workshops actually earn margin.
Capabilities
Live means in the multi-tenant product/demo. Integrations use Live / Stub / Dry-run / Planned — never Connected for stubs. Roadmap means not production-complete.
Kanban stages with domain-enforced transitions — not a free-text status field.
Learn more →Build lines, track approval state, recover declined work for follow-up revenue.
Learn more →Token portal for customers to accept or decline estimate lines on mobile.
Learn more →Findings on the RO today feed estimate lines and the portal. Photo media templates are expanding — Live+, not a US-class media suite.
Learn more →Catalogue, low stock, PO/receive path, reservation on approved lines.
Learn more →Tax invoices from ROs, payment records, pay-link path on issue.
Learn more →ARO, car count, efficiency-style metrics with documented formulas. Modular canvas; chart series are live + mock hybrid — never Connected for stubs.
Learn more →Demo-shop booking flow and marketing book surface for independents.
Learn more →Live Swagger at the API. Webhooks and deep accounting adapters staged.
Learn more →ACCREC stage + dry-run push only — staged OAuth shell; not a live App Store push.
Learn more →FAQ
Structured for humans and search (FAQ schema). We update when ship status changes.
Software that runs the vehicle lifecycle in one place: customers and vehicles, bookings, job cards / repair orders, inspections, estimates and approvals, parts, invoicing, and often customer messaging. Better products also expose profit metrics (ARO, efficiency) and audit status changes.
Yes — AU/NZ-first discovery, GST-aware invoicing helpers, and planned Xero-first accounting export. The live demo uses multi-tenant isolation you can try today. Local parts catalog adapters are staged after the core money path.
Yes. Request the live demo at /demo — we issue a signed access desk and email role credentials for the seeded garage.
We compete on modern board/PWA workflow, portal approvals, open TypeScript APIs, transparent published plans, and documented KPI theory. We do not claim feature parity on every AU parts integration on day one — see Compare and Alternatives pages for dated, fair notes.