Oversize permits, multi-stage projects, scale tickets, equipment combinations that don't fit a dropdown. Generic platforms handle specialized freight with custom fields and add-on modules, which is another way of saying somebody keeps a spreadsheet.
A permit is a document with a validity window and a consequence when it lapses. It should behave like a maintenance hold or a contract expiry — gating the work at the source — not like a scanned PDF in a folder that somebody checks when they remember.
Some jobs aren't one load with one invoice. They're a sequence of movements billed as a project, with progress billing along the way. When the system only understands per-load invoicing, that reconciliation happens in Excel.
A tractor, a jeep, a stretch trailer and a booster is one configuration. Software that models equipment as a single trailer field can't tell you what's actually under a load, or what needs servicing next.
When the invoice depends on a weight, a count or a measurement captured in the field, that number needs to reach billing attached to the load — not read off a photo somebody texted in.
Vektra's equipment and document models are built to hold structure rather than flatten it, and the "status with consequences" pattern that powers maintenance holds applies just as well to a permit that expired.
Specialized is also the freight type where we're most likely to meet a requirement we haven't built yet, because the variation between operations is enormous. The commitment is that you'll hear that on the demo call rather than discovering it in month three.
POST /loads/8812/assign 400 Bad Request { "error": "PERMIT_EXPIRED", "permit": "OS-2026-4471", "expiredOn": "2026-08-01", // same gate as a maintenance hold "override": "explicit + audited" }
The one with three permits, four movements and a billing structure nobody else could model. We'll tell you honestly whether Vektra handles it.