/ Project: Milevra · 2024 /

SaaS dashboard for logistics

Cargo tracking web app: real-time maps, roles & permissions, public API for company clients. Built in 16 weeks and deployed with CI/CD.

Key decisions Map, roles and a public API in one dashboard
Type
Apps
Industry
Logistics / SaaS
Year
2024
Build stages 16 weeks
  1. Brief & research ≈ 2 wk
  2. UX/UI design ≈ 5 wk
  3. Development ≈ 7 wk
  4. QA & launch ≈ 2 wk
  • React
  • Node.js
  • PostgreSQL
  • Mapbox

Product screens 06

  1. 01 Shipment map
  2. 02 Trips and statuses
  3. 03 Roles and access
SaaS dashboard for logistics
  1. 04 Client access
  2. 05 API
  3. 06 Mobile version
About the project

A SaaS dashboard for a logistics company: a cargo map, delivery statuses and client access. The mobile version serves drivers and managers on the road.

  • Live map A Mapbox map with routes and the current position of every load.
  • Delivery statuses A timeline of each trip from loading to hand-over.
  • Roles & access Separate rights for dispatchers, drivers and clients.
  • Client API Clients pull statuses into their own systems — no calls to a manager.
01 · The brief

The internal cargo-tracking tool ate manager hours and had no architecture: clients kept calling instead of opening a link.

02 · What we built

We turned it into a real SaaS dashboard: live maps, roles and permissions, a public client API, and cloud deploys with CI/CD and monitoring.

  1. Before Clients phone a manager to find out where their cargo is.

    After Clients see the status themselves — in their own access or via the API in their system.

  2. Before Tracking shipments eats up managers’ hours.

    After A real-time map with routes and the current position of every shipment.

  3. Before An internal tool with no architecture and no access control.

    After Roles for dispatchers, drivers and clients, and a structure built to grow into SaaS.

03 · The client’s path

How a person moves through the product, from the first step to the result the business needs.

  1. The dispatcher sees everything

    Shipments with routes and current positions on one map.

  2. The team on the road

    Drivers and managers work from the mobile version.

  3. The client checks a trip

    The timeline from loading to delivery, in their own access.

  4. Statuses flow into the client’s system

    Through the API, with no calls to a manager.

04 · What is inside the project

  1. A cargo-tracking screen with map and live statuses

  2. Roles and permissions for the team and for clients

  3. A structure built to grow into a SaaS product

Forecast

Dispatchers check a trip status in minutes instead of calling drivers, and clients track shipments themselves, so “where is my cargo” calls roughly halve. A guideline, not a promise.

05 · Architecture

How the product is put together: from what the user sees to the data and services behind it.

  1. User Opens the site on a phone or a computer
  2. Interface What a person sees and taps
    • React
  3. Logic Rules, roles and scenarios
    • Node.js
  4. Data & integrations Where the data lives and what the product talks to
    • PostgreSQL
    • Mapbox

06 · How a project like this is built

Total: 16 weeks
  1. 01 ≈ 2 wk Brief & research Goals, audience, page structure and what the product must do
  2. 02 ≈ 5 wk UX/UI design Prototype, design of the key screens and the mobile version
  3. 03 ≈ 7 wk Development Front end, CMS, integrations and animation
  4. 04 ≈ 2 wk QA & launch Device testing, speed, SEO groundwork and launch

Typical phase split for a project of this size

07 · Services in this project

Next project Rutynik · 2024 Business process automation platform Automation / SaaS

Solutions for a specific job

Ready-made scenarios for your case — with examples and indicative pricing.

More projects

All projects →