Capacity you can count on, without the fleet.

Fleetable wins retained contracts — a dedicated route, a scheduled multi-drop round, capacity held against an SLA — and then buys the capacity to fulfil them from vetted operators. The central team is deliberately small and does four things: sales, dispatch, compliance, and account management.

That shape is the whole argument. A logistics business that owns vans has to keep them moving, which means its incentive is to fill vehicles rather than to serve your rounds. Fleetable buys capacity per route, so a round that shrinks costs you less instead of costing the same.

It also means the answer to “can you take on three more sites in April” is not limited by what is parked in a yard. Capacity flexes with the contract, up and down.

Fleetable moves food and nothing else. That is a choice, and it costs some revenue.

Food carries constraints that general haulage does not. The temperature has to hold from collection to signature. Goods-in will refuse a load whose record is missing, however cold it actually is. And a delivery that lands after service has failed even though it arrived on the right day — which is why the measure that matters here is on-time-in-full rather than same-day.

Solving those properly means not spreading across every category that would take the call. A narrow operation that never misses a service window is worth more to a food business than a broad one that sometimes does.

The operating rule is simple enough to state in one line: no fixed cost is taken on before contracted revenue covers it. No vans, no depot, no accreditation carried speculatively, no headcount ahead of the work.

It is not modesty. It is what lets Fleetable quote a route on what the route actually costs, rather than on the recovery of assets bought for somebody else’s contract — and it is why nothing here is billed for standing capacity.

The same rule shapes what this site claims. Figures that have not been audited are labelled as samples, accreditations appear only once held, and the way to check any of it is to run one route and look at the record it produces.

It applies to the site as much as the service. Every page is built to WCAG 2.2 AA and tested against it on each deploy, so an ops manager using a screen reader or a keyboard can price a route and book a review unaided — the detail, including what is still imperfect, is in the accessibility statement.