Delivery Operations Platform for LogicPath Logistics
LogicPath Logistics is a last-mile delivery company that runs its daily operations on custom software. VLO Labs works across that platform, from the dispatcher CRM and billing to native driver apps, a shipper API and the public website.
- Industry
- Last-mile delivery and logistics
- Status
- Live
- Platforms
- Web, iOS, Android
The challenge
A delivery company depends on a chain of software. Shippers send orders, dispatchers build routes, drivers scan and deliver, recipients check status, and each shipment has to be billed correctly. When this work began in 2025, LogicPath already had a backend and a dispatcher CRM in place, so the job was to extend software the business was already using, not to start over.
The requirements became more specific as shippers came on board. Shippers wanted to connect their own systems, print carrier labels, receive the same reports they got from their previous carrier, and be billed against contract pricing. The driver app also needed a real application and approval process before it could be offered on the public app stores.
Our approach
The platform is treated as one product made of separate parts: a backend API, a dispatcher and shipper web app, a public tracking app, the marketing site, iOS and Android driver apps, and infrastructure defined in code. New work goes into the running system in steps, and the backend has been kept current along the way, including an upgrade to PHP 8.5.
Requests from one shipper are built as configuration that any account can use. Scan behavior and rate cards are set per customer, so a new contract does not change how existing accounts operate or get billed. A customer with no rate card is billed exactly as before.
What we built
Dispatcher CRM
A web app for managing orders, routes, drivers, customers, terminals, invoices and reports, with route optimization and address validation.
Native driver apps
Separate SwiftUI and Jetpack Compose apps for viewing routes, scanning package barcodes, capturing proof of delivery by photo, signature or notes, reporting failed deliveries, and working offline until the connection returns.
Courier application and review
Drivers apply, upload their license, insurance and registration, and wait in a review queue. A dispatcher approves them onto a customer account before routes appear. Documents are kept in private storage and opened through signed links.
Shipper portal
A logged-in area where shippers create orders, upload them in bulk, track packages and manage their own users.
Integrations API
An API for shipper systems covering orders, quotes, shipping labels, cancellations and webhook status updates. Labels can be produced as ZPL for thermal printers.
Contract billing and invoicing
Rate cards price each order by zone and weight, then add fuel, residential or remote charges and extra fees such as signature, declared value and oversize handling. Dispatchers can apply or waive fees.
Shipper reports
On-time shipment and open package reports, modeled on the exports a shipper already received from its previous carrier.
Public website
A Next.js marketing site with service area and pricing pages and a contact form.
Cloud infrastructure
Production infrastructure defined in code, with automated deployments for the web front ends.
Engineering highlights
Scans that drive operations
A step in a customer's scan sequence can trigger actions such as assigning a package to today's route or to the driver who scanned it. For another customer the same step only records the event. Warehouse scans, route scans and driver scans go through one code path, so a repeated scan does not create a duplicate event.
Dates in the customer's time zone
Report dates are calculated in each customer's time zone, because an evening pickup can be already the next day in UTC. Expected delivery counts business days from each destination ZIP's transit time, and weekend or holiday pickups start on the next business day.
Billing records that hold up to review
An order on a non-void invoice is locked, so corrections go through invoice adjustments. Waived fees stay on record for audit and are never billed.
Signed webhooks with retries
Webhook payloads are signed with HMAC-SHA256 so receivers can verify them. Failed deliveries are tried up to three times, and client errors are not retried.
Order activity history
Moves, scans and reassignments are written to an activity log in the same transaction as the change, so the history shows who changed an order and when.
Where it stands
- Public website
- Live
Technology
Have something similar in mind?
Tell us what you need to build and we will give you a straight answer on how to approach it.
Get a free consultation