> For the complete documentation index, see [llms.txt](https://docs.perkville.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.perkville.com/features/settings/location-setup/locations/add-and-configure-a-location.md).

# Add and configure a location

If your business already uses Perkville and is opening another location, creating it is only the first step. Complete this checklist before loyalty activity begins.

## Location setup checklist

1. Add and validate the location details.
2. Map the correct external ID and integration location.
3. Review [Location program status](https://docs.perkville.com/features/settings/location-setup/locations/location-program-status.md) before activity starts. Choose **Active**, **Activate With Business**, **Activate Later**, or **Inactive**.
4. Review [allowed activities while inactive](https://docs.perkville.com/features/settings/loyalty-activity-controls/allowed-activities-while-inactive.md) and the customer message.
5. Set the [earliest transaction date](https://docs.perkville.com/features/settings/loyalty-activity-controls/activation-and-transaction-dates.md) when historical imports need restriction.
6. Confirm staff access, groups, and integration setup.
7. Run a final activation review.

{% hint style="warning" %}
An incorrect earliest transaction date can allow an integration backfill to process older transactions.
{% endhint %}

## 1. Add the location in Perkville

Go to **Settings → Locations** and click **Add Location**. Enter the location name, address, timezone, language, and any other applicable fields.

See [Locations](https://docs.perkville.com/features/settings/location-setup/locations.md) for the field definitions and location-management steps.

{% hint style="warning" %}
Adding a location may affect your Perkville subscription. Contact [Perkville Support](https://docs.perkville.com/overview/support.md) if you need help confirming account or billing implications.
{% endhint %}

## 2. Connect the location to your integration

If your business uses a POS, membership, scheduling, or other connected system, confirm the new location is authorized and mapped correctly before activity begins.

* Add the required [External location ID](https://docs.perkville.com/features/settings/location-setup/locations/external-location-ids.md) when applicable.
* Review the [Integration Reference](https://docs.perkville.com/integrations/integration-reference.md) for any system-specific authorization or setup requirements.
* If the new location uses a different system, account, site, or authorization than your existing locations, contact Perkville before activation so the integration setup can be confirmed.

{% hint style="info" %}
An external location ID is only one part of integration setup. Some integrations also require separate authorization, whitelisting, or configuration.
{% endhint %}

{% hint style="warning" %}
Seeing customer activity arrive from the new site does **not** by itself confirm that the location is fully configured in Perkville. Activity can sometimes reach Perkville before the location has been added to the rewards program, mapped correctly, or included in the intended program rules. Complete the remaining setup and verification steps below before launch.
{% endhint %}

## 3. Decide which program features apply at the new location

Review your location settings across the loyalty program and add the new location wherever it should participate. This may include:

* [Earning rules](https://docs.perkville.com/features/earning-rules.md)
* [Promotions and bonus earnings](https://docs.perkville.com/features/earning-rules/promotions-and-bonus-earnings.md)
* [Rewards](https://docs.perkville.com/features/redeeming-rules.md)
* [Challenges](https://docs.perkville.com/features/challenges.md)
* [Referral offers](https://docs.perkville.com/features/referrals/configuring-your-referral-program/referral-offer.md)

For guidance on standardizing a program while allowing location-level flexibility, see [Multi-location businesses and franchises](https://docs.perkville.com/overview/multi-location-businesses-and-franchises.md).

## 4. Review staff access

Make sure the appropriate staff members can access the new location. Staff access can be restricted by location, so head-office, regional, franchise, and local staff may each need different assignments.

See [Staff members](https://docs.perkville.com/features/settings/staff-members.md).

## 5. Add the location to reporting groups if needed

If you use location groups for reporting, add the new location to the appropriate region, franchise ownership group, or other reporting group.

See [Multi-location businesses and franchises](https://docs.perkville.com/overview/multi-location-businesses-and-franchises.md#location-groups-and-reporting).

## 6. Verify the setup before launch

Before announcing the new location, verify a few representative workflows:

* Customer activity is associated with the correct location.
* The intended earning rules and promotions apply.
* The correct rewards, challenges, and referral offers are visible for that location.
* Staff can access the location with the expected permissions.
* Reporting groups and integration identifiers are correct.

If anything does not match the intended setup, contact [Perkville Support](https://docs.perkville.com/overview/support.md) before activation.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.perkville.com/features/settings/location-setup/locations/add-and-configure-a-location.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
