Customer order tracking: how to show delivery status and take the load off dispatch

Why it pays to open up delivery progress

As long as the recipient can see nothing, they invent their own version of events. After an hour of waiting the anxiety starts; after two comes the phone call. The dispatcher is pulled away from planning, has to chase the courier, call back — and the same handful of facts get repeated out loud dozens of times a shift. Transparency removes that work entirely: the person opens a page and answers the question themselves.

The second effect is fewer failed visits. When the recipient knows in advance that someone will arrive within the half hour, they do not pop out to the shops or disappear into a meeting. Not being ready to accept the goods is one of the most common reasons for a reschedule, and the cure is timely information rather than more phone calls.

The third effect is less obvious but matters most to the operations team: opening up progress imposes discipline on internal processes. The moment an outsider can see the statuses, it becomes impossible to close jobs retroactively or leave stale marks sitting in the system. Data the client looks at is forced to be accurate — and accurate data is something you can finally build your own analytics on.

Finally, there is the matter of expectations. People are used to watching progress unfold on marketplaces and in ride-hailing apps, and they carry that habit over to every delivery and every field service visit. Not offering it no longer reads as a missing feature; it reads as a company with something to hide.

Which statuses the recipient actually needs

The temptation to expose every internal step is strong, but too much detail backfires: the longer the chain, the harder it is to work out what is happening right now. A short sequence of plain-language states is the working minimum.

• Accepted — the job is registered, the address and date are known.
• Courier assigned — a specific person is responsible and a time window has been set.
• On the way — the courier has set off and the recipient has an estimate for arrival.
• Completed — the job is closed with confirmation attached: photo, checklist, signature.
• Not completed — the visit did not happen, with the reason given and the next step spelled out: reschedule, second attempt or return.

That last state is the one most often left out, and it is the critical one. Silence after a failed visit generates far more ill will than the reschedule itself, because the recipient has no idea whether to keep waiting today or give up. An honest entry with a reason and a new date settles the question before it turns into a complaint.

Wording matters more than the count. Internal jargon along the lines of "in processing with logistics" tells an outsider nothing. Each state should be rewritten to answer two questions: what has already happened, and what to expect next. Think through field service and distribution separately — there, the gap between "assigned" and "completed" can involve a long stretch of work on site, and that deserves a state of its own.

Where to show progress: portal, link, notifications

There are three ways to get the information across, and they complement each other rather than compete.

A client portal. This suits B2B work and regular partners: the account holder sees all their jobs at once, along with history, documents and confirmations. It is a working tool people log into routinely, so detail and an archive of past periods both belong here.

A link to a single delivery. This is the format for one-off recipients: a short address arrives by message, opens without registration and shows the state of one job. The barrier to entry is zero, which is exactly why the calls stop — asking someone to create an account for the sake of one parcel is pointless.

Push notifications. The most valuable piece is not the page but the message that arrives on its own the moment something changes: a window has been set, the courier has left, the job is closed, the visit has been moved. The rule is simple — notify about events that call for a reaction from the recipient and stay quiet about the rest. A stream of messages covering every internal step is irritating and gets muted fast.

Which combination you choose depends on the audience. Business accounts want a portal, private recipients want a link and a couple of messages, and a mixed flow needs both at once.

Where the tracking data comes from

Tracking is a shop window. It is useful exactly to the extent that the data behind it is accurate, and that accuracy rests on three sources.

The courier in the field. This is the main supplier of facts: they log departure, arrival and completion, attach a photo report and checklist, and record the reason when a visit falls through. The key requirement is that logging takes seconds and happens on the spot rather than from memory in the evening. A mobile web interface for couriers works without forcing anyone to install an app, which noticeably simplifies onboarding for contractors and new hires.

The dispatcher and the plan. Some states are born in the office: accepting the job, distributing it among couriers, setting a time window, moving it to another date. This is also where the arrival estimate comes from — drawn from the planned route rather than a rough promise, and updated when the day drifts from the plan.

The system of record. Jobs usually originate somewhere other than the delivery system: their source is accounting software or a CRM. If the data is carried across by hand, discrepancies are inevitable and the client is shown yesterday's picture. An exchange with 1C, AmoCRM, Bitrix24 and Excel closes that gap.

In itlogist these three streams are brought together in a single loop: intake and distribution of jobs, routes on a live map, courier check-ins with on-site confirmation of completed work, and a client portal showing the current state — Courier management. The client is not looking at a separate feed somebody maintains by hand, but at a direct reflection of what is happening in operations.

Mistakes that stop tracking from working

A status page on its own solves nothing. These are the usual culprits:

• Backdated check-ins. The courier closes every stop in one batch at the end of the day, so the page shows "on the way" for parcels handed over hours ago and loses all credibility.
• An over-long chain. A dozen internal states instead of five clear ones, leaving the reader unable to tell what is happening at this moment.
• Silence when things go wrong. Messages arrive while everything runs to plan, then the system goes quiet the instant a visit falls through — precisely when the information is needed most.
• Promising an exact time with no slack. If the arrival estimate is calculated down to the minute, every traffic jam becomes a visible delay. A window is more honest than a precise time.
• No link to the source of jobs. The order was cancelled or moved in the system of record, but in tracking it carries on as if nothing happened.
• No way to reply. The recipient can see the courier is on the way but cannot say "I will only be back after six" — so they call, which is the very thing tracking was meant to prevent.

All of these share one common denominator: a gap between what is shown on the outside and what is actually going on. It closes through discipline in the field and a link to the source of jobs, not through better copy on the page.

How to launch tracking in a few steps

It makes sense to work from the process towards the shop window, not the other way round.

• Define the states. Five or six plain-language entries, always including a state for a failed visit along with a list of reasons.
• Get check-ins in order. While couriers are still logging events after the fact, it is too early to show any of it to an outsider.
• Connect the source of jobs. A job should reach the delivery system automatically and return its result to the system of record just as automatically.
• Pick the channel to match the audience. A portal for business accounts, a link and messages for one-off recipients.
• Set up event-based messages. Window set, courier on the way, job closed, visit moved — and nothing beyond that.
• Measure the result. The number of "where is my order" enquiries, the share of wasted trips and the share of jobs closed on time are the three metrics that show whether transparency paid for itself.

Getting started with itlogist takes 7 days and requires no long-term contract, and the platform is built for teams of 5 to 100 couriers — so you can test the effect of open progress on a real flow of jobs rather than in theory. Start with a single segment: one city, one service type or one group of accounts. Gather figures on the three metrics above, and only then extend the practice to the rest of the flow.