Locations

Concept

A location is a reusable trading spot that sessions are scheduled against.

Each location stores the details customers and staff rely on during service: name, address, location type, map coordinates, wayfinding notes, and an optional default outlet.

You can add as many unique locations as you need, whether that is a regular weekly spot, a one-off private event, or a festival pitch.

Think of locations as your operating map. Sessions come and go, but locations stay reusable.

Why it matters

Strong location setup reduces avoidable customer friction on busy days.

• Customers can find the correct collection point quickly.
• Staff can run service with fewer "where are you?" support messages.
• Scheduling is faster because location records are reused across sessions.
• Reporting and operations stay clearer when each session points to the right place.

Poor location data usually shows up as late arrivals, queue confusion, and preventable support load.

Your location data is also customer-facing after checkout. Order confirmation emails use your saved location details (including address and map pin), and customers rely on this information to find you without contacting support.

How to configure it

1. Go to Dashboard -> Locations and select Add location.
2. Add a clear Location name (internal) your team will recognise later.
3. Set an optional Public title if customers should see a shorter or cleaner label.
4. Add the address using the location picker so coordinates and map context are captured.
5. Choose a Location type (for example market, festival, roadside, private event).
6. Set a Default outlet if this location usually runs with one outlet.
7. Add wayfinding details where useful:
   • Collection point label
   • Directions by car
   • Walking directions
   • Parking information
8. Save, then assign this location when creating or editing sessions.

Use one location per real pickup spot. Reuse it across dates instead of creating duplicates for every event.

How to verify it worked

• The location appears in your locations list and can be selected in session setup.
• A test session at that location publishes with correct customer-facing details.
• Address and directions are clear enough for a first-time customer to follow.
• If a default outlet is set, it is preselected when scheduling.

Before each live event, run one phone-based walkthrough from customer view to confirm links, wording, and wayfinding are still accurate.

Common mistakes

• Using vague names (for example "Main site") that are unclear on service day.
• Creating duplicate locations instead of reusing an existing record.
• Leaving stale directions after moving pitch position or access route.
• Forgetting to separate internal naming from public customer wording.
• Trying to archive a location that still has upcoming draft or published sessions.