Building an Uber-Like Medicine Delivery Platform — Powered by 100+ Drivers Daily

How we built a full-stack logistics platform for a California-based medicine delivery company — with real-time route optimization, geofenced deliveries, live driver tracking, and automated weekly payouts — all running smoothly since 2021.

CHALLENGE

The Problem We Solved

Our client Andrew runs a medicine delivery operation under Hanna’s Transportation Incorporated, based out of Rancho Cucamonga, California, serving the Los Angeles and Greater Los Angeles areas. Think of it like an Uber — but specifically for prescription medicine deliveries. Andrew’s clients are pharmacies. He provides them with two things: the technology to manage deliveries, and a fleet of drivers who actually do the deliveries. The idea is solid, the demand is real, but the logistics are genuinely complex. Medicine deliveries are time-sensitive, address-critical, and compliance-heavy. You can’t just wing it with a WhatsApp group and a spreadsheet.

CORE CHALLENGES BOX:

Pharmacies were using different prescription management software (Liberty RX, Digital RX, Pioneer RX) with no unified way to pull delivery addresses into one system; dispatcher had to manually coordinate routes without any optimization; drivers had no accountability layer — no way to verify deliveries were happening at the right location; no automated driver payout system, making weekly settlements a headache; the entire operation needed to scale across 100+ daily drivers without breaking.

Before Platform Delivery existed as a proper system, managing all of this — the routes, the drivers, the packages, the confirmations, the payments — was either manual, error-prone, or simply not happening at scale. As the operation grew, they needed a proper platform that could handle everything end to end, without the dispatcher running around putting out fires all day.

SOLUTION

Our Approach: One Unified Platform, Built for the Chaos of Last-Mile Delivery

We built Platform Delivery from the ground up — a two-part system with a web-based backend for dispatchers and a mobile app for drivers. The goal was simple:

Architecture Layers:

• Web Backend (Laravel + MySQL): This is where the dispatchers work. It connects with pharmacy prescription APIs, manages routes, tracks drivers in real time, and handles all the business logic.
• Mobile App (Flutter — iOS & Android): The driver-facing application. Handles route navigation, package verification, delivery confirmations, and push notifications.
• API Integrations: Firebase and FireStore for real-time data sync, FCM for push notifications, Google Maps API for route optimization (up to 25 packages), Nextbillion API for larger batches (25+ packages), Liberty RX / Digital RX / Pioneer RX for prescription and address data, Twilio for customer SMS notifications, Stripe for automated driver payouts.
• Infrastructure: Hosted on AWS. We handle all DevOps and server maintenance.

the dispatcher should be able to scan a bucket of medicine packages, click one button, and have an optimized delivery route sent to a driver’s phone — with everything tracked, verified, and logged automatically.

KEY TECHNICAL DECISIONS

• Multi-API Pharmacy Integration: Rather than building a rigid integration with one system, we designed a flexible layer that connects with whichever prescription API the pharmacy is using — Digital RX, Pioneer RX, or Liberty RX. The selection happens at the pharmacy account level, so the dispatcher doesn’t need to think about it.
• Two-Engine Route Optimization: We deliberately chose to use two routing APIs based on batch size. Google Maps API is accurate and cost-effective for smaller batches. For larger batches of 25+ packages, Nextbillion API handles the complexity better and gives more precise multi-stop optimization. Switching between them happens automatically based on package count.
• Geofencing as a Compliance Tool: In a regulated industry like medicine delivery, you need verifiable proof that packages reached the right address. Geofencing solves that — it’s not just a nice feature, it’s an accountability layer that protects both the client and the end customer.
• Stripe Automation for Driver Payouts: With 100+ drivers running routes daily, manual payouts would be a nightmare. The Stripe integration calculates and processes weekly payments without any human intervention, which means the finance side of the operation runs itself.
• AWS + Full DevOps Support: We didn’t just build the product — we own the infrastructure too. Platform Delivery is hosted on AWS, and Neuvo WebTech handles all the DevOps, updates, and server maintenance. The client doesn’t need a separate technical team.

Results

Impact & Metrics

Platform Delivery has been live since 2021 and has been running without interruption ever since. Within the first few months of launch, the platform was handling 100+ active drivers daily across the Los Angeles and Greater Los Angeles area — and that number has only grown. Here’s what the platform changed for the operation:

100+

Active Drivers Daily

3

Pharmacy APIs Integrated

0

Manual Payout Processing

4+ Years

Live & Continuously Upgraded

Beyond the numbers paragraph: Before this platform, the dispatcher’s day was consumed by manual coordination — looking up addresses, planning routes by hand, chasing drivers for confirmation, and doing the math on weekly payments. Now, a single dispatcher can manage an entire day’s worth of deliveries from one screen. Routes are optimized in seconds, drivers are tracked live, deliveries are geofence-verified, and every driver gets paid automatically at the end of the week. The operation runs — and it runs well.

PROCESS SECTION

Implementation Timeline