Custom web development
Narva Kohvik Delivery
From the CRM to the courier’s phone.
The Narva Kohvik delivery solution connects the dispatcher’s work with courier actions. Orders, delivery times, responsibilities and handover details belong to one workflow.
- Solution
- Delivery management CRM and web app
- Users
- Dispatcher and courier
- GoMedia’s work
- Workflow, interface and development
- Technical complexity
- High
What needed to be solved?
Delivery planning needs to account for order contents, delivery time, address, courier availability and the amount still to collect from the customer. The dispatcher needs the full picture. The courier needs clear next actions on a phone.
A large order adds another condition: several couriers may deliver the same order. Each hands over a part, but the final completion and any outstanding delivery payment must happen only once.
The dispatcher’s CRM workspace
The day’s orders appear in one view. The dispatcher can compare times and addresses, select orders for a route and open details without leaving the list.
Design examples are shown in Estonian. All order, customer and payment details are illustrative. Interface images are design examples; they do not establish a production rollout.
Daily orders and route planning
The table brings together delivery time, order, address, courier, amount to collect and status. A date selector focuses the view on a particular day.
Order details in a side panel
Order contents, the delivery note and payment information open alongside the list. The need for several couriers is visible without searching the order list again.
Route map and calculation
These design examples show the selected stops on a map and a calculation for two couriers. Distances, arrival times and waiting times are illustrative; the calculation excludes current traffic.
Selected stops on the map
The map brings together three selected orders for the same day. The dotted line shows stop order, rather than a road route or the courier’s live location.
Route calculation for two couriers
The example separates each courier’s distance, driving time, total route duration, arrival and handover time. An early arrival includes waiting until the delivery window opens.
The courier web app on a phone
The courier view opens from a link in a mobile browser. The order brings together the delivery time, address, contents, call action and next step.
Swipe between views. Open any image to see it at full size.
Offered orders
In this example, the courier is offered three orders. They select two; the third returns to the dispatcher for reassignment.
My route
The phone shows the next order, its time window and the remaining stops. The courier can open the relevant order details directly.
Order handover
One view contains the address, delivery time, call and navigation actions, order contents and controls to record handover or a delivery problem.
One order, three couriers
An example of a large order delivered by three couriers. Another €5 needs to be collected from the customer. The amounts and details are fictional.
The first courier hands over their part
Their part is marked as handed over. The shared order stays open, and this courier does not collect the additional payment.
The second courier hands over their part
Two of the three parts have now been handed over. Final completion still requires the last courier’s confirmation.
The last courier completes the order
Once the other parts are handed over, the last courier can confirm their own part and record receipt of the €5. The order is completed once.
Swipe between views. Open any image to see it at full size.
Handing over one part
An earlier participant confirms their own part. The last courier collects any additional payment.
The final participant’s view
Two parts have been handed over. The final participant sees that they complete the shared order.
Additional payment and completion
The courier records how the money was received. The card option in this example means payment through an external terminal.
How is the solution built?
Two workspaces, shared orders
The dispatcher CRM and courier web app use the same order logic. A courier action is linked to a specific order and their participation in it.
An order and a courier’s part are separate
Completing one participant’s work does not automatically complete the whole order. The system distinguishes a courier’s handed-over part from the shared order’s final state.
The server checks completion rules
The server checks whether the other participants have finished and whether the order can be closed. A repeated confirmation must not create a second completion or additional payment record.
The courier works in a browser
The phone view is a web interface for a specific job. The courier opens a delivery link and sees the information needed for work. Downloading an app is not part of this workflow.
What makes it technically complex?
Complexity is high because several people can work on the same order at the same time. The system must distinguish partial handover, completion of the whole delivery and receipt of the additional payment.
Development must account for two couriers confirming almost simultaneously or a phone sending the same request again. Order status and payment information must stay consistent. These rules require server-side checks and handling of repeated operations.
What can the business do with it?
- Bring daily deliveries, deadlines and responsibilities into one CRM view.
- Give couriers the information they need directly on a phone.
- Arrange delivery of a large order by several couriers.
- Distinguish each participant’s handover from completion of the whole order.
- Link receipt of an additional payment to the final handover.