Planowanie tras dostaw w ERPNext
ERPNext Logistics

Delivery routes planned without sheets, telephones and guessing

Based on WZ documents, customer data and Google Maps API, we create ready-made Delivery Trips in ERPNext: with the order of points, estimated travel times, a list of tasks for the driver and automatic communication to recipients.

Ask about logistics in ERPNext See how it works

From the WZ document to the ready route for the driver

In many companies, logistics starts only when the warehouse issues the WZ. Someone writes down the addresses, arranges the order on the sheet, calls the driver, and then answers customers' questions: "When will the delivery be?"

ERPNext allows you to turn this process into one controlled flow. WZ documents indicate what is to go to and to whom. Delivery Trip groups deliveries into a specific route. Google Maps API helps you calculate distances, times and the real order of travel. The driver receives the route on his phone, and the customer can receive e-mail, SMS or WhatsApp notifications.

Delivery Trip TR-2026-014
  1. 01
    Central WarehouseStart: 07:30
  2. 02
    Client: Nowa 14ETA: 08:05, WZ-1042
  3. 03
    Client: Polna 8ETA: 08:45, WZ-1045
  4. 04
    Client: Fabryczna 21ETA: 09:30, WZ-1049

How does Delivery Trip work in ERPNext

1

The WZ turns into a delivery point

The system collects data from the WZ documents: recipient, address, contact, goods items, delivery date and notes for the driver. There is no need to manually copy the customer list to a separate file.

2

Delivery Trip groups the trip

The dispatcher selects the driver, vehicle, starting warehouse and documents to be handled. Delivery Trip becomes one route card: with a list of stops, documents, statuses and responsibilities.

3

Google Maps API calculates the route

Customer addresses can be geocoded and the system can download distances and travel times. Thanks to this, the delivery plan is based on real road data, and not only on the intuition of the person planning the route.

4

The driver works from the phone

The list of points is available on mobile. The driver sees the order, addresses, recipients' telephone numbers and documents, and after completion, he marks the point as completed. The office immediately sees the progress of the route.

What the company gains

Less manual planning

WZ, addresses and contacts are already in ERP. The route is created from data that is needed for sales, storage and delivery of goods anyway.

Better order of deliveries

Integration with Google Maps API helps organize points by distance, time and reasonable route.

Full status control

The dispatcher can see which deliveries are planned, en route, completed or require response. Without calling the driver every few minutes.

Fewer questions from customers

Automatic notifications can provide the recipient with information about the planned delivery, estimated time and contact details of the driver.

One process from warehouse to customer

Sales, warehouse, delivery note, transport and communication work on the same data. This reduces errors and speeds up complaint handling.

Readiness for further automation

The same logic can be used to build a pickup signature, delivery photos, driver billing or integration with an external TMS.

Notifications for customers, recipients and drivers

The route does not end with generating a list of points. The biggest difference occurs when the system itself sends messages to the right people.

  • email to the customer with information about the scheduled delivery
  • SMS with the expected delivery time window
  • WhatsApp with a link to route information or contact information to the driver
  • notification to the driver about the new route and changes in the schedule
  • message after the delivery point has been reached or in case of a problem on the route

We select communication channels to suit the company's process. In a simple variant, e-mail is enough. In a more operational implementation, we can add SMS and WhatsApp so that delivery recipients get information where they actually read it.

Route today

Driver: Jan K.

WZ-1042 Delivered, 08:07
WZ-1045 Next point, ETA 08:45
WZ-1049 In queue, ETA 09:30

Mobile driver access

The driver does not need a separate sheet or a printed list that becomes invalid after the first change. Opens the route on the phone and works with current data from ERPNext.

List of points

Further addresses, planned times, WZ numbers, contact details of the recipient and unloading comments in one place.

Customer navigation

The delivery point can lead directly to a map on the phone, with the address taken from the customer's file.

Fulfillment status

After delivery, the driver marks the point as completed. The office sees the progress without asking the driver by phone.

Problem response

An absent consignee, no unloading space or a change in order can be noted at a specific route point.

Who is this function for

It is best suited if:

  • you issue WZ documents and organize your own deliveries
  • you have several or a dozen recipients per car per day
  • the dispatcher arranges the routes manually in a spreadsheet or maps
  • customers often ask about the delivery time
  • you want to see the delivery status without constant contact with the driver

What you need to prepare:

  • ordered addresses of customers and delivery places
  • process issuing a WZ in ERPNext
  • list of drivers, vehicles and starting warehouses
  • Google Maps API key and rules for using map data
  • consent and content of messages for e-mail, SMS or WhatsApp

You want to show the driver a ready route instead of sending him a list addresses?

Describe how WZ is created today, who arranges routes and how drivers confirm deliveries. We will prepare the scope of logistics implementation in ERPNext: from simple Delivery Trip to integration with Google Maps API, SMS and WhatsApp.

Let's talk about delivery routes