B2B · Partial
PartialFleet work with PO discipline — not free-form verbal POs
Fleet customers need purchase-order rules and threshold checks before work expands. Workshop Wrench ships fleet account fields and check APIs/UI as a Partial shell — not a branded fleet portal or insurer network.
Primary persona: Advisor / owner
The problem
What breaks without this process
Fleet jobs start without PO; invoices bounce; AR ages while the bay already spent hours.
Why it matters
Rationale — profit, risk, and shop floor truth
- 01
PO-required flags stop free work for account customers.
- 02
Threshold checks protect margin on large authorisations.
- 03
Honest Partial status sets expectations vs full fleet platforms.
Proof from the live demo
Real UI — not a pitch mockup
Captured from the seeded multi-tenant demo. Open the same surface with demo credentials.
Stage sequence
Step-by-step use case
Each stage lists the action, the business why, and the intended outcome. This is how we implement and test the product — not marketing fiction.
- 01
Mark fleet account
Action
Customer isFleet + PO / threshold settings.
Why this stage
Rules only fire when the account is first-class.
Surface: Customers / FleetOutcome: Account configured - 02
Check before expand
Action
Fleet check API/UI against PO and threshold.
Why this stage
Prevent silent scope creep on commercial accounts.
Surface: /fleetOutcome: Allow or block signal - 03
Invoice with discipline
Action
Issue invoice with PO reference habits your bookkeeper needs.
Why this stage
Fleet AR fails without paperwork hygiene.
Surface: InvoicesOutcome: Payable invoice
Related search intent
- fleet workshop software
- PO required auto repair
- B2B garage accounts
Related product pages
FAQ
Questions on this flow
Structured for buyers and search.
Is this a fleet customer portal?+
No. It is account-level PO/threshold support in the shop OS. Do not expect a multi-fleet self-serve portal as Connected today.