Skip to main content
This guide walks Nash Portal admins through running deliveries with their own drivers. You will learn how to configure an internal fleet, add and manage drivers, and turn on live location tracking so customers can follow deliveries in real time. All steps take place in the Nash Portal (https://portal.usenash.com). You need an admin account for your organization.

Overview

Running your own deliveries through Nash involves three parts:
  1. Internal fleet — a fleet provider that represents your own drivers and vehicles. It carries the optimization settings (vehicle counts, costs, and limits) Nash uses when planning routes.
  2. Drivers — the people who fulfill deliveries. Each driver has a name, phone number, optional vehicle details, and the store locations they serve.
  3. Live location tracking — the driver’s device shares its GPS location while delivering, and you control whether that location appears on the customer-facing tracking page.
Two capabilities in this guide are provisioned by Nash rather than self-serve:
  • Internal fleets are created on the backend by Nash. Admins can edit an existing internal fleet in the Portal but cannot create one from scratch.
  • The Drivers tab appears only for organizations on Nash Lite TMS.
If you don’t see these in your Portal, contact Nash support to have them enabled.

Prerequisites

Before you begin, make sure you have:
  1. An admin account for your organization in the Nash Portal.
  2. An internal fleet enabled on your organization (provisioned by Nash — see the note above).
  3. Nash Lite TMS enabled if you want to add and manage drivers in the Portal.
  4. At least one store location configured, so drivers can be associated with the locations they serve.

Step 1: Configure your internal fleet

Your internal fleet holds the settings Nash uses when optimizing and dispatching routes to your drivers.
  1. In the left sidebar, click Providers.
  2. In the floating toggle bar at the bottom of the page, select Internal. The page header reads Internal Fleets.
  3. You’ll see a table of your internal fleets. Click a fleet row to open its configuration drawer.
If the Internal Fleets tab isn’t visible, your organization doesn’t have an internal fleet yet. The table cannot create one — contact Nash support to provision an internal fleet, then return here to configure it.
The fleet drawer is titled with your fleet’s name. Under Configurations for Optimization, you can set the attributes Nash considers when running route optimization: When you’re done, click Save. These settings feed directly into Nash’s route optimization for your fleet.

Step 2: Add drivers

With Nash Lite TMS enabled, you manage drivers directly in the Portal.
  1. In the left sidebar, click Providers, then select Internal in the floating toggle bar.
  2. Switch to the Drivers tab. The header shows a count of your Internal Drivers.
  3. Click New Driver to open the Add New Driver drawer.
If you don’t see a Drivers tab, your organization isn’t on Nash Lite TMS. Contact Nash support to enable it.
Fill in the driver details:
  • Driver
    • First Name (required)
    • Last Name (required)
    • Phone Number (required) — enter the driver’s mobile number; this is how they receive their deliveries.
  • Vehicle (Optional) — expand this section to record the driver’s vehicle.
    • Type — choose Car, SUV, Bike, or Motorbike.
    • For motorized vehicles you can also set Brand, Model, Year, Color, and License Plate. (Bikes skip these.)
  • Locations — click Add Location to associate the driver with one or more of your store/pickup locations. This determines which locations the driver can fulfill orders for.
Set the driver’s availability (Available/Unavailable) using the toggle in the drawer header, then click Save. A confirmation appears once the driver has been added, and the driver shows up in the Drivers table.

Manage existing drivers

The Drivers table lists each driver’s Name, Phone Number, Vehicle, Location, and Availability. From here you can:
  • Toggle a driver’s Availability on or off directly in the table.
  • Click a driver (or use the row actions) to Edit their details.
  • Remove a driver you no longer need.

Connecting a driver to the Driver App

Nash Lite TMS drivers fulfill deliveries through a web-based Driver App — there is no separate native app to install and no email invitation. Each driver opens a personal link in their phone’s browser, where they see assigned deliveries, set availability, and view history.
Nash distributes the Driver App links — contact Nash support if your drivers need theirs.

Step 3: Turn on live location tracking

Live location tracking has two parts: the driver’s device must share its location, and you choose whether that location is displayed to customers on the public tracking page.

Part A: The driver shares their location

Location capture happens in the Driver App and is controlled by the driver, not by an admin setting:
  1. When a driver opens the Driver App, they see a prompt to Share your location so customers can track the delivery.
  2. The driver taps Share your location and grants their browser’s location permission.
  3. Once granted, the Driver App automatically streams the driver’s position to Nash while they’re delivering — no further action is required.
If a driver denies the location permission, tracking won’t work for their deliveries. The Driver App shows OS-specific instructions for re-enabling location access in the device’s browser settings.

Part B: Show the driver’s location to customers

You control what appears on your customer-facing public tracking page from Settings:
  1. In the left sidebar, open Settings.
  2. Go to CustomizationTracking. The page is titled Public Tracking Customization.
  3. Under Configure Sections, turn on the switches that control map and location display:
    • Driver Location — shows the driver’s live location.
    • Driver Location After Delivery — keeps the last-known driver location on the page after a delivery completes. Off by default; the return-to-store leg stays hidden either way.
    • Map — shows a map with pickup, dropoff, and driver locations.
  4. Click Save.
With these enabled, customers who open the public tracking link (https://portal.usenash.com/tracking/[JOB_ID]) will see the driver’s live position on the map as the delivery progresses.

Optional: Driver geolocation alerts

If you want internal alerts based on a driver’s proximity to pickup or dropoff, go to SettingsNotificationsTriggers and configure a Driver Geolocation trigger. This is for alerting (for example, “driver is within X minutes of dropoff”) and is separate from enabling tracking display.

Putting it together

A typical end-to-end setup looks like this:
  1. Nash provisions your internal fleet (and Nash Lite TMS, if you want to manage drivers in the Portal).
  2. You configure the fleet’s optimization settings under Providers → Internal → Internal Fleets.
  3. You add your drivers under Providers → Internal → Drivers, including their vehicle and store locations.
  4. Drivers open the Driver App and share their location.
  5. You enable Driver Location and Map under Settings → Customization → Tracking so customers can follow deliveries live.

Common questions and troubleshooting

I don’t see an “Internal Fleets” tab

Your organization doesn’t have an internal fleet yet. Internal fleets are provisioned by Nash. Contact Nash support to set one up.

I don’t see a “Drivers” tab

The Drivers tab requires Nash Lite TMS. Contact Nash support to enable it for your organization.

A driver’s location isn’t showing on the tracking page

Check both halves of tracking:
  • Capture — confirm the driver granted location permission in the Driver App (the Share your location prompt). Denied permissions stop tracking.
  • Display — confirm Driver Location and Map are turned on under Settings → Customization → Tracking.

Routes aren’t being optimized for my fleet

Make sure your internal fleet has its Configurations for Optimization filled in — particularly Vehicle Count and the Limits (max orders per route, driving time, driving distance). Missing values can prevent the optimizer from planning routes for your fleet.