> For the complete documentation index, see [llms.txt](https://docs.thewalletcrew.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.thewalletcrew.io/guides-enrolment/enrolment/enrolment-form/stores.md).

# Stores

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.

<details>

<summary><strong>Real-world examples</strong></summary>

* 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.

</details>

### 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.

{% stepper %}
{% step %}

#### Open store data

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

<figure><img src="/files/N7Q1VQ2c5q0k6RSrTLwj" alt="Store data section in The Wallet Crew administration console"><figcaption><p>Open the Store section to manage location data.</p></figcaption></figure>
{% endstep %}

{% step %}

#### Add a store

Select **Add New** to open the store-data form.
{% endstep %}

{% step %}

#### 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.

<figure><img src="/files/JBdnXNqpYxC7BcI7JQEf" alt="Store data form with fields for store ID, name, and address"><figcaption><p>Use a unique store ID and recognizable location details.</p></figcaption></figure>
{% endstep %}

{% step %}

#### Save and verify

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

<figure><img src="/files/keHgiR0Jwusz82GUR0dy" alt="Saved store data record in The Wallet Crew administration console"><figcaption><p>Verify the saved record before using its store ID in a redirect.</p></figcaption></figure>
{% endstep %}
{% endstepper %}

### 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.

<figure><img src="/files/sD3NGXtGJUN8BYkaEgQ2" alt="Excel import interface for several store data records"><figcaption><p>Import store data in bulk to maintain a large location network efficiently.</p></figcaption></figure>

### Use store IDs in enrolment journeys

Store IDs connect location data to distribution channels. For example, a [Redirect](/guides-enrolment/enrolment/enrolment-form/redirect.md) 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

<details>

<summary><strong>What makes a good store ID?</strong></summary>

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.

</details>

<details>

<summary><strong>Can one enrolment form support several stores?</strong></summary>

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

</details>

<details>

<summary><strong>Should stores be created manually or through import?</strong></summary>

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

</details>

<details>

<summary><strong>What should be checked after importing stores?</strong></summary>

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

</details>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.thewalletcrew.io/guides-enrolment/enrolment/enrolment-form/stores.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.