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.
Reporting for customer portals: KPI exports and SLA reports
How to deliver KPI exports and SLA reports in your customer portal: automated exports, file formats, self‑service filters, security and user rights.
Quick answer
KPI exports and SLA reports in a customer portal can be automated, secure and user friendly. Use CSV feeds for data analysis and PDFs for signed documentation. Self‑service filters and role‑based access give your teams control over what, when and how often reports run.
Why structured reporting matters for logistics portals
Customers need clear KPIs and proof of SLA performance. Structured reporting answers questions on transit times, delivery success rates, exceptions and punctuality. For Swiss companies, traceable logs and simple exports help controlling, procurement and compliance.
Automated exports: frequency and triggers
Set frequencies by role: real‑time feeds for operations, daily exports for dispatch teams, and weekly or monthly reports for management. Use scheduled jobs (e.g. daily CSV at 05:00) and webhooks for immediate alerts on SLA breaches.
PDF vs CSV: pick the right format
CSV is best for analysis, pivot tables and system imports. It contains raw numbers and timestamps. PDF is better for signed SLA evidence, neat management reports and archival copies. Offer both and allow mixed exports when needed.
Self‑service filters and saved templates
Let customers set filters: date range, region (e.g. Zürich, Geneva), client ID, service level. Allow saving templates for repeated exports. A simple UI reduces support work and raises adoption.
Security and access control
Use role‑based access control so not every user sees all data. Encrypted transport (TLS) and secure storage prevent leaks. Maintain audit logs that record who generated which export and when.
Integration and API considerations
Provide RESTful APIs with parameterised endpoints for KPI queries. Standardise field names (e.g. shipment_id, delivery_time, status_code). Good documentation and sample requests make integrations with ERP, BI tools or Excel easier.
Frequently asked questions
Which KPIs should exports include?
Key KPIs are transit time (pickup→delivery), on‑time delivery rate, exception rate, delivery attempts, SLA breaches and confirmation timestamps. Choose KPIs based on service levels and internal needs.
How do I set up automated reports?
In the customer portal choose a schedule, format (CSV/PDF), recipients or SFTP target. Or configure webhooks or API queries for real‑time data.
What security measures should I require?
Use TLS for transport, encrypted storage, role‑based access control and audit logs. Use API keys or OAuth tokens with expiry and scoped permissions.
Can I filter reports by region?
Yes. Robust portals allow filtering by region, depot or postal code range so you can run reports for Zürich operations or all shipments in Romandy.