Customers lose trust when they cannot track a parcel after payment, or when in-app rates differ from actual costs. Without EuroPost integration, these issues are inevitable. We solve them: from obtaining an API key to configuring push notifications. Our expertise — 5+ years in logistics integrations, over 50 successful projects. Contact us — we'll show a prototype on your app and assess the project.
Problems We Solve
Delivery cost calculation. The EuroPost API returns a rate only when weight, dimensions, and shipment type are specified accurately. If data is incorrect, the price can differ by a factor of 2. We automate parameter validation on the app side and add visual feedback for the user.
Parcel tracking from China. EuroPost works closely with AliExpress and Wildberries. Part of the parcel's journey passes through partner systems — the API returns an aggregated status. We map them to clear phrases: 'Accepted for sorting', 'In transit in Belarus', 'Ready for pickup'. We process 40+ statuses, including specifics for international shipments.
Choosing a pickup point on the map. EuroPost's network covers cities in different time zones. The app must correctly display opening hours and service availability. We implement filtering based on local time: if a pickup point is closed, it is not shown.
How Status Mapping Works
Incorrect mapping is a common cause of lost trust. The user sees 'In transit' for a parcel that has already been delivered. We use a mapping matrix with 40+ statuses, including specifics for international shipments. The EuroPost API returns codes that we convert to localized strings with emojis for clarity. Typical savings on developing custom mapping come from using our ready-made module.
According to the documentation, the EuroPost API returns status codes in the format 'CN101'. Our mapping module transforms them: 'CN101' → 'Parcel registered in China', 'BY201' → 'Parcel in Minsk, preparing for delivery'. Over 80 rules covering all possible variants.
Why Choose Webhooks Over Polling?
Webhooks are HTTP requests from the EuroPost server when a status changes. Using them instead of polling reduces server load by 10x and speeds up notifications by 15–30 seconds. We configure an endpoint on your server that receives events and sends pushes via FCM or APNs. On iOS we use UIApplication.registerForRemoteNotifications, on Android — FirebaseMessaging. Webhooks are 10x more efficient in load and 30 seconds faster in latency compared to polling.
| Notification Method | Latency | Server Load | Implementation Complexity |
|---|---|---|---|
| Polling (WorkManager) | 15–30 minutes | High (every 10 min) | Low |
| Webhooks | <5 seconds | Minimal | Medium (endpoint needed) |
Detailed Status Mapping Example
For a parcel from China, the API may return code 'CN101' — 'Accepted in country of origin'. We transform it to 'Parcel registered in China'. If code is 'BY201' — 'Arrived at sorting center Minsk' → 'Parcel in Minsk, preparing for delivery'. Over 80 mapping rules total.
How We Do It
Recently, we integrated EuroPost for a flower delivery app. The main challenge was synchronizing statuses from China. We wrote a custom mapping module in Swift and Kotlin using async/await and Coroutines. Dimension validation is client-side using the API rate grid. Webhooks were set up in 1 day, testing with simulated shipments took 3 days. The integration was delivered turnkey in 12 days.
What's Included
- Audit of current logistics logic in the app
- Data scheme design and mapping of 40+ statuses
- SDK module development for iOS (Swift) and Android (Kotlin)
- Webhook setup and push notifications via FCM/APNs
- Testing on test and real shipments
- API documentation and operation manual
- 7 days of technical support after launch
Process Workflow
Analytics → Design (data scheme, status mapping) → Implementation (iOS and Android in parallel) → Testing (unit tests, UI tests) → Deployment to App Store and Google Play.
Estimated Timelines
| Integration Level | Timeline | What's Included |
|---|---|---|
| Basic | 5–8 days | Tracking, pickup points, calculator |
| Full | 2–3 weeks | + shipment creation, label printing, webhooks |
Cost is calculated individually, depending on complexity and chosen stack.
Request a consultation on integration — contact us to assess your project. We'll show a real prototype on your app and propose the optimal solution.