---
metadata:
  - name: generator
    content: Diplodoc Platform v5.19.6
alternate:
  - https://docs.routeq.com/doc/en/vrp/interface-import.md
  - https://docs.routeq.com/doc/tr/vrp/interface-import.md
title: RouteQ — working with the interface —  import window
---
> **Documentation Index:** Fetch the complete configuration index at https://docs.routeq.com/doc/en/llms.txt


# Import window

## Steps {#import-steps}

### Step 1. Enter the data {#step-1}

On the **Planning** tab, choose one of the options:

- Click the **Upload file** button or drag the document into the window to upload the data that you prepared in an Excel file.
- Click the **Start planning** button to enter the data directly on the interface tabs. Before you start planning a task, you can switch between tabs and make changes.

### Step 2. Fix the errors and check the warnings {#step-2}

Next to the tab names, you can see the icons reflecting the status of the uploaded data: If the system detects errors in the source data, information about this appears in the list of comments next to the table. Click on the message in the list to highlight the problem cell.

<svg width="18px" height="18px" viewBox="0 0 18 18" version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink"><g id="rnd-5ed9939__Symbols" stroke="none" stroke-width="1" fill="none" fill-rule="evenodd"><g id="rnd-5ed9939__sidebar-OK" transform="translate(-221.000000, -267.000000)" fill="#27A72B" fill-rule="nonzero"><g id="rnd-5ed9939__tabs" transform="translate(0.000000, 100.000000)"><g id="rnd-5ed9939__orders" transform="translate(0.000000, 140.000000)"><path d="M230,27 C234.970563,27 239,31.0294373 239,36 C239,40.9705627 234.970563,45 230,45 C225.029437,45 221,40.9705627 221,36 C221,31.0294373 225.029437,27 230,27 Z M234.789991,32.2134487 L227.712243,39.4378669 L225.210009,36.8837797 C224.931189,36.5991814 224.487936,36.5991814 224.209115,36.8837797 C223.930295,37.168378 223.930295,37.6208163 224.209115,37.9054146 L227.204647,40.9630219 C227.483467,41.2476202 227.93387,41.2476202 228.21269,40.9630219 L235.790885,33.2350836 C236.069705,32.9504853 236.069705,32.498047 235.790885,32.2134487 C235.512064,31.9288504 235.068811,31.9288504 234.789991,32.2134487 Z" id="rnd-5ed9939__icon"/></g></g></g></g></svg>: The data is correct.

<svg width="20" height="20" viewBox="0 0 20 20" fill="none" xmlns="http://www.w3.org/2000/svg"><path d="M10 0C4.48 0 0 4.48 0 10C0 15.52 4.48 20 10 20C15.52 20 20 15.52 20 10C20 4.48 15.52 0 10 0ZM10 11C9.45 11 9 10.55 9 10V6C9 5.45 9.45 5 10 5C10.55 5 11 5.45 11 6V10C11 10.55 10.55 11 10 11ZM11 15H9V13H11V15Z" fill="#FF0000"/></svg>: You have errors that must be resolved before planning.

<svg width="20px" height="18px" viewBox="0 0 20 18" version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink"><g id="rnd-c44264a__Symbols" stroke="none" stroke-width="1" fill="none" fill-rule="evenodd"><g id="rnd-c44264a__issues-warnings" transform="translate(-208.000000, -118.000000)" fill-rule="nonzero"><g id="rnd-c44264a__issue" transform="translate(0.000000, 94.000000)"><g id="rnd-c44264a__icon" transform="translate(208.000000, 24.000000)"><rect id="rnd-c44264a__Rectangle" fill="#FFFFFF" x="7.5313712" y="5.0075" width="4" height="10"/><path d="M2.0013712,17.0075 L17.0613712,17.0075 C18.6013712,17.0075 19.5613712,15.3375 18.7913712,14.0075 L11.2613712,0.9975 C10.4913712,-0.3325 8.5713712,-0.3325 7.8013712,0.9975 L0.271371202,14.0075 C-0.498628798,15.3375 0.461371202,17.0075 2.0013712,17.0075 Z M9.5313712,10.0075 C8.9813712,10.0075 8.5313712,9.5575 8.5313712,9.0075 L8.5313712,7.0075 C8.5313712,6.4575 8.9813712,6.0075 9.5313712,6.0075 C10.0813712,6.0075 10.5313712,6.4575 10.5313712,7.0075 L10.5313712,9.0075 C10.5313712,9.5575 10.0813712,10.0075 9.5313712,10.0075 Z M10.5313712,14.0075 L8.5313712,14.0075 L8.5313712,12.0075 L10.5313712,12.0075 L10.5313712,14.0075 Z" id="rnd-c44264a__Shape" fill="#FFCC00"/></g></g></g></g></svg>: You have warnings but can still run Planning.

### Step 3. Define the optimization settings {#step-3}

Set the appropriate settings for the current planning task.

#|
|| **Name** | **Description** ||
|| **Time zone** | The time zone used for all the time windows. ||
|| **Consider geofences** | Choose **Yes** to automatically match orders with geofences from the [Geofence master data](https://docs.routeq.com/doc/en/vrp/interface-geozones.md) based on their coordinates. The planning will take into account geofence [restrictions](https://docs.routeq.com/doc/en/vrp/properties-of-vehicles.md#geozones). Choose **No** to ignore geofences. ||
|| **Solution quality** | Sets the [quality of the solution](https://docs.routeq.com/doc/en/vrp/options-quality.md). The **Fast** option is good for quickly checking the solution for errors. **Optimal** is best for planning a real route. ||
|#

### Step 4. Run the planning {#step-4}

On the **Settings** tab, click the **Plan** button. The button is enabled if there are no errors in the data.

When the task solution is ready, the [planning result](https://docs.routeq.com/doc/en/vrp/interface-result.md) opens. You can view and edit it.

## Managing data in the interface {#interface-managment}

### Adding data {#add}

In the **Download template** list, you can find the files with filled-in data to use for the test planning (see also the [Planning example](https://docs.routeq.com/doc/en/vrp/example.md) section).

To add data:

- Copy data from Excel by clicking **Upload file**.
- Extend the contents of one cell in a range by dragging the selection frame over a column.

### Editing data {#edit}

- Edit cell values by double-clicking the left mouse button.
- Delete, insert, and copy rows using the context menu available on right-click in a row.

### Sorting {#sort}

To sort data by column:

1. Right-click any table cell and choose **Sort table**.
1. Click the column name.

## Filling in the tabs {#tabs}

#|
|| **Tab** | **Explanation** | **Visible by default** | **Instruction for Excel** ||
|| Orders | Add information about delivery points, order pickup, start or end route points.
Required fields:
- Order ID.
- Recipient's address or coordinates.
- Window. | <svg xmlns="http://www.w3.org/2000/svg" version="1.1" viewBox="0.00 0.00 16.00 13.00" width="16.00" height="13.00"><path fill="#fece06" d="   M 14.06 0.00   L 16.00 0.00   L 16.00 1.81   L 6.69 13.00   L 4.94 13.00   L 0.00 7.44   L 0.00 5.94   C 2.21 3.92 4.10 7.71 5.56 9.07   Q 5.97 9.45 6.33 9.02   L 14.06 0.00   Z"/></svg> | [Orders sheet](https://docs.routeq.com/doc/en/vrp/excel-fill-guide.md#orders) ||
|| Depots | Add information about depot location and working hours, as well as details about route start and end points.
Required fields:
- Depot ID.
- Depot address or coordinates.
- Depot working hours. | <svg xmlns="http://www.w3.org/2000/svg" version="1.1" viewBox="0.00 0.00 16.00 13.00" width="16.00" height="13.00"><path fill="#fece06" d="   M 14.06 0.00   L 16.00 0.00   L 16.00 1.81   L 6.69 13.00   L 4.94 13.00   L 0.00 7.44   L 0.00 5.94   C 2.21 3.92 4.10 7.71 5.56 9.07   Q 5.97 9.45 6.33 9.02   L 14.06 0.00   Z"/></svg> | [Depot sheet](https://docs.routeq.com/doc/en/vrp/excel-fill-guide.md#depot-depots) ||
|| Map | The tab shows the map and a list of delivery addresses. To learn more, see the [Map](https://docs.routeq.com/doc/en/vrp/interface-import.md#map) section. | <svg xmlns="http://www.w3.org/2000/svg" version="1.1" viewBox="0.00 0.00 16.00 13.00" width="16.00" height="13.00"><path fill="#fece06" d="   M 14.06 0.00   L 16.00 0.00   L 16.00 1.81   L 6.69 13.00   L 4.94 13.00   L 0.00 7.44   L 0.00 5.94   C 2.21 3.92 4.10 7.71 5.56 9.07   Q 5.97 9.45 6.33 9.02   L 14.06 0.00   Z"/></svg> | None. It can only be filled out in the interface ||
|| Vehicle | Add information about company vehicles, their dimensions, and shift duration. To use vehicles previously added to [Master data](https://docs.routeq.com/doc/en/vrp/interface-transport.md) in planning, disable the **Transport from an Excel file** option.
The required field is the vehicle ID. | <svg xmlns="http://www.w3.org/2000/svg" version="1.1" viewBox="0.00 0.00 16.00 13.00" width="16.00" height="13.00"><path fill="#fece06" d="   M 14.06 0.00   L 16.00 0.00   L 16.00 1.81   L 6.69 13.00   L 4.94 13.00   L 0.00 7.44   L 0.00 5.94   C 2.21 3.92 4.10 7.71 5.56 9.07   Q 5.97 9.45 6.33 9.02   L 14.06 0.00   Z"/></svg> | [Vehicles sheet](https://docs.routeq.com/doc/en/vrp/excel-fill-guide.md#vehicles) ||
|| Incompatible | Add information about cargo types and their incompatibility with one another. | <svg xmlns="http://www.w3.org/2000/svg" version="1.1" viewBox="0.00 0.00 16.00 16.00" width="16.00" height="16.00"><path fill="#ababab" d="   M 0.00 0.00   L 2.81 0.00   L 7.71 4.94   Q 8.15 5.39 8.56 4.90   Q 10.95 2.03 14.06 0.00   L 16.00 0.00   L 16.00 2.56   L 11.03 7.70   Q 10.64 8.12 11.04 8.52   L 16.00 13.56   L 16.00 16.00   L 13.44 16.00   L 8.46 11.21   Q 8.00 10.76 7.52 11.20   L 2.44 16.00   L 0.00 16.00   L 0.00 13.94   L 4.95 8.44   Q 5.33 8.02 4.94 7.62   L 0.00 2.44   L 0.00 0.00   Z"/></svg> | [Incompatible order types sheet](https://docs.routeq.com/doc/en/vrp/excel-fill-guide.md#incompatible-order-types) ||
|| Groups | Add information about orders that need to be delivered by one courier.
Location IDs is a required field. | <svg xmlns="http://www.w3.org/2000/svg" version="1.1" viewBox="0.00 0.00 16.00 16.00" width="16.00" height="16.00"><path fill="#ababab" d="   M 0.00 0.00   L 2.81 0.00   L 7.71 4.94   Q 8.15 5.39 8.56 4.90   Q 10.95 2.03 14.06 0.00   L 16.00 0.00   L 16.00 2.56   L 11.03 7.70   Q 10.64 8.12 11.04 8.52   L 16.00 13.56   L 16.00 16.00   L 13.44 16.00   L 8.46 11.21   Q 8.00 10.76 7.52 11.20   L 2.44 16.00   L 0.00 16.00   L 0.00 13.94   L 4.95 8.44   Q 5.33 8.02 4.94 7.62   L 0.00 2.44   L 0.00 0.00   Z"/></svg> | [Location groups sheet](https://docs.routeq.com/doc/en/vrp/excel-fill-guide.md#location-groups) ||
|| Adv. settings | Fill in the list of routing options. | <svg xmlns="http://www.w3.org/2000/svg" version="1.1" viewBox="0.00 0.00 16.00 16.00" width="16.00" height="16.00"><path fill="#ababab" d="   M 0.00 0.00   L 2.81 0.00   L 7.71 4.94   Q 8.15 5.39 8.56 4.90   Q 10.95 2.03 14.06 0.00   L 16.00 0.00   L 16.00 2.56   L 11.03 7.70   Q 10.64 8.12 11.04 8.52   L 16.00 13.56   L 16.00 16.00   L 13.44 16.00   L 8.46 11.21   Q 8.00 10.76 7.52 11.20   L 2.44 16.00   L 0.00 16.00   L 0.00 13.94   L 4.95 8.44   Q 5.33 8.02 4.94 7.62   L 0.00 2.44   L 0.00 0.00   Z"/></svg> | [Options sheet](https://docs.routeq.com/doc/en/vrp/excel-fill-guide.md#options) ||
|| Routes | Add information about predefined routes.
Required fields:
- Vehicle ID.
- Shift number.
- Location ID. | <svg xmlns="http://www.w3.org/2000/svg" version="1.1" viewBox="0.00 0.00 16.00 16.00" width="16.00" height="16.00"><path fill="#ababab" d="   M 0.00 0.00   L 2.81 0.00   L 7.71 4.94   Q 8.15 5.39 8.56 4.90   Q 10.95 2.03 14.06 0.00   L 16.00 0.00   L 16.00 2.56   L 11.03 7.70   Q 10.64 8.12 11.04 8.52   L 16.00 13.56   L 16.00 16.00   L 13.44 16.00   L 8.46 11.21   Q 8.00 10.76 7.52 11.20   L 2.44 16.00   L 0.00 16.00   L 0.00 13.94   L 4.95 8.44   Q 5.33 8.02 4.94 7.62   L 0.00 2.44   L 0.00 0.00   Z"/></svg> | [Routes sheet](https://docs.routeq.com/doc/en/vrp/excel-fill-guide.md#routes) ||
|| Settings | Specify additional route parameters, such as date, time zone, and transportation method. To learn more, see [Settings](https://docs.routeq.com/doc/en/vrp/interface-import.md#step-3). | <svg xmlns="http://www.w3.org/2000/svg" version="1.1" viewBox="0.00 0.00 16.00 13.00" width="16.00" height="13.00"><path fill="#fece06" d="   M 14.06 0.00   L 16.00 0.00   L 16.00 1.81   L 6.69 13.00   L 4.94 13.00   L 0.00 7.44   L 0.00 5.94   C 2.21 3.92 4.10 7.71 5.56 9.07   Q 5.97 9.45 6.33 9.02   L 14.06 0.00   Z"/></svg> | None. It can only be filled out in the interface ||
|#


### Map {#map}

The tab contains:

- The map.
- A list of order or depot addresses.
- A link for downloading geocoded data in Excel format.

![](./_images/planing-map-close.png)

Here you can run addresses through the Geocoder to get their latitude and longitude. Geocoding can be started automatically or manually.

Geocoding only works for uploading orders and depots from Excel files. When using the API, you need to pass point coordinates rather than addresses. This means that you must geocode in advance on the side of the integrated system.

There are two types of geocoding:

- [Automatic](#auto-geocoding): By default, it starts after you upload an Excel file.
- [Manual](#manual-geocoding): Used for assigning coordinates to a point on your own.

#### Automatic geocoding {#auto-geocoding}

{% note alert %}

To start geocoding, fill in the `address` box (write the recipient's address) for **every order** on the `Orders` sheet.

{% endnote %}

Automatic geocoding starts immediately after you upload the data file to the interface. But if the file has a lot of addresses without coordinates, you may need to click **Find coordinates** to start geocoding.

If the recipient's address indicates the apartment number, automatic geocoding determines the coordinates of the building entrance where the courier has to arrive. Entrance coordinate data isn't available for all addresses yet, but the database is constantly being updated.

To get more accurate results, enable the **Search in the map's viewport** option. It's useful if:

- The address is incomplete. For example, the city isn't specified.
- You need to set non-standard borders for address search.
- You need to split geocoding into several steps, changing the scope at different iterations.

**How to break down geocoding into steps**

1. Stop geocoding by clicking **Stop**.
1. Enable the **Search in the map's viewport** option.
1. Move the map's viewport to the necessary position.
1. Set the scale.
1. Click **Search by address** again.

#### Automatic geocoding results {#auto-geocoding-result}

When geocoding is completed, the following address groups appear to the left of the map: **With coordinates**, **Without coordinates**, and **Approximation**. There can be one or more groups.

Addresses are divided into groups depending on how correct the source data is in the uploaded file. All found addresses are marked on the map using color labels.

#|
|| **Placemark color** | **Group** | **Property** | **Example** ||
|| ![](./_images/geo-green.png) | With coordinates | The address is written in the correct format and without errors. | Moscow, Pyatnitskoe highway, 23k2 ||
|| ![](./_images/geo-yellow.png) | Approximation | The address is written incorrectly. | 26Bc2, Moscow, Bolshaya Pochtovaya street ||
|| | | The address is written with errors or contains information that isn't related to the address. | Moscow region, Bhgrrkha, Tereshkova street, 13 ||
|| | | The address doesn't specify the city (different cities may have the same street names). | Okruzhnaya street, 8 ||
|| | | The address in text format (the `address` field) and coordinates (the `point.lat` and `point.lon` fields) don't match. | 22.0 and 33.1, Moscow, Vysokovoltny passage, 1s36 ||
|| | | The building was not found (but the system found a building with a number that's close to the one in question, or only the street). | Moscow, Bolshaya Pochtovaya Street, 5559<br> 
or<br> 
Moscow, Bolshaya Pochtovaya Street, 55/59 ||
|| ![](./_images/geo-red.png) | Without coordinates | The address field isn't filled in. | Empty ||
|| | | The street wasn't found, and only the coordinates of the city center are returned. | Moscow, Ulichnaya street, 8 ||
|#

You need to manually check whether the addresses in the **Approximation** group have the correct coordinates.

You may also need to check the addresses in the **With coordinates** group. For example, there may be a typo in the coordinates box. In that case, the order location will be thousands of kilometers from the main group of orders. To find such an error, you need to zoom out on the map a lot.

#### Automatic geocoding features {#auto-geocoding-specifics}

The default search area covers ±1 degree from the depot coordinates.

The geocoder may determine the order coordinates incorrectly if the address is set inaccurately (for example, without specifying the city), and there is the same street and building number in a neighboring locality. To avoid this, choose the scale and location on the map to display the desired point.

The map parameters are stored locally for the company and used for the next planning. To make geocoding more accurate, enable the **Search in the map's viewport** option.

#### Manual geocoding {#manual-geocoding}

To assign coordinates to a point manually:

1. Click the address in the list next to the map.

2.  A window and (for the **Approximation** and **With coordinates** groups) a pin that marks the order address appear on the map. There are two ways to edit the address:

    - **Dialog window**. In the dialog window that appears, start entering or editing the address, then select the appropriate option in the drop-down list.

    - **Pin**. Click the pin and drag it to the correct location on the map. The address in the window changes. Switch layers, if you need to get a better view of the area.

    ![](./_images/one-pin.png)

3. The pin and address in the list are marked green.

4. Click **Continue** to go to the next address in your list.


#### Save the results {#geocoding-save-results}

To save the geocoding result to a file, click **Download geocoded addresses as an Excel file**. In the downloaded file, every order address has the exact coordinates based on the results of automatic and manual geocoding. You can use them for further planning.

If any orders are left without coordinates as a result of planning, you can save them and exclude them from planning. To do this, click ![](./_images/download-result.png) → **Download orders without coordinates and remove them from planning**.

{% include [warehouse-feedback](_includes/feedback-81845556eeea.md) %}
