Parts warranty tied to the RO
LiveSupplier, part number, expiry date, and claim status recorded on the repair order — not a separate spreadsheet. When a customer returns with a failed part, the history is one click away.
Loading
Loading
How it works
Workshop Wrench ties warranty to the repair order at the moment of install, so there's never a gap between what was promised and what's documented.
Technician adds the part to the job. Warranty details — supplier, part number, expiry — are captured on that repair order line.
When the advisor invoices the job, your labour warranty policy pre-fills from settings. They can override per-job if needed.
Upcoming expirations appear on the advisor dashboard so the claim window is caught before it closes — not after.
The RO history shows warranty status immediately. Advisor sees what is covered, what the supplier owes, and whether a claim is already open — before the conversation starts.
Warranty · Claims · RO history
A customer returns with a failed part three months after the job. Who supplied it? What was the labour warranty? Is the claim window still open? With Workshop Wrench, the answers are on the repair order — not in someone's head. Every part installed gets a warranty record tied to the RO: supplier, expiry date, claim status. Labour warranty policy is captured at invoice time. When the customer returns, the advisor sees the full warranty picture before the conversation starts.
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.
Supplier, part number, expiry date, and claim status recorded on the repair order — not a separate spreadsheet. When a customer returns with a failed part, the history is one click away.
Your labour warranty policy is recorded on the RO at invoice time. Advisors see at a glance whether a returned job is still under your stated warranty — before the conversation starts.
Dashboard surfaces upcoming warranty expirations so advisors catch the claim window before it closes — not after the customer has already paid for a second repair.
Open → Submitted → Supplier credit received. Warranty claims have a real status — not a sticky note on a monitor that disappears when someone shifts desks.
Customers see warranty information on their job history in the portal — proactive transparency that builds trust without a phone call.
FAQ
Structured for humans and search (FAQ schema). We update when ship status changes.
Supplier name, part number, install date, expiry date, and claim status — all tied to the specific repair order line. You can filter the warranty dashboard by status and expiry window.
Labour warranty policy is recorded per RO. You set your standard terms in settings and they pre-fill on each invoice — advisors can override per-job when your policy allows exceptions.
Yes — claims have a lifecycle: Open, Submitted to Supplier, Credit Received. You can track the value of outstanding supplier credits across all open claims in the dashboard.