Search the documentation

Find a page by title or section.

Go to dashboard
Locations

Destinations

The places you deliver to, stored once and reused by every trip that stops there.

Updated

A destination is a place goods go to. You record it once — address, coordinates, contact, opening hours — and every trip that stops there points at the same record, so a corrected pin or a new phone number reaches all future work without touching a single trip.

Who can do this

Role
Administrators
Permission
destinations:readdestinations:writedestinations:delete

Drivers also hold destinations:read, which is what lets the driver app and portal show the place they are heading to. Creating, editing and deleting are admin actions.

Terminology

Your organisation can rename these. If your screens say something else, this is what they mean here.

Destination
A place goods are delivered to. Some tenants rename these sites, clients, customers or drop points.Rename it in Customization → Terminology
Origin
A place goods are collected from. The separate record type described on the Origins page.Rename it in Customization → Terminology

A destination is not an origin

The two look alike on screen — both are named places with an address, a type, a contact and coordinates — but they are separate record types with separate lists, separate permissions and separate fields. Pick by direction of travel: goods leave an origin and arrive at a destination. If you are describing a warehouse you collect from, you want Origins.

DestinationOrigin
DirectionGoods arrive hereGoods leave here
Delivery windowWindow open and window closeNot held on the record
Pickup fieldsNonePickup instructions, average prep time
Assigned driversYes, many per destinationNo
Default tasksYes, copied onto every stopNo
Detail pageYes, with visit historyNo, editing opens the form
Map viewYes, clusteredNo
Auto-created recordsNeverYes, from a driver GPS fix
What each record type carries that the other does not.

Create a destination

The form is one modal split into sections. Only four fields are required; the rest earn their keep later.

  1. 1

    Open the form

    Destinations → Add Destination

    The sidebar entry carries your own word for these — if you renamed them, look for that instead.

  2. 2

    Name it and pick a type

    Name is required and capped at 200 characters. Type is required too, but it arrives pre-selected with the first type your organisation has configured, so you can leave it alone.

  3. 3

    Place it on the map

    The location picker offers three modes — Search, Map and Manual. Choosing a search result also fills in the city, state, postal code and country below.

  4. 4

    Complete the address

    Address Line 1, City and Country are required. Everything else is optional.

  5. 5

    Add a contact and a delivery window

    Contact name, phone and email appear on the destination overview as a click-to-call and click-to-mail block. Operating hours are free text; the Window Open and Window Close times are structured.

  6. 6

    Assign drivers, if you work that way

    Linking drivers to a destination lets you filter the list by who covers what. Editing later replaces the whole set: whatever is in the field on save becomes the complete list of active assignments.

Types are your vocabulary, not ours

The type list is configured per organisation, not fixed by the product. Out of the box it is Warehouse, Restaurant, Store, Hub and Other; you can replace that list entirely with whatever your operation actually distinguishes between. Edit it under Customization → Entity Types, which also owns trip, stop and origin types.

Finding the ones you need

Search matches name, city and address. Beyond that the toolbar filters on:

  • Status — active or inactive.
  • Type — drawn from your configured list.
  • Not visited — never, or not in the last 30, 60 or 90 days.
  • Visited — a date range, or a last 7 / 30 / 90 days preset.
  • Assigned drivers — one or more, matching any of them.
  • Your own custom fields, through the toolbar’s conditions mode.

Quick views sit above the filters as one-click starting points: Active, Never visited, Gone quiet, Visited this week, and All.

What the record accumulates

Opening a destination gives you seven tabs: Overview, Visits, Tasks, Proof, Map, Drivers and Exceptions. The list itself carries a Last Visited column that reads Never in full until a trip stop there is actually served — which is usually the fastest way to spot addresses that were imported and then forgotten.

The Tasks tab holds the destination’s default tasks: a blueprint copied onto every stop created at this destination, so "photograph the pallet, get a signature" is configured once rather than per trip.

Loading a lot of them at once

Import accepts CSV, XLSX or JSON, up to 500 rows per file. A row whose name matches an existing destination updates it rather than creating a duplicate, and empty optional cells leave the current values alone. The downloadable template already contains your custom-field columns; assign drivers by putting their email addresses in the driver_emails column, separated by semicolons. See Imports for the full process.