Features

Everything between the invoice list and the signed delivery.

LogisticsOp is one system covering the whole delivery day, planning the routes, running them, proving what happened, and closing the books. Here is what each part actually does.

Planning the day

Upload the invoice list. Get routes.

Export the day's invoices from your ERP and drop the file in. LogisticsOp matches each line to a customer, groups them by salesperson, and hands each driver an ordered route.

Works with the ERP you already have

The upload reads a spreadsheet, so it works with Microsoft Dynamics 365 Business Central, SAP, Oracle, Odoo, Zoho, Tally, or anything that exports to Excel or CSV. Nothing changes in your ERP. Where a customer wants invoices to flow across automatically, we build a direct integration for their system.

AI route optimisation

Given a day's stops, the system measures the true driving distance between every pair across the road network, then works out the visiting order that covers them in the least driving. With twenty stops there are more possible orders than a dispatcher could ever compare by hand.

Salesperson to driver, once

Map each salesperson code to the driver who covers that territory and the assignment happens on every future upload without being asked again.

What the file needs

Posting dateThe invoice date
Invoice no.Your tracking key
Customer no.Matched to the stop
Customer nameShown to the driver
Salesperson codeDecides the driver
Amount incl. VATRoute value
Latitude, longitudeWhere the shop is
While the route runs

See where every vehicle is, and what it is doing.

Once drivers start, the map is the operations desk. Vehicles move in real time, and every stop shows its outcome as it happens.

Live vehicle positions

Each van on the map with its route trail, updating as it drives. A pulsing marker means the position is current; a still one means the driver has finished or stopped transmitting.

Stop detection

Where a vehicle stood still and for how long, whether or not it was a planned delivery. An unplanned twenty-minute stop shows up without anyone having to ask about it.

Reorder a running route

A customer calls and needs their delivery sooner. Move that stop up the order and the driver's phone updates immediately. Stops already completed stay where they are.

Add work mid-day

An urgent invoice arrives after the route has started. Add it, re-optimise only the stops the driver has left, and he carries on from where he is, no restart, no new odometer reading.

Cancellations and reschedules

When a shop is closed or an order refused, the driver records the reason on the spot. A reschedule creates the follow-up automatically for the agreed date, carrying the invoice number with it.

Distance that matches the odometer

Drivers photograph the odometer at the start and end of the route, so the recorded distance can be checked against the vehicle rather than taken on trust.

Proof of delivery

A photo proves something happened. GPS proves where.

When a customer says the delivery never arrived, a photograph alone rarely settles it. LogisticsOp records the driver's position at the moment the shopfront photo is taken and compares it with the customer's registered location.

At every stop

Shopfront photoCaptured on site
Invoice photoSigned copy
Position recordedAt the moment of the photo
Checked againstRegistered shop location
Matchedat the shop
Did not matchflagged for review

Settle disputes with evidence

Every delivery carries a photograph, a time, and a position. A query about last Tuesday is answered from the record rather than from memory.

Find the coordinates that are wrong

Shops whose saved location does not match where the driver actually delivered show up immediately. Fix them once at the source and every future route improves.

Only look at what needs looking at

Deliveries that matched are left alone. Only the ones that did not are surfaced, so nobody spends the morning opening photographs that were fine.

Closing the loop

Every invoice ends delivered or cancelled.

A reschedule is not an ending. LogisticsOp follows an invoice through every attempt until it reaches an outcome, and lists anything still open so it cannot quietly disappear.

The whole chain, under one number

An invoice attempted on Monday, rescheduled to Wednesday, then delivered on Friday is one record with three attempts, not three unrelated rows. Your invoice number stays attached the entire way.

Nothing falls through

Anything not yet delivered or cancelled appears on a single list, oldest first. Today's route is excluded, because work in progress is not a problem to solve.

Resolve it there and then

Mark it delivered if it was, cancel it with a reason if it will not be, or reschedule it properly, without leaving the list.

An invoice with three attempts

Attempt 1 · 12 AugShop closed
Attempt 2 · 15 AugRescheduled by customer
Attempt 3 · 18 Augdelivered
Reporting

Close the day in one click. Analyse it in your own tools.

Dashboards

Delivery rate, value delivered, distance driven and driver comparison, over any period. Click a figure to see the invoices behind it.

The daily closing file

One spreadsheet with every invoice, its outcome, the reason behind it, times, distance from the registered location, and coordinates.

A read-only API

Connect Power BI or Excel directly and refresh live. Same data, in your own dashboards, without exporting anything by hand.

Time at every stop

Travel time and time inside the shop measured separately, so a slow day can be explained rather than guessed at.

Access you control

Give a supervisor view-only access, or rights to particular actions, without handing over the admin account.

Your data stays yours

Each company runs on its own database, its own address, and its own photo storage. Nothing is shared between customers.

The driver app

Simple enough that drivers actually use it.

Complicated software gets abandoned in the cab. The app shows one stop at a time and asks for as little as possible.

A day in the app

  • Odometer reading and photo, once in the morning
  • The next stop, with a tap to navigate there
  • Two photos, then mark it delivered
  • A reason recorded when a delivery cannot be completed
  • Closing odometer, and the day is written up

Set up once

A driver enters the company code you give them, confirms the company name, and logs in. After that the app remembers, including through a logout.

Practical details

PlatformAndroid · iOS in development
Location recordedOnly while a route is active
Visible to the driverPersistent notification
Photos per stopShopfront and invoice
Training neededWorking within a day

See it running on your own routes.

A working walkthrough with your kind of delivery day, not slides.

Request a demo