Stores

Manage physical store and venue locations for geolocated Apple Wallet and Google Wallet pass notifications.

Manage stores for geolocated wallet pass notifications

Stores is the physical location registry for a wallet programme. It supports retail stores, venues, pop-ups, and other address-based sites.

The Wallet Crew embeds configured locations in wallet passes. A phone can then surface a contextual message when a customer is nearby.

Stores are a prerequisite for geolocated notifications. At least one store must exist and be geocoded before location triggers can be configured on a pass template.

Configure geolocated notifications on the pass template after geocoding a store.

Real-world examples

• A retailer can add a customer's preferred store to a loyalty pass.
• An event organiser can add a venue to an event ticket.
• A brand can add campaign pop-up locations to a wallet pass.

Store location fields

Field	Description
ID	A unique identifier for this location. Read-only after creation. Matched to customer data, such as a home store code from a POS or CRM.
Store name	A human-readable label for internal management. Not shown to end-users.
Address	Street address. Used to geocode coordinates automatically.
Latitude / Longitude	GPS coordinates. Populated automatically with Find, or entered manually.

Create and geocode a store

Create a store record before configuring a location trigger. Use a stable ID so the record can be matched with source data.

1

Go to Data & Integrations → Stores

Open the Stores page from the left navigation.

2

Click Add

The edit form opens.

3

Fill in the ID and Store name

Use a stable ID from the source system, such as a POS store code or CRM location ID. The ID cannot be changed after creation.

4

Enter the address and geocode it

Enter the address in Address, then click Find. The platform resolves GPS coordinates and positions a map pin. Review the pin position before saving.

If the resolved location is incorrect, adjust latitude and longitude manually. This can occur with large venues.

5

Save

Click Save. The store is now available for geolocation configuration.

The ID is permanent. Use a stable, recognisable value from existing systems. Pass templates and Liquid logic reference this ID, for example, to assign a customer's home store.

Import store locations in bulk

Use Import for large location lists. Use Export first to download a CSV template in the expected format.

Edit or delete a store location

Click a row to edit its name, address, or coordinates. Use Delete to remove a store.

Deleting a store removes it from future location calculations. Issued passes keep its coordinates until their next update.

When a store closes permanently, also delete its associated redirect or QR code to prevent customers from scanning a code that no longer leads to an active enrolment journey.

Geolocation limits for wallet passes

Apple Wallet and Google Wallet impose the following geolocation limits:

Limit	Value
Maximum coordinates per pass	10
Maximum radius per coordinate	300 m

The Wallet Crew selects stores to embed in each pass, based on the configuration. Retail programmes often embed a customer's home store and the nine closest locations.

Frequently asked questions about stores and geolocation

Can Stores be used for event venues?

Yes. Any address-based location can be a store record. This includes stadiums, concert halls, conference centres, and pop-up sites. The registry is named “Stores,” but its records are not limited to retail locations.

What happens when a store address changes?

Changing an address and re-geocoding updates its registry coordinates. The new coordinates apply with the next pass update. Issued passes keep previous coordinates until then.

Are coordinates required for every store?

Only stores with latitude and longitude can be embedded in a pass. Records without coordinates remain valid but cannot trigger geolocation.