
Successful logistics platform development cuts costs by attacking three things at once: empty space in vehicles, manual handoffs between systems, and failed deliveries. A well-built platform ingests orders automatically, plans routes against real constraints such as capacity, time windows and driver hours, tracks execution live and keeps customers informed so fewer deliveries fail. This guide walks through how such a platform is designed and built, using an illustrative scenario of a mid-size US distributor, and covers architecture, route optimization, legacy integration, cost modeling and the trade-offs between custom and commercial software.
Key takeaways
- The largest savings in a logistics platform usually come from better vehicle utilization, fewer failed deliveries and less manual data entry, not from any single advanced feature.
- Open-source solvers such as Google OR-Tools or Vroom handle vehicle routing with time windows well, so engineering effort is better spent on integration, data quality and dispatcher tools.
- Legacy warehouse or ERP integration is typically the riskiest part of the project and deserves a generous share of budget, plus reconciliation and alerting from the first release.
- Keeping dispatchers in control of route approval builds trust in automated planning and catches constraints that the optimizer cannot know about.
- Model the return with your own fleet, volume and failure rates before building, and compare it honestly with the subscription cost of a commercial transportation management system.
Logistics Platform Development: The Problem It Solves
Consider a hypothetical regional distributor in the US Midwest running around 20 delivery vans and roughly 1,000 stops a day to retailers and businesses. Its operation has grown faster than its tooling. Orders arrive by email, EDI and phone and are typed into an aging transportation management system (TMS). A separate route planning tool builds the morning routes, which a dispatcher copies into printed manifests. Drivers call in when they finish stops or hit problems, and customer service fields a steady stream of where-is-my-delivery calls.
Where the money leaks
The cost of this setup is spread across several budget lines, which is why it often goes unnoticed. Dispatchers and coordinators spend hours each day re-keying data between systems and correcting the errors that re-keying creates. Routes are planned once in the morning and cannot adapt to late orders, traffic or a van that breaks down, short of a manual replanning exercise. Vehicles often leave partly full because nobody has time to consolidate loads, which means extra vans, extra drivers and extra fuel. Customers receive no proactive updates, so more deliveries fail because nobody is there to receive them, and every failed delivery costs nearly as much as a successful one while earning nothing.
Why fixing one piece is not enough
A better route planner alone does not help if orders still arrive late and incomplete. Tracking alone does not help if routes are poor. The value of a logistics platform comes from connecting order intake, planning, execution and customer communication around one data model, so improvements in one stage are not lost at the next handoff. That is the core design goal for the rest of this guide.
Typical scope
For a distributor like this, the platform needs to ingest orders automatically from the warehouse or ERP system, generate daily route plans that respect vehicle capacity, delivery windows and driver hours, dispatch routes to a driver app, track positions and delivery events in real time, send customers notifications at key milestones, capture proof of delivery and give managers a dashboard of operational KPIs.
Custom Platform or Commercial TMS?
Before writing any code, a distributor should evaluate commercial options seriously. Many good TMS and route planning products exist, and for standard operations they are often the faster, cheaper path.
When a commercial TMS fits
If your warehouse or ERP system is a mainstream product with supported connectors, your delivery rules are conventional and your fleet is small, a commercial platform configured well will usually beat a custom build on time to value. Subscription pricing is predictable, and the vendor carries the burden of maintenance, mobile app updates and mapping data.
When custom logistics platform development makes sense
Custom development earns its place when the hard part of the problem does not fit the packaged product. The most common reason is integration: a bespoke or heavily customized warehouse system with no standard API, which forces manual export and import into any commercial TMS and recreates the very data entry problem you set out to remove. Other reasons include optimization goals that differ from the defaults, such as prioritizing vehicle fill over distance, unusual service rules for specific customers, or a need to own operational data for analytics and future machine learning without vendor restrictions.
| Factor | Commercial TMS | Custom platform |
|---|---|---|
| Time to first value | Weeks of configuration | Typically several months to first production release |
| Legacy system integration | Limited to supported connectors | Built to fit your systems directly |
| Optimization objectives | Vendor defaults with some settings | Fully tunable to your cost structure |
| Pricing model | Per vehicle or per user subscription | Upfront build plus hosting and maintenance |
| Data ownership | Held in the vendor platform | Held in your own cloud account |
A hybrid option
Some teams use a commercial routing API, such as Google’s Route Optimization API, inside an otherwise custom platform. This trades per-request fees for less solver work and can be a sensible middle ground at moderate volumes.
Logistics Platform Development: Reference Architecture
A practical architecture for a fleet of this size does not need dozens of microservices. A modular monolith with clear internal boundaries is easier to build, test and operate with a small team.

Bounded contexts
The platform splits naturally into three contexts. Order management handles intake, validation and order status. Route planning holds vehicles, drivers, depots, constraints and the optimization runs. Execution and tracking manages dispatched routes, live positions, delivery events and proof of delivery. In a Django codebase, each context becomes its own app with its own models and service layer, communicating through internal Python interfaces rather than network APIs. If volume later justifies it, a context can be extracted into a separate service along those same boundaries, as our article on microservices architecture for supply chain discusses.
Core components
PostgreSQL stores transactional data, with the PostGIS extension for geographic queries such as finding stops within a zone. Celery workers with Redis or RabbitMQ run route optimization, integration jobs and notifications outside the request cycle. Django Channels, backed by Redis, provides WebSocket connections for live updates. A React dashboard gives dispatchers a map view, built with a library such as Leaflet or Mapbox GL JS, alongside route lists and exception queues. Everything runs on a managed cloud such as AWS, with the database, queues and object storage for proof-of-delivery photos as managed services.
Event flow
An order arrives and is validated. Overnight or early morning, a planning job builds routes. A dispatcher reviews and approves them, and the driver app receives its route. As drivers progress, location pings and delivery events stream back, update the dashboard and trigger customer messages. A nightly reconciliation job checks that every order in the source system has a matching status in the platform.
Route Optimization and Dispatch
Route optimization is the technical heart of the platform, but it is also the part where buying or reusing proven tools makes the most sense.
Solving the vehicle routing problem
The underlying problem is the vehicle routing problem with time windows (VRPTW): assign stops to vehicles and sequence them so every delivery arrives within its window, no vehicle exceeds its capacity and no driver exceeds allowed working hours. Google OR-Tools is a mature open-source library with a routing solver that handles these constraints, along with pickups and deliveries, multiple depots and vehicle-specific limits. Vroom is another open-source option with a simpler HTTP interface. Building a custom solver from scratch is rarely justified, because it would consume much of the budget without beating these tools on real-world problems at this scale.
Choosing the objective
The objective function is where business knowledge matters. Minimizing total distance alone can produce routes that leave vans half empty, which misses the main cost driver. A better objective for many distributors combines distance and time with a fixed cost per vehicle used, so the solver prefers fewer, fuller vans unless the extra distance outweighs the saving. Set a time budget for each solve, for example 30 seconds for a full daily plan and a few seconds for single-route replanning, so dispatchers are never left waiting.
Driver hours and US rules
For property-carrying commercial motor vehicles, the FMCSA hours-of-service rules limit driving to 11 hours within a 14-hour on-duty window after 10 consecutive hours off duty, and electronic logging devices are generally required for drivers subject to those rules. Many last-mile vans fall below the weight thresholds that trigger these federal rules, but state rules and company policy may still apply. Encode the applicable limits as hard constraints in the solver and ask counsel which rules cover your fleet.
Human approval
Have the solver propose routes and let dispatchers review, adjust and approve them before dispatch. Dispatchers know things the system does not: a customer who needs a particular driver, a van with a known fault, a road closure that is not yet in traffic data. Log every override, because the patterns reveal constraints you should add to the model. Our guide to route optimization in logistics covers solver tuning in more depth.
Real-Time Tracking and the Driver App
The driver app is where the plan meets the road, and its design affects data quality across the whole platform.
Progressive web app or native app
A progressive web app (PWA) is faster to build and deploy, uses one codebase for every device and can capture GPS, photos and signatures through standard browser APIs. The significant limitation is background location: browsers, especially on iOS, do not allow a web app to report location reliably while it is in the background or the screen is off. If drivers use company-issued Android devices kept in the foreground on a dashboard mount, a PWA can work well. If you need dependable background tracking on personal iPhones, a native or cross-platform app built with Flutter or React Native is the safer choice. OnWay, a local delivery app built with Flutter, illustrates the cross-platform route.
Location updates and live dashboards
Send location pings every 15 to 60 seconds while a route is active, plus an immediate update on each delivery event such as arrived, delivered or failed. Batch pings when connectivity drops and replay them when the signal returns, since rural routes often have dead zones. On the server, write positions to a time-ordered table and push updates through Django Channels to dispatchers viewing that route. Keep the dashboard responsive by sending only the latest position per vehicle to the map, with full history available on request. Our article on real-time fleet management apps goes deeper on this pipeline.
Proof of delivery
Capture GPS coordinates, timestamp, status, recipient name or signature and an optional photo at each stop. For high-value goods, scan a barcode to confirm the right item was delivered. Generate a proof-of-delivery PDF server-side with a library such as WeasyPrint so customer service and finance can resolve disputes quickly.
Driver privacy
Location data about employees and contractors is personal information. Track only while a route is active, explain clearly what is collected, and set retention limits. Some states, such as New York, require notice to employees about electronic monitoring, and California’s CCPA as amended by the CPRA covers employee data. Ask counsel what notices and policies your operation needs.
Legacy System Integration: The Hardest Part
In many logistics projects, integration with an older warehouse or ERP system carries more risk than any other component. It deserves early attention and a realistic budget.
Working with what the legacy system offers
Older systems often lack a REST API. They may expose a database the vendor does not support for external access, a scheduled file export in a fixed-width or CSV format, or EDI messages. A pragmatic approach is a small integration agent that runs near the legacy system, watches for new export files, parses them, normalizes records into a clean JSON schema and posts them to the platform’s inbound API over HTTPS. Status updates can flow back through whatever import mechanism the vendor supports. A delay of a minute or two between order confirmation and platform intake is usually acceptable for same-day route planning.
Defensive engineering
File and EDI integrations are fragile compared with modern APIs, so build defenses in from the start. Validate every record against a schema. Send records that fail validation to a dead-letter queue with clear error messages rather than dropping them. Make inbound processing idempotent so a re-sent file does not create duplicate orders. Run a daily reconciliation that compares counts and statuses between the source system and the platform and alerts when they diverge beyond a threshold. These checks often uncover data quality problems in the source system that nobody knew existed, and fixing them upstream reduces manual corrections further.
Budgeting for uncertainty
Integration estimates are the least reliable part of a logistics project because the details of legacy formats only emerge once work begins. Plan a short discovery phase to obtain sample files, documentation and access, and hold contingency in the budget. Our API development and integrations work follows this pattern of discovery first, then build, then reconcile.
Modeling the Cost Savings Before You Build
A logistics platform should be justified with your own numbers. The structure of the model matters more than any industry benchmark.
Vehicle utilization
Start with current average load as a share of capacity and the number of vehicles dispatched daily. In the hypothetical distributor, suppose vans leave at about two-thirds of capacity on average. If consolidation raises that substantially, the same stops may be served with several fewer vehicles per day. Multiply the reduction by the daily cost of a vehicle and driver, including fuel, maintenance, insurance and wages, to estimate the annual saving. Distance reduction from better sequencing adds further fuel savings.
Labor and administration
List the manual tasks the platform removes: re-keying orders, building routes by hand, updating delivery status from phone calls and answering status inquiries. Estimate hours per day for each and multiply by loaded labor cost. In practice, these hours are often redeployed to higher-value work rather than eliminated, which is still a real gain.
Failed deliveries
Measure your current failed delivery rate and the cost of each redelivery. Proactive notifications, accurate arrival windows and the ability for customers to leave instructions usually reduce failures. Even a few percentage points on a high daily volume can produce meaningful savings, because each avoided failure saves nearly the full cost of a stop.
Putting it together
Add the annual savings, subtract hosting, maintenance and any third-party API costs, and compare the result with the build cost. A platform with this scope, covering order intake, optimization, a driver app, tracking, notifications and one legacy integration, typically falls in the USD 30K to 50K band or above USD 50K depending on integration complexity and the number of apps. Lycore works at USD 25 per hour, on a fixed project price or on a monthly retainer. If the model shows a payback period you are comfortable with on conservative assumptions, proceed; if not, narrow the scope to the strongest lever first.
Pros and Cons of Custom Logistics Platform Development
Pros
- Direct integration with bespoke warehouse or ERP systems that commercial products cannot connect to cleanly.
- Optimization objectives tuned to your actual cost structure, such as vehicle fill, rather than generic defaults.
- Operational data held in your own cloud account, ready for analytics and future machine learning.
- No per-vehicle or per-user license fees, which becomes more favorable as the fleet grows.
Cons
- Higher upfront investment than a first-year commercial subscription, with a longer path to payback.
- Ongoing responsibility for maintenance, security updates, mapping and mobile app releases.
- Longer time to first value, often several months, compared with configuring a packaged TMS.
- Integration risk with legacy systems that can push budget and schedule beyond initial estimates.
Frequently Asked Questions
Which route optimization tools work best for a custom logistics platform?
For most fleets of tens of vehicles and hundreds to a few thousand daily stops, Google OR-Tools is a strong starting point. It supports capacity limits, time windows, driver breaks, multiple depots and pickup-and-delivery pairs, and it has Python, Java, C++ and .NET interfaces. Vroom is a good open-source alternative with a simple HTTP interface that many teams find easier to integrate. If you prefer not to run a solver yourself, hosted services such as Google’s Route Optimization API provide similar capabilities on a pay-per-use basis. Commercial mathematical solvers such as Gurobi are worth considering for very large or unusual problems, but they bring licensing costs. Whatever you choose, wrap it behind your own interface so you can switch later.
How should real-time route replanning work?
Replanning should balance better routes against the confusion of constantly changing instructions. A tiered approach works well. Small delays are absorbed by updating estimated arrival times and notifying customers, without changing the stop sequence. Moderate delays trigger a re-optimization of the affected route only, checking whether resequencing the remaining stops improves on-time performance. Major disruptions, such as a breakdown or an urgent large order, trigger a wider replanning that may move stops between vehicles. In each case, the dispatcher should see the proposed change and approve it before it reaches drivers. Single-route replanning with a couple of dozen remaining stops typically solves in seconds, which is fast enough for interactive use on the dispatch dashboard.
How long does logistics platform development take?
A first production release covering order intake, route planning, a driver app, live tracking, customer notifications and one legacy integration commonly takes around three to five months, depending on the integration and the choice between a progressive web app and a native mobile app. Discovery and integration access often determine the real schedule, so obtaining sample files, documentation and test environments in the first weeks is important. Phasing helps: the first release can focus on intake, planning and the driver app, with customer notifications, analytics and advanced replanning following once the core is stable. Running the new platform alongside existing processes for a few weeks before full cutover reduces risk and builds dispatcher confidence.
What data does a logistics platform need to get started?
At minimum you need clean customer addresses with geocoded coordinates, delivery time windows, order sizes in the same unit as vehicle capacity (weight, volume, pallets or cases), vehicle capacities and availability, driver shifts and depot locations. Historical delivery records, including actual arrival times and service durations at each stop, make the plans far more realistic, because the solver needs to know how long a typical stop takes. Many projects begin with an address cleanup exercise, since bad geocodes cause poor routes and failed deliveries. Collect failure reasons from the start as well, so you can measure which causes notifications and better windows actually reduce. Good input data improves results more than any amount of solver tuning.
Conclusion
Logistics platform development delivers savings when it connects order intake, route planning, execution and customer communication into one coherent system. The technology is proven and largely open source: OR-Tools or Vroom for routing, Django and PostgreSQL for the core, WebSockets for live tracking and a mobile app suited to your devices. The real work, and the real risk, sits in legacy integration, data quality and the operational details that make dispatchers trust the system. Model the return with your own numbers, start with the strongest cost lever, keep humans in control of dispatch and invest generously in integration and reconciliation.
Building a logistics, dispatch or delivery platform for your operation? Talk to Lycore. We can help you scope the first release, plan the legacy integration and build the platform on an hourly, fixed-price or retainer basis.



