Line items
LiveLabour and parts lines with approval state.
Authorisation
Workshop Wrench builds estimates as structured lines on the RO. Customers decide per line via portal. Deferred work stays recoverable. Variations re-enter estimate rather than silent scope expansion.
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.
Labour and parts lines with approval state.
Approve / decline / defer without shop login.
Learn more →Findings become priced recommendations.
Learn more →Declined work becomes follow-up opportunity.
FAQ
Structured for humans and search (FAQ schema). We update when ship status changes.
Line-level. Partial approval is normal; all-or-nothing UX forces bad compromises.