> 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/guides/pause-and-reactivate-a-loyalty-program.md).

# Pause and reactivate a loyalty program

Temporarily pause loyalty at a business or location, then reactivate it.

Pause the whole business through [Business program status](https://docs.perkville.com/features/settings/business/business-program-status.md). Pause one location through [Location program status](https://docs.perkville.com/features/settings/location-setup/locations/location-program-status.md).

Choose any [allowed activities while inactive](https://docs.perkville.com/features/settings/loyalty-activity-controls/allowed-activities-while-inactive.md) and set a customer message before saving. Reactivate manually or set a scheduled activation date.

### During a pause

Balances, history, settings, schedules, and location status choices remain saved. Existing vouchers remain usable.

Normal monthly point expiration and expiration-warning processing pause while the applicable business or location is inactive. They resume on the normal future cycle after reactivation. There is no catch-up cycle or automatic extension.

Birthday and anniversary awards skipped during inactivity are not guaranteed to catch up. Skipped integration transactions are not automatically retried.

### Before reactivating

1. Confirm the activation and [earliest transaction dates](https://docs.perkville.com/features/settings/loyalty-activity-controls/activation-and-transaction-dates.md).
2. Review allowed activities and the customer message.
3. Test a representative customer workflow.

Pausing loyalty differs from deleting or operationally disabling a location. Use location status for a temporary loyalty pause.


---

# 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/guides/pause-and-reactivate-a-loyalty-program.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.
