Delivery Tracking Bot in Mobile App

NOVASOLUTIONS.TECHNOLOGY is engaged in the development, support and maintenance of iOS, Android, PWA mobile applications. We have extensive experience and expertise in publishing mobile applications in popular markets like Google Play, App Store, Amazon, AppGallery and others.
8+Years of work900+Completed projects100+In house employees19+Partners
Development and support of all types of mobile applications:
Information and entertainment mobile applications
News apps, games, reference guides, online catalogs, weather apps, fitness and health apps, travel apps, educational apps, social networks and messengers, quizzes, blogs and podcasts, forums, aggregators
E-commerce mobile applications
Online stores, B2B apps, marketplaces, online exchanges, cashback services, exchanges, dropshipping platforms, loyalty programs, food and goods delivery, payment systems.
Business process management mobile applications
CRM systems, ERP systems, project management, sales team tools, financial management, production management, logistics and delivery management, HR management, data monitoring systems
Electronic services mobile applications
Classified ads platforms, online schools, online cinemas, electronic service platforms, cashback platforms, video hosting, thematic portals, online booking and scheduling platforms, online trading platforms

These are just some of the types of mobile applications we work with, and each of them may have its own specific features and functionality, tailored to the specific needs and goals of the client.

Offered services
Showing 1 of 1 servicesAll 1735 services
Delivery Tracking Bot in Mobile App
Simple
~2-3 business days
FAQ
Our competencies:
Development stages
Latest works
  • image_mobile-applications_feedme_467_0.webp
    Development of a mobile application for FEEDME
    756
  • image_mobile-applications_xoomer_471_0.webp
    Development of a mobile application for XOOMER
    624
  • image_mobile-applications_rhl_428_0.webp
    Development of a mobile application for RHL
    1054
  • image_mobile-applications_zippy_411_0.webp
    Development of a mobile application for ZIPPY
    947
  • image_mobile-applications_affhome_429_0.webp
    Development of a mobile application for Affhome
    862
  • image_mobile-applications_flavors_409_0.webp
    Development of a mobile application for the FLAVORS company
    445
Show more works

Implementing Delivery Tracking Bot in Mobile Application

Package stuck on customs for third day — user doesn't know because tracker site shows last update "2 days ago" with no notifications. Delivery tracking bot turns passive waiting into active information.

Sources for Delivery Status Data

Each logistics company is separate API or scraping. Major players provide official APIs:

  • CDEK: REST API (api.cdek.ru), OAuth 2.0, real-time statuses
  • DHL: Tracking API (api.dhl.com/track/shipments), API key
  • FedEx: Track API v1 (apis.fedex.com/track/v1/trackingnumbers)
  • Russian Post: tracking via tracking.russianpost.ru/rtm34 (SOAP, unpleasant but works)
  • Boxberry, OZON Rocket — REST API with docs

For companies without official API or closed access use scraping via Puppeteer/Playwright on server — less reliable, breaks on site redesign, but works for MVP.

Polling System Architecture

Bot can't receive pushes from courier — must poll their API. Polling strategy:

  • New tracking number: first 24 hours — poll every 30 minutes
  • "In transit" status: every 2 hours
  • "On sorting" or "On customs" status: every 4 hours
  • "Delivered" status: stop tracking

Implement via scheduler (Bull Queue with delayed jobs). On each poll compare new status with last saved — if changed, send Telegram notification and FCM push to app.

Mobile App: Tracking UX

Main screen — list of active shipments with last status and update time. Tap shipment — detailed timeline with status history.

On Flutter build list via ListView.builder with Hive for local cache. Each item — card with color-coded status: green (delivered), orange (in transit), red (problem/delay).

Push notification on status change leads via deep link directly to specific shipment screen. On iOS via Universal Links, on Android via App Links with Intent and tracking_id parameter.

Handling Courier API Errors

Courier APIs aren't stable. CDEK periodically returns 500 for hours, Russian Post SOAP endpoint down for days.

Strategy: retry with exponential backoff (3 attempts at 5/15/60 min intervals). If three attempts fail — notify user: "Couldn't update status [Courier Name]. Will try later". Don't leave silent.

Integrating bot with 2–3 couriers and mobile client — 2–3 weeks. Supporting 10+ couriers with unified parser — 5–7 weeks.