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.
Hybrid model: combining fixed slots and on‑demand rides
How do you combine fixed delivery slots with on‑demand rides? A practical guide for operations managers on SLAs, workflows, IT interfaces and KPIs.
Quick answer
A hybrid model pairs scheduled fixed slots for recurring deliveries with flexible on‑demand rides for ad‑hoc shipments. For operations managers the aim is to keep service levels steady, cut empty runs and make costs predictable. Start by setting clear SLAs for both streams, implement simple workflows and IT links, and track a few KPIs such as on‑time performance, vehicle utilization and cost per run.
Why choose a hybrid model
Many Swiss companies send both regular and spontaneous shipments. Fixed slots secure recurring deliveries and ease planning. On‑demand rides cover volatility and avoid bottlenecks. The hybrid approach helps use capacity more efficiently and stabilise delivery quality.
SLA design: two clear sets of rules
Define separate SLAs for fixed slots and on‑demand rides. For fixed slots set time windows, tolerances and repetition. For on‑demand rides set response times, maximum runtime and cancellation rules. Include responsibilities, escalation paths and communication channels in both SLAs.
Operational workflow: roles and transitions
Map the process from order intake to delivery. Assign roles: dispatch, driver, customer contact. Define how on‑demand tasks fit into the day (e.g. cut‑off windows for requests, buffers around fixed slots). Rules for prioritisation and rebooking reduce conflicts.
IT interfaces and booking flow
Link your ERP or order portal to the dispatch system via API or standard file import. Book fixed slots as recurring orders and on‑demand rides as ad‑hoc tasks. Use simple dashboards for a live overview and automated customer notifications.
Controlling: KPIs and reporting
Focus on a few meaningful KPIs: on‑time delivery (OTD), vehicle utilisation, cost per run, number of rebookings and response time for on‑demand requests. Run weekly operational reports and monthly reviews. Keep data separate for fixed slots and on‑demand rides to spot trends fast.
Pilot and roll‑out
Start with a pilot in a market such as Zurich or Geneva. Test SLA details, the booking flow and reporting for three months. Collect feedback from drivers and customers. Scale stepwise and adjust SLAs and buffer times to real utilisation.
Frequently asked questions
How many fixed slots should I plan?
Analyse 3–6 months of historical shipments. Find recurring runs and customer groups. Plan slots for the 60–70% of reliably recurring deliveries; cover the remainder with on‑demand rides.
What buffer time works for fixed slots?
A 15–30 minute buffer per slot is a pragmatic start. Exact buffer depends on traffic and handling times. Buffers reduce delays without inflating costs.
How do I stop on‑demand rides from blocking fixed slots?
Set dispatch prioritisation: fixed slots have priority in critical corridors, on‑demand tasks fill free windows or are routed to succession plans. Use real‑time data to reallocate tasks.
Which IT data do I need for controlling?
At minimum: order type (fixed/on‑demand), pickup and delivery timestamps, run cost, vehicle ID and status updates. These metrics support OTD calculation, cost allocation and trend analysis.