Payment records on invoices
LiveCash/card/partial pay update AR on the money path.
Learn more →Collection · Partial
Text-to-pay path built on invoices and portal tokens — not slideware
US leaders treat text-to-pay as table stakes. Workshop Wrench ships payment records and absolute pay URLs on invoices, plus portal pay API/UI path. Hosted Stripe Checkout is stub without keys and live when configured — never badged Connected as a default.
Why this category matters
Profit levers behind the keyword
Category pages should not be synonym stuffing. Here is the operating rationale every serious shop platform must address.
- 01
Car count dies on missed calls, weak booking, and messy intake — the OS must own first contact through check-in.
- 02
ARO dies when findings never become priced, decided lines — DVI and portal approvals are margin features.
- 03
Throughput dies when AWAITING_AUTH and AWAITING_PARTS are invisible — board stages must mean something.
- 04
Cash dies when invoices are re-keyed and AR is a Friday spreadsheet — money path starts on the repair order.
Vehicle lifecycle
Complete vehicle service lifecycle
The Automotive Workshop Operating System (AWOS) maps every customer moment from first contact to retention — so software follows how workshops actually earn margin.
- 01Lead
- 02Customer
- 03Vehicle
- 04Booking
- 05Check-in
- 06Inspect
- 07Estimate
- 08Approve
- 09Parts
- 10Labour
- 11Produce
- 12Invoice
- 13Pay
- 14Release
- 15Retain
Shop day sequence
Six moments that protect cash
The same operational spine as the product board — detailed use cases live under Processes.
- 01
Book or walk in
Public booking or front desk intake with customer + vehicle first-class. Why: car count dies when first contact never becomes a system object.
- 02
Check in & board
Booking becomes a repair order; board shows stage, tech, and blockers. Why: WIP you cannot see is WIP you cannot manage.
- 03
Inspect with evidence
DVI findings with severity convert to estimate lines or deferred work. Why: verbal upsells without structure kill trust and ARO recovery.
- 04
Authorise work
Line-level approve / decline / defer via portal tokens. Why: silent scope expansion creates write-offs and disputes.
- 05
Parts & labour
Reserve stock, raise POs, clock labour on the RO. Why: authorised work without parts is fake progress; unbilled labour is pure waste.
- 06
Invoice & collect
GST invoice from approved lines, payments, AR visibility. Why: revenue is not cash until collected — money path stays on the RO.
Capabilities
What ships — with honest status
Live means in the multi-tenant product/demo. Integrations use Live / Stub / Dry-run / Planned — never Connected for stubs. Roadmap means not production-complete.
Invoice payUrl
Live+Absolute pay links for deep linking from comms.
Portal Pay CTA
Live+Customer portal can initiate pay flow when available.
Learn more →Stripe Checkout (shop invoices)
StubStub without keys; live sessions when STRIPE secrets configured.
Learn more →US-style SMS text-to-pay packaging
PartialExpanding toward the bar set by Shopmonkey/Tekmetric — labeled honestly.
FAQ
Questions buyers actually ask
Structured for humans and search (FAQ schema). We update when ship status changes.
Is text-to-pay fully live like Shopmonkey?+
Not as mature integrated packaging. Core pieces (records, pay URLs, portal pay path, optional Stripe Checkout) ship with status labels. Verify in demo.