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.
Contract terms between courier and pharmacy for sensitive deliveries
Practical guide on liability, controller/processor roles, data SLAs and proof obligations for courier-pharmacy contracts handling sensitive, securely packed shipments.
Quick answer
Contracts between a courier and a pharmacy should clearly set liability, roles (controller vs processor), data-SLAs and proof obligations. Put in writing: scope of service, processing details, security measures, liability limits and concrete proof such as delivery receipts, signatures and electronic tracking records.
1. Define roles: controller and processor
Specify who is the data controller and who acts as processor. Usually the pharmacy is the controller for patient data and decides processing purposes. The courier processes data on behalf of the pharmacy for delivery tasks. Record the roles and the permitted processing activities in the contract.
2. Liability: allocate risks and limits
Set out liability for loss, damage or data incidents. Agree what types of damage are covered and any liability caps. Make sure exclusions are transparent and lawful. Include reporting deadlines and contact points to speed up incident handling.
3. Privacy SLA: technical and organisational measures
Include a privacy SLA with concrete measures: access controls, encryption for electronic delivery data, driver training, secure handover procedures and data retention periods for proof records. Define audit intervals and reporting obligations, for example compliance checks or training attestations.
4. Proof obligations and record-keeping
Specify required proofs: physical or electronic signatures, handover photos (with consent), timestamps, GPS logs and digital delivery receipts. State retention periods and who may access the records. Define the format and deadlines for claims and dispute evidence.
5. Incident reporting and coordination
Describe reporting lines and timelines for loss, damage or privacy breaches. Who notifies whom and within what time? Describe cooperation during investigations and remedies. A clear process reduces risk and speeds resolution for both parties.
6. Operational handover and exceptions
Agree packaging rules, identity checks on handover, labelling and allowed transport modes (e.g. securely packed items suitable for passenger cars). Specify exceptions, replacement deliveries and drop-off permissions. Concrete instructions reduce daily friction.
Frequently asked questions
Is the pharmacy always the data controller?
In most cases yes. The pharmacy decides processing purposes for patient data and is therefore the controller. The courier normally acts as a processor for the delivery.
What proof is needed for a legally sound delivery?
Clear timestamps, recipient signature or handover photo (with consent), electronic delivery record and where appropriate GPS logs. Set retention periods in the contract.
How should liability for damaged items be handled?
Agree which damages are covered, any maximum amounts and notification deadlines. Clear documentation obligations make claims easier to resolve.
What privacy clauses belong in a SLA?
Clauses on access control, encryption, staff training, deletion periods, breach notification and regular audits or reviews.

