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.
Integrating courier bookings into your ERP
Practical guide for Swiss companies to connect courier bookings to ERP systems. Focus: API, order flow, automated notifications and tracking.
Quick answer
Integrate courier bookings into your ERP by using an API for order submission, webhooks for status updates and built‑in tracking fields. Create consistent order data (pickup/delivery addresses, time window, parcel details), trigger API calls when shipments are released, and handle webhook events to update the order status and notify customers. Account for local Swiss constraints like business hours and regional pickup windows in Zurich, Basel or Geneva.
Why integrate courier bookings
A direct integration reduces manual entry, cuts errors and speeds up shipping. Your team saves time on address entry, label printing and phone calls. Customers get reliable delivery updates faster.
Data model: required fields
Core fields: pickup address, delivery address, contact name, phone, desired time window, parcel weight and dimensions, and reference numbers (order or invoice). Optional fields: return info, insurance code, fragile flag. A clear data model prevents mapping errors between ERP and courier.
Technical pieces: API, webhooks, auth
Submit bookings via a REST API with JSON. Use webhooks for status changes such as 'picked up', 'in transit', 'delivered'. Protect calls with API keys or OAuth2. Make endpoints idempotent or use reference IDs to avoid duplicate bookings.
Order flow: from release to delivery
1) Shipment release in ERP triggers API request. 2) Courier returns booking ID. 3) Webhooks push status updates to ERP. 4) On 'delivered', ERP updates order, notifies customer and closes the shipping task. Add retry logic for failed API calls.
Automated notifications and customer updates
Forward webhook events to your notification engine. Send automated emails or SMS for pickup, ETA and delivery. Include order number, ETA and recipient name to reduce support tickets.
Tracking and reporting inside ERP
Store tracking URLs and a status history in the order record. Build dashboards for pending pickups, delayed deliveries and cost analysis. For Swiss sites, filter reports by location, postal code or pickup window.
Frequently asked questions
Which status events should webhooks cover?
At minimum: booking confirmation, pickup, in transit, delivered, failed attempt and cancellation. Additional events like driver photo or POD are helpful if available.
How do I avoid duplicate bookings?
Use idempotent booking IDs or an ERP reference number. Check existing booking status before creating a new one and implement server‑side guards.
How can I test the integration safely?
Use the courier's sandbox or test API. Simulate webhook events and exercise all status paths. Also test error conditions such as missing fields and timeouts.
Are there data protection considerations in Switzerland?
Minimise transferred personal data and keep only what you need. Follow your company’s Swiss data retention and privacy rules.