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.
Rate and tariff lookup via API: automating cost transparency
Discover how API tariff lookups let Swiss teams in Zurich, Geneva or Basel calculate transport costs quickly, run price simulations and automate budget allocation.
Quick answer
An API‑based tariff lookup returns reproducible prices for direct and overnight courier services. Key parameters are pickup and delivery locations (e.g. Zurich, Basel), dimensions, weight, time window, insurance and extras. Use these inputs to run price simulations and push results into budget and cost‑centre workflows.
Why a tariff API helps Swiss businesses
An API gives transparent, repeatable rates without manual quotes. Procurement, logistics and finance teams save time. It is especially useful for many one‑off deliveries or for feeding standard rates into ERP systems.
Essential tariff parameters to send
Location data: exact addresses or Swiss postal codes (e.g. 8004 Zurich). Package details: length, width, height and weight. Time window: same‑day, overnight or specific delivery slot. Service options: declared value, recipient contact, multiple stops. Extra charges: parking, difficult access. Each parameter affects the price.
Building price simulations
Start with a base simulation: same zone pickup and delivery, standard weight and size. Run variance tests by changing weight, dimensions or time windows one at a time. Create scenarios for frequent routes, urgent deliveries, or longer trips to Geneva or Lugano. Capture results in a spreadsheet to set cost‑per‑shipment thresholds.
Feeding tariffs into budget and cost‑centre workflows
Export API results as JSON or CSV. Map fields to ERP cost objects: cost centre, project ID, customer, transport type. Automate monthly consolidated postings for recurring runs and set alerts for budget overruns. This assigns each delivery to a cost centre and keeps finance in control.
Technical and operational implementation tips
Use endpoint versioning and test in a sandbox. Validate addresses with a simple geocoding step before querying rates. Apply rate‑limiting and caching for repeated lookups. Implement logging and monitoring to detect rate changes or API errors quickly.
Example: price simulation for overnight Zurich to Lausanne
Parameters: pickup 8004 Zurich, delivery 1003 Lausanne, parcel 60×40×30 cm, 12 kg, overnight. A base simulation returns a ground rate. Change the delivery window or declared value to measure extra cost. Result: defined thresholds for economical handling and automated assignment to an ERP project code.
Frequently asked questions
What data quality is needed for tariff lookups?
Accurate addresses or postal codes, correct dimensions and true weight. Poor data causes wrong estimates or failed bookings.
How often should I refresh price simulations?
Monthly checks work for stable tariffs. Weekly reviews help when prices or volumes fluctuate.
Can tariff data be imported automatically into an ERP?
Yes. Exported JSON/CSV and a field mapping allow automatic postings and reporting.
What about cross‑border deliveries?
Customs, borders and different rules affect price and service. Check whether your API covers these factors or if you need extra modules.