Locations

A location is a store or site Nash keeps on file — a physical place an order is picked up from or dropped off at. Instead of retyping an address every time you build an order, you save the place once and pick it from a list; the order points at the saved record rather than copying it. Locations are the "where" behind every order: each one starts somewhere and ends somewhere, and both ends are locations.

There are two kinds, split by the job the place does for an order:

• Pickup locations — your stores and depots, the places orders leave from. This is the rich record: beyond an address and contact, a pickup location can carry operating hours, pickup windows, prep and service time, routing settings, coverage, and the zones it serves.
• Dropoff locations — recurring destinations you deliver to often enough to be worth saving. This is the lighter record: a name, an address, and an optional contact and instructions.

A single saved place can play both roles, so the kind isn't two separate databases — it's what the point does for a given order.

What a location saves

Every location carries a name and, on the pickup side, an external ID — your own store code, shown alongside the name as "Name (externalId)" so you can find a store by the code you already use. From there a location can hold a contact, an address with its own timezone, operating hours, pickup windows, prep and service time, blackout dates, and pickup or dropoff instructions. A pickup location adds the operational layer on top: picker capacity, routing settings, provider allocation, a coverage area, and the zones it's associated with.

You don't have to fill all of that in. The pickup form is a stepped one — pickup details, routing, zone details, integration, provider allocation, store inventory, coverage — and the later steps appear only when the matching capability applies to your organization. Don't be thrown if you see fewer steps than a colleague at another org; the extra steps are conditional, not missing.

Where to find this

Locations live under Configure ▸ Network ▸ Locations, as their own page. You can create one through the stepped form, import many at once from a CSV, sync stores from a connected online ordering platform, or export what you have. Locations are available to every organization — there's nothing to turn on.

Note

Location Operations users is a built-in role that scopes a user to specific stores, so a store manager sees and works only their own locations. Availability varies by organization — reach out to Nash for access.

What you can do with locations

• How locations work — what a location is, the two kinds, and how a saved place feeds dispatch and routing without moving an order on its own.
• Set up your pickup and dropoff locations — save, edit, import, and export the stores and addresses you attach to orders by name.
• Configure pickup labels — choose what prints on the pickup label for your organization.
• Set up a Location Operations user — scope a user to specific stores with the built-in role.
• Pickup location settings reference — every field on the pickup location form, and when each step appears.

How they relate to zones

Locations and zones describe two different things on the same map: a location is a single point, and a zone is a deliver-here area. They connect in both directions — a pickup location's form has a Zone details step for the zones it serves and a Blocked Zones section for zones it's excluded from, and a zone, in turn, lists the locations it covers. For the area side, see the zones overview.

One thing to carry into all of this: a saved location doesn't dispatch or route anything by itself. It just needs to exist to be picked from a list. Naming it on an order is what puts it to work — and even then, Nash dispatches the order while a provider or your own fleet actually drives it.