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.
ERP integration for express spare-part orders
How to trigger express spare-part courier bookings directly from your ERP: technical interfaces, required fields and steps to automate bookings with x25pronto.
Quick answer
Answer: Automate express spare-part bookings from your ERP using a REST/HTTPS API or SFTP file transfer. Send required data (pickup/delivery address, dimensions, weight, time window, order ID, contact, handling flags), validate inputs and submit a booking request. x25pronto returns a transport ID and provides status updates via webhook or API polling.
Why integrate spare-part bookings into your ERP?
Manufacturers and service teams need spare parts fast. Manual courier orders add delays and errors. An ERP integration reduces input mistakes, speeds up booking and shortens machine downtime across Switzerland.
Which interfaces work best?
Common choices are RESTful JSON APIs over HTTPS and SFTP file exchange using CSV/JSON. REST APIs enable real-time booking and immediate feedback. SFTP suits batch jobs. Both support webhooks or polling for status updates.
Required fields for express spare-part orders
At minimum include: pickup address (company, street, postal code, city), recipient address, contact phone, number of packages, dimensions (LxWxH) and weight, desired time window or ASAP flag, internal order number and declared value. Optional fields: return address, special handling notes, and PDF attachments.
How an automatic booking flows
1) ERP builds a booking request with required fields. 2) Request is sent to x25pronto API or uploaded to SFTP. 3) API validates data and returns a transport ID and ETA. 4) Webhook notifies your ERP of status changes (picked up, in transit, delivered). 5) Proof of delivery is returned digitally.
Error handling and validation
Validate addresses using postcode/city checks. Enforce size/weight limits and mandatory fields. On validation errors, block the booking and show a clear error to the dispatcher. Add retry logic for network issues and keep a dead-letter file for manual follow-up.
Implementation tips
Start with a pilot in one site such as Zurich or Basel. Use sandbox endpoints and map ERP fields to API fields early. Define SLA and escalation procedures. Implement webhooks for state changes and automate notifications to technicians.
Frequently asked questions
Which data formats does the API accept?
Typically JSON over HTTPS for real-time calls. For batch processing, CSV or JSON over SFTP is common. Confirm exact formats with your x25pronto integration contact.
How do I receive status updates in my ERP?
Use webhooks to receive push events on status changes. Alternatively poll the API at intervals to fetch status.
What if an address is incorrect?
The API returns a validation error. Your ERP should block the booking, display the error and allow the dispatcher to correct it.
How should I test the integration?
Use a sandbox API and test orders with dummy addresses. Test error scenarios, timeouts and webhook retries before going live.