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.
Integrating courier scans into your ERP/QA system
How to ingest courier scan data into your ERP or QA system: API patterns, file formats, field mapping, security and a practical rollout plan for Swiss companies.
Quick answer
You can reliably import courier scan data into ERP and QA systems by defining clear interfaces, standard file formats (JSON, PDF, XML), and solid error handling. Map required fields first (shipment ID, scan type, timestamp, location, recipient confirmation). Use webhooks for real‑time events and batch APIs for bulk reconciliation. Specify authentication (OAuth2 or API keys), versioning and Swiss data handling rules. A sandbox, replay data and staged rollout reduce integration risk and speed up adoption.
What courier scans should include
Standardise required fields before you connect systems. At minimum include: shipment ID, scan type (pickup, interim, delivery), timestamp with timezone, location (GPS or site name), recipient data (name, optional signature/photo) and status. Optional fields: weight, packaging ID, driver notes.
File formats and payload examples
Use JSON for structured data. Use PDF or JPG for signatures and photos. XML remains valid for legacy ERPs. Example JSON payload: {"shipmentId":"X25-123","scanType":"DELIVERED","timestamp":"2026-09-09T14:32:00+02:00","location":{"lat":46.948,"lon":7.447},"recipient":{"name":"Müller AG","signatureUrl":"https://.../sig.jpg"}}.
API patterns: Webhooks vs Batch APIs
Webhooks suit real‑time updates like delivery events. Implement retries, idempotency keys and a dead‑letter queue for failed events. Batch APIs suit hourly or daily mass syncs. Provide paging, filters (date, status) and bulk acknowledgements. A hybrid approach works well: webhooks for live events, batch for reconciliation.
Authentication, security and data protection
Use OAuth2 or secure API keys with IP allow‑listing. Encrypt transport with TLS 1.2+ and store personal data encrypted at rest. Respect Swiss data rules and your retention policies. Log accesses and provide auditable reports for QA checks.
Error handling and monitoring
Define clear error codes for missing fields, invalid signatures or auth failures. Implement automatic retries with backoff and alerts for persistent errors. Use monitoring dashboards, alert channels (Slack, email) and hourly reconciliation jobs against ERP master data.
Test and rollout checklist
Begin in a sandbox with replayable test data. Run integration, load and failover tests. Roll out in phases: pilot clients, 24–48h close monitoring, then full deployment. Provide API contracts and supply Postman collections or OpenAPI/Swagger specs.
Frequently asked questions
Which fields matter most for QA tracking?
Shipment ID, timestamp with timezone, scan type, location, recipient confirmation (photo/signature) and driver ID. These enable traceability and root cause analysis.
How do I avoid duplicate webhook events?
Use idempotency keys and check shipment ID plus event timestamp. Add deduplication in the consumer layer to ignore repeats.
Which auth method is best?
OAuth2 for larger integrations with roles; API keys with IP restrictions for simple trusted connections. Always use TLS.
Should media files be stored together with JSON?
Keep structured data in JSON and store media (JPG/PDF) separately in an object store. Provide secured URLs with short‑lived access tokens.