Do couriers need to install a separate app?

In itlogist the field employee works through a mobile web interface — no mandatory app install. The courier opens a link, sees their list of orders and the route, and changes statuses as the work goes.

How do I confirm the fact of delivery, not the courier's word?

At each stop the courier attaches a photo report and marks the result in the app. The dispatcher sees the confirmation immediately, so a delivery is recorded as a fact, not a verbal message.

Where do orders come from in the system?

From your sources: website, CRM, ERP or an Excel export. From there they are assigned to field staff and laid out into routes.

How to track couriers without endless phone calls

Courier control does not rest on "where are you?" phone calls, but on the status of every order being visible in the system in real time. Let's look at what data you need to collect to see the whole field team's work, and how to move from calls to a transparent picture on a single screen.

Why calls and spreadsheets don't work

As long as control relies on phone calls and a spreadsheet, the dispatcher always has blind spots. Information becomes stale the moment it is written down: the courier said "on my way", but in reality got stuck or already left for the next address. The dispatcher spends the shift calling, the courier is distracted from delivering, and the manager has no objective data — only what the field staff say.

The problem is not people's discipline, but the lack of a single place where an order's status updates itself. Once that place appears, the need for manual control drops sharply.

What you need to see about a courier's work

For control to be complete rather than selective, a dispatcher needs just four layers of data:

Location on a map — where the courier is now and how they move along the route.
Order status — accepted, in transit, delivered, rescheduled, refused.
Proof of completion — a photo on site, a checklist, a signature or a code.
Deviations — lateness against a delivery window, stuck orders, missed stops.

This data should be updated by the field employee in the mobile app as the work happens, not entered by someone manually after the fact.

How to build a transparent process

A working control scheme looks like this:

orders enter the system from your sources (website, CRM, ERP, Excel) and are assigned to couriers;
the courier sees their list and route in the mobile interface and changes statuses as they go;
at each stop they attach a photo report and mark the result;
the dispatcher and manager see a live map and a status feed, and the system highlights deviations.

With this scheme control becomes passive: you don't have to call anyone — it's enough to watch the exceptions. That is exactly how the courier management loop in itlogist is built: orders, map routes, a mobile app with photo reports and real-time statuses.

What changes for the manager

When data is collected automatically, the manager gets what calls never gave: objective statistics. How many deliveries each courier made, how many were late against the window, where a route consistently slips. On these numbers you can build norms, incentives and shift planning — instead of arguing about who missed what and why.