Express courier. Direct.
Also overnight.
x25pronto Switzerland takes goods direct to the destination. Small loads go by car. Larger loads go by van or Van XL. Direct, express and overnight trips run Monday to Sunday when a slot is free. Free times are shown in the booking calendar. This keeps the plan clear.
Route planning for collection batching: tools and heuristics
Practical guide to TSP heuristics, Excel proofs-of-concept and routing API options for collection batching. For logistics and shipping teams in Switzerland.
Quick answer
Start with a simple heuristic (Nearest Neighbour or Clarke-Wright Savings) to quickly group pickups. For growing operations, move from an Excel distance-matrix PoC to a routing API for scalable, automated optimisation. Test APIs in sandbox mode, benchmark against Excel results, then integrate the chosen solution into your booking or TMS workflow.
Why route planning matters for collection batching
Batching multiple pickup addresses into one tour reduces drive time, fuel and cost. For Swiss SMEs that collect from several clients per day, even simple optimisation yields measurable savings.
Simple heuristic methods (TSP approach)
Two practical heuristics: Nearest Neighbour and Clarke-Wright Savings. Nearest Neighbour starts at a depot and always adds the closest stop. It is fast but not always optimal. Clarke-Wright ranks potential savings when merging routes. Both are easy to implement in scripts or spreadsheets.
Excel setups: distance matrices and Solver
Excel is useful for PoCs and small fleets. Build a distance or time matrix (via Google Maps exports or routing provider CSV). Use formulas for Nearest Neighbour or the Solver for small TSP models. Pros: transparency and quick tweaks. Cons: limited scaling and no real-time data.
API integrations: scalable and automatable
Routing APIs provide distances, travel times and optimized routes. They support batch optimisation, time windows and returns to depot. APIs are best when you run multiple daily tours and handle changing orders. Start with sandbox keys and typical order tags (pickup size, access notes).
Which heuristic to pick by size
For 5–15 stops: Nearest Neighbour or Clarke-Wright usually suffices. For 15–50 stops: combine clustering (e.g., K-Means by postcode or geo) with local heuristics. Above 50 stops: use an API-based optimiser or a TMS with built-in routing.
Implementation steps for Swiss businesses
1) Clean data: standardise addresses and add coordinates. 2) PoC in Excel: create a distance matrix and test a simple heuristic. 3) Benchmark: record drive-time and cost metrics. 4) API test: run sandbox comparisons against Excel. 5) Rollout: integrate the best option into your booking system or TMS and set up monitoring.
Frequently asked questions
Which heuristic is quickest to implement?
Nearest Neighbour. You only need coordinates and a distance matrix. Implementation in Excel or Python takes little time.
When should we switch to a routing API?
When you run multiple daily tours with varying stops, require time windows, or need to scale. APIs add real-time data and stronger optimisation for larger volumes.
How do we geocode Swiss addresses reliably?
Use Swiss-aware geocoding services or established API providers that support CH address formats. Ensure consistent fields: street, number, postcode, city.
Can Excel results be connected to a TMS?
Yes. Export the optimized stop list as CSV and import into your TMS or booking system. For automation, prefer an API integration.