X Lojistik Product concept

Managing a fleet of 1,200 vehicles from one operations screen.

Route planning, live tracking and a driver app in one platform; the dispatcher sees delays before the recipient does.

X Lojistik product concept with sample data: an Istanbul live map with 1,248 active vehicles, 37 at-risk and 9 delayed trips; 46 exceptions ranked by risk on the right. In front, the driver's next stop is Y Gıda Kartal Warehouse; the lower-right card warns of an 18-minute delay risk for vehicle 34 XL 0001 and reports that an SMS was sent to the recipient.
The driver's daily routeFull screen ↗
Product concept: a solution study presented through screen designs, not an interactive demo. X Lojistik is fictional; screen data is illustrative.
Industry
Logistics & Transport
Capabilities
Product Strategy, Experience Design, Software Engineering
Platform
Web, iOS, Android

Problem and approach

Problem

In a large fleet, delays are often noticed only when the recipient calls.

Plans are prepared in Excel, changes are relayed to drivers by phone, and vehicle locations remain in separate systems. Delivery documents are signed on paper; no single screen shows the plan alongside field activity.

Approach

We launch this kind of platform in phases, not all at once.

In a two-week discovery sprint, we observe depots and drivers on site and test a prototype with actual users in week three. The jointly scoped first phase, such as live tracking and the driver app, targets a launch in 6–12 weeks; later phases such as route planning follow the roadmap.

Solution

One system from planning to proof of delivery.

The X Lojistik concept's Live Operations screen, with sample data: active vehicle, on-time delivery, at-risk trip and average delivery time indicators; vehicle clusters and depots on an Istanbul map; a card showing vehicle 34 XL 0001 reaching Y Gıda Kartal Warehouse 18 minutes late; a risk-ranked exception list on the right, with depots and driver app sync status on the left.
Tracking delayed tripsFull screen ↗
The live operations screen shows the next action, not everything: trips requiring intervention appear in the exception list on the right.
Two screens from the X Lojistik concept's driver app, with sample data. Left, Today's Route: 6 of 10 stops on trip XL-24817 are complete, 3 offline deliveries await sync, and the next stop is Y Gıda Kartal Warehouse. Right, Proof of Delivery: an electronic delivery note number, a 12-pallet count, two delivery photos, the warehouse manager's signature and a Confirm Delivery button.
Proof of deliveryFull screen ↗
Driver app: today's route and proof of delivery.
  1. Live operations map

    All vehicles on one map, colour-coded by delay risk. Trips needing intervention stand out.

  2. Automated route and load planning

    Delivery windows, capacity and breaks are calculated together. If a stop changes, the system suggests a new sequence.

  3. Offline driver app

    Electronic delivery note, photo and signature in one flow. Without a connection, the record waits on the phone.

  4. Automatic recipient notifications

    When the arrival time changes, recipients receive the new time and a tracking link by SMS or email.

Scenario and scope

Example users

Dispatcher, driver, warehouse manager and operations manager.

Example workflow

An order is added to the plan; the dispatcher assigns the trip, and the driver sends status updates and proof of delivery. The operations team intervenes when a delay risk arises.

Decisions for a real project

Define the vehicle tracking source, pilot fleet size, data stored offline, location permissions and notification channels. Assess separately whether route recommendations require rules or an optimisation model.

Related service: Custom software development and enterprise mobile application development. You can list your own users and systems in the project brief tool.

Timelines, teams and technologies in this scenario are illustrative planning choices; actual scope, schedule and team are defined during discovery. Product names do not imply partnerships.

What we measure

%15Target: reduction in average delivery time
%10Target: reduction in fuel consumption per vehicle
%90Target: proportion of delays identified before the recipient notices
1Target: number of screens the dispatcher uses to monitor the entire fleet

These targets are example measures defined for this scenario; actual results vary by project.

Technology and team

Technology

  • React
  • TypeScript
  • Go
  • PostgreSQL + PostGIS
  • Kafka
  • React Native
  • AWS

For scope, offline operation and delivery terms for driver and field-team apps, see the enterprise mobile application development page.

Suggested team 7 people

  • 1 product strategist
  • 1 product designer
  • 4 software engineer (web, mobile, backend)
  • 1 QA engineer

Your process

Do you manage a similar operation? Let's schedule a 30-minute conversation about bringing fleet planning and live tracking into one view.

Let's discuss this concept

This is an example, not a limit; we apply the same approach to similar processes in other industries.