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.
Checklist: What your tracking portal must do for time‑critical deliveries
A practical checklist for Swiss businesses: features, KPIs, roles and integration points a tracking portal must support for time‑critical shipments across Zurich, Geneva and Basel.
Quick answer
Your tracking portal must provide real‑time status, event notifications and clear ERP/CRM integration. These core capabilities reduce uncertainty and let teams act proactively on time‑critical shipments.
1. Core features that must work immediately
Real‑time tracking: current vehicle position and estimated time of arrival (ETA). Event log: departure, stops, delivery attempts and final delivery with timestamps. Live notifications: push, SMS and email on status changes or delays. Proof of Delivery (PoD): photo, recipient name and digital signature for handover proof.
2. KPIs to measure timeliness and response
On‑Time Delivery Rate: share of deliveries on time. Average Delay Minutes: average delay in minutes. First Attempt Success Rate: share delivered on first attempt. Mean Time to Exception Resolution: time from exception detection to resolution. Display these in dashboards and use alerts for thresholds.
3. Roles, permissions and user interfaces
Clear roles avoid data chaos: dispatchers see all shipments and can act. Customers see only their shipments and receive status updates. Drivers use a mobile app with scan, photo and signature features. Admins manage users, SLAs and integrations. Role‑based views reduce errors and protect customer data.
4. Integration points with ERP, WMS and CRM
ERP: hand over order and billing data, auto‑post shipping events. CRM: feed customer communication and escalation rules with status updates. WMS: send shipment records from the warehouse, picking status and dispatch time. Use RESTful APIs, webhooks for push events and CSV/EDIFACT export depending on legacy systems.
5. Event design and notification rules
Define clear event types (e.g., 'Dispatched', 'Delay >15 min', 'Delivery Failed'). Rules decide who receives which message and when. For time‑critical loads, configure automatic escalations: when an SLA threshold is crossed, notify dispatcher and account manager.
6. Data quality, security and compliance
Accurate location needs clean vehicle telemetry. Log all changes and keep an audit trail. Encrypt data in transit and use role‑based access controls. Ensure compliance with Swiss data protection practices and agreed data retention policies.
Frequently asked questions
Which integration method is fastest to implement?
Webhooks for status updates are often the fastest. They push real‑time events to your system without heavy API polling. Use REST APIs for details on demand.
Which KPIs should I watch daily?
On‑Time Delivery Rate, Average Delay Minutes and First Attempt Success Rate give a daily view of performance and highlight urgent issues.
How do I set useful escalation rules?
Use thresholds like 'Delay >15 minutes' or 'ETA change >30 minutes'. Configure tiered notifications: driver→dispatcher→account manager.
Do I need separate interfaces for drivers and customers?
Yes. Drivers need a compact mobile app for scans and PoD. Customers need a simple portal for status and response options. Dispatchers need an operations dashboard with intervention tools.