Job board & repair orders
LiveKanban stages with domain-enforced transitions — not a free-text status field.
Learn more →Shop management · independents
Workshop Wrench is cloud shop management for independent auto repair: service advisor board, technician-friendly flows, digital inspection path, line-level approvals, parts readiness, invoices, and owner dashboards. Built as a workshop operating system — early access with a working multi-tenant demo.
This page targets the US/global phrase “auto repair shop software.” AU buyers may prefer our workshop management hub. Same product; regional language only.
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.
Shop day sequence
The same operational spine as the product board — detailed use cases live under Processes.
Public booking or front desk intake with customer + vehicle first-class. Why: car count dies when first contact never becomes a system object.
Booking becomes a repair order; board shows stage, tech, and blockers. Why: WIP you cannot see is WIP you cannot manage.
DVI findings with severity convert to estimate lines or deferred work. Why: verbal upsells without structure kill trust and ARO recovery.
Line-level approve / decline / defer via portal tokens. Why: silent scope expansion creates write-offs and disputes.
Reserve stock, raise POs, clock labour on the RO. Why: authorised work without parts is fake progress; unbilled labour is pure waste.
GST invoice from approved lines, payments, AR visibility. Why: revenue is not cash until collected — money path stays on the RO.
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; rich media templates are an active next slice.
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.
Table stakes: CRM + vehicles, scheduling, repair orders, estimates, DVI, inventory, invoicing, customer messaging/approvals, payments or payment partners, and reporting. Leaders also ship portal approve, text-to-pay, and multi-location.
Those platforms set a high bar on UX, SMS, and packaging. We match core workflow pieces in a live demo, publish transparent tiers, open REST APIs, and focus AU tax/accounting path. See our Compare pages — no fake “#1” claims.
14-day trial path on published plans, plus a live demo access desk after you request at /demo.