Stores

Create and import store location data for enrolment journeys and wallet pass experiences.

Store data creates a shared reference for each physical location. It gives each store a unique identifier and location details that can be used in enrolment journeys, redirects, and wallet pass configurations.

Use store data when one programme operates across several locations. It keeps location context consistent and avoids manually adding the same store information to every journey.

Real-world examples

• A retail brand adds a storeId to each in-store QR code for location-level enrolment reporting.
• An event organiser stores venue details for ticket distribution and customer support.
• A luxury brand connects a clienteling journey to the store where the customer enrolled.

Why store data matters

Store data links a digital wallet journey to a physical location. This supports accurate attribution, localised customer experiences, and reliable operational reporting.

The storeId is the key value. It must stay stable because redirects and other configurations use it to identify the location.

Create a store

Create stores individually when opening a new location or maintaining a small store network.

1

Open store data

In the administration console, open Integration → Data → Store.

Open the Store section to manage location data.

2

Add a store

Select Add New to open the store-data form.

3

Enter the store details

Add the required store information:

• storeId — a unique, stable identifier for the location.
• Name — the store or venue name.
• Address — the location address.

Use a unique store ID and recognizable location details.

4

Save and verify

Select Save, then confirm that the new store appears in the store list.

Verify the saved record before using its store ID in a redirect.

Import several stores

Use an Excel import when adding or updating many locations. Include the same core fields used for manual creation: storeId, name, and address.

Additional store-specific data can also be included when needed, such as a ticket code. Keep column names and identifier values consistent across imports.

Import store data in bulk to maintain a large location network efficiently.

Use store IDs in enrolment journeys

Store IDs connect location data to distribution channels. For example, a Redirect can add storeId to an enrolment form URL.

Before publishing a store-specific QR code or link, confirm that its storeId matches an existing store record. This prevents missing location context and inaccurate reporting.

FAQ

What makes a good store ID?

Use a unique and stable value from an existing business system when possible. Avoid values that may change when a store name, address, or local team changes.

Can one enrolment form support several stores?

Yes. Use the same form with separate redirects. Each redirect can add the relevant storeId for its location.

Should stores be created manually or through import?

Create individual stores manually for one-off changes. Use Excel import for a new store network or repeated updates across several locations.

What should be checked after importing stores?

Verify a sample of records. Confirm that each store ID is unique and that its name and address match the intended location.