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.
Batch vs. real-time booking: when to use which method
Clear guidance for Swiss businesses on choosing batch or real-time courier booking. Covers costs, latency, operational effort and industry examples.
Quick answer
Use batch booking for routine, high-volume shipments with predictable schedules. Choose real-time booking when immediate confirmation, low latency or fast reaction to changes matter — for example for urgent spare parts or time-critical deliveries.
What is batch booking?
Batch booking collects many orders and sends them to the courier in one interval. Typical workflows export orders from ERP or WMS once per night or during fixed windows. It is stable and fits planned, recurring shipments.
What is real-time booking?
Real-time booking sends each order immediately via an API. You get instant confirmation and can handle changes or cancellations quickly. It suits ad-hoc or urgent shipments.
Pros and cons at a glance
Batch: lower operational overhead, simpler integration and often fewer transaction costs. Drawback: latency and slower reaction to changes. Real-time: immediate feedback, better error handling and dynamic dispatch. Drawback: higher integration effort and more frequent API calls.
Cost considerations for Swiss businesses
Batch reduces API calls and manual handling, saving money for many small shipments. Real-time may increase transaction costs but can cut error and cancellation expenses. Calculate total cost: dev effort, integration, transaction fees and error remediation.
Latency and operational effort
Batch introduces interval latency. If your SLA needs confirmations in minutes or seconds, batch won’t work. Real-time needs robust monitoring, retry logic and clear error rules. Small operations often prefer batch; teams with IT resources can implement real-time.
Typical Swiss use cases
Batch fits regular B2B deliveries, return clusters, production shipments from Basel/Zürich and distribution centres with night cycles. Real-time fits spare-part dispatch in machinery, just-in-time deliveries, lab samples in life sciences and eCommerce with same-day options in cities such as Zurich or Geneva.
Frequently asked questions
Can I use both methods together?
Yes. Many companies use batch for routine orders and real-time for exceptions. You can implement rules that route orders by priority, weight or SKU to the preferred method.
How does shipment volume affect the choice?
Predictable high volumes favour batch for efficiency. Small, unpredictable or time-critical shipments justify real-time booking.
What integration effort should I expect?
Batch often needs export scripts or SFTP. Real-time requires API integration, authentication and monitoring. Allocate developer time and testing.
Do SLAs influence the decision?
Yes. Tight SLA or customer requirements for instant confirmation point to real-time. Flexible SLAs are fine with batch.