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.
CSV workflow: from address list to optimized tour
Step-by-step: Clean your Excel/CSV addresses, validate fields, and import into a TMS or API to generate optimized courier tours and reduce drive time.
Quick answer
Short answer: Clean and standardize your Excel/CSV file, verify addresses and package details, then import into your TMS or via API to produce an optimized route. This reduces failed deliveries and saves driving time in Switzerland.
Why a standardized CSV workflow matters
Unstructured address lists lead to failed deliveries, phone calls and extra kilometers. A clear workflow reduces mistakes, speeds processing and makes route planning reliable. For Swiss businesses, precise addresses and time windows cut costs and time.
Step 1 – Collect raw data and define columns
Export your address list from CRM or ERP as CSV. Create a template with fixed columns: recipient, street, house_number, postal_code, city, canton, email, phone, width, height, weight, time_window_start, time_window_end, reference. Avoid combined fields such as a single 'address' column without separation.
Step 2 – Clean data in Excel or Google Sheets
Normalize canton and city names to match your systems. Remove duplicates and empty rows. Validate postal codes and fix typos. Use built-in functions: Text to Columns, VLOOKUP/SVERWEIS for references, TRIM and CLEAN to remove invisible characters.
Step 3 – Verify addresses and package info
Validate critical addresses with geocoding tools or the Google Maps API if your TMS needs coordinates. Flag hard-to-reach locations, restricted parking or special delivery notes in a 'comments' field. Record package dimensions and weight to choose the right vehicle.
Step 4 – CSV format and encoding
Save as UTF-8 without BOM to keep special characters. Use comma or semicolon as delimiter according to the target system. Check decimal separators for weights. Test with a small sample file of 5–10 rows before a full import.
Step 5 – Import into TMS or via API
Most TMS platforms offer CSV import or an API endpoint. For CSV imports, select the template and map columns (e.g., 'house_number' to house number). For API uploads, convert rows to the required JSON and send in batches. Review the import log for errors and fix failing rows.
Frequently asked questions
What columns are minimally required for route optimization?
At minimum: recipient, street, house number, postal code, city, phone, time window, weight and dimensions, and a reference ID. Coordinates are optional but helpful.
How do I fix common import errors?
Check file encoding (UTF-8), correct delimiter, missing required fields and unexpected special characters. Import logs usually show failing rows. Correct and re-upload.
Do I need geo-coordinates for route planning?
Not strictly. Many TMS systems geocode addresses automatically. Coordinates speed up planning and avoid confusion with similar place names.
How should I test the CSV workflow safely?
Start with a small test import. Verify delivery addresses, time windows and the generated route. Adjust the template and save the column mapping for future uploads.