Planning snapshot from in-repo sources. Re-check MyTrucking, vWork, and RouteWise packaging on their sites before you rely on it in a pitch.
Transport TMS, broad dispatch, and last-mile scale each optimise for a different centre of gravity. Yardstick anchors on ledger-recognised job threads for own-fleet NZ operators.
“Job to invoice is the transport workflow”
“Proof and dispatch close the loop on the finance record”
“Schedule and optimise the mobile workforce”
Legend: ✓ strong / native · ~ partial or add-on · ✗ not a
docs/logistics/offering.md in the repo. the Yardstick repo.
| Feature | Yardstick | MyTrucking | vWork | RouteWise |
|---|---|---|---|---|
| Operations | ||||
| Visual board (truck / day) | ✓ | ✓ | ✓ | ✓ |
| Structured proof of load | ✓ | ~ | ~ | ~ |
| POD photo / signature | ✓ | ✓ | ✓ | ✓ |
| No-login tracking link | ✓ | ~ | ~ | ✓ |
| MYOB-linked job creation | ✓ | ~ | ~ | ~ |
| Xero / MYOB handoff | ~ | ✓ | ✓ | ~ |
| EROAD telematics ingest | ~ MVP gate | ✓ | ✓ | ~ |
| Multi-stop route optimisation | ~ | ~ | ✓ | ✓ |
| Offline-first field capture | ~ | ~ | ~ | ~ |
Yardstick wins own-fleet + accounting-anchored proof, not solver-first optimisation or subcontractor marketplaces on day one. RouteWise-class capabilities appear where retail last-mile scale matters; we stay focused on finance-ready closure.
Strong where route automation and customer portals are the product story. We differentiate on tokenised tracking and MYOB/Xero-aligned job threads rather than claiming parity on every retail optimisation lever.
Competitor packaging changes. Confirm live features and pricing on vendor sites before customer-facing claims.
Sign in when you want a configured tenant and integrations.