Optimise your routes before the van leaves the warehouse.

Rowan Rutas starts from a common base and gets personalised for each client. The application, the optimisation algorithm and the cost model (€/km, time windows, capacity per vehicle) are already built. What we adapt is the connection to your data sources (ERP, spreadsheet, your own API), the specific business rules (exclusive zones, per-client priorities, loading restrictions) and the look of the dashboard so it fits how your team works in the office and on the road.

No. Rowan Rutas works as a standalone application: you load the stops from an Excel file, a Google Sheets file, or by connecting an API, and the application calculates the optimal route per vehicle. If you already have an ERP, we build a connector so stops travel automatically from your system and signed delivery notes go back to the ERP without manual intervention.

Last-mile distributors with 5+ vehicles, local courier companies, technical field services (maintenance, installations, assistance), food or building-material distribution, and any operation with more than 30 stops a day per vehicle. From that volume upward, optimising routes instead of planning them by eye usually saves between 12% and 25% of kilometres and driving hours.

It depends on the vehicle, the fuel and the maintenance model. As an operational reference we use within Rowan Rutas: a Sprinter-type van comes to around €0.18/km all-in (fuel, tyres, insurance, maintenance, depreciation), and a small vehicle like a Kangoo or Berlingo is around €0.11/km. The application lets you define the real cost per vehicle of your fleet so the route calculation optimises for money, not just kilometres.

The base product deploys in 2-4 weeks if we work with stops loaded from a spreadsheet. Integration with an existing ERP is scoped separately and usually adds 3 to 6 weeks depending on the complexity of the system and the API available. There's an initial 2-3 week period with real data to fine-tune the cost model and the restrictions before moving to production use.

Real roads. Each route is calculated against a mapping engine with up-to-date data, and the polyline the driver sees on their phone follows roads, not straight lines on a map. The time estimate takes historical traffic in the area into account — it isn't made up. It's a point where we break from many TMS prototypes that stop at a pretty drawing without validating the real driving time.