> 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/faqs/points/how-do-i-stop-customers-from-earning-new-points-but-let-them-use-existing-points.md).

# How do I stop customers from earning new points but let them use existing points?

If you are winding down or changing your loyalty program, you can stop customers from earning new points while continuing to offer rewards for points they have already earned.

For a temporary pause, use [Business program status](https://docs.perkville.com/features/settings/business/business-program-status.md) or [Location program status](https://docs.perkville.com/features/settings/location-setup/locations/location-program-status.md). Choose [allowed activities while inactive](https://docs.perkville.com/features/settings/loyalty-activity-controls/allowed-activities-while-inactive.md) rather than treating a pause as an earning-rule change. Existing vouchers remain usable. A location-only pause does not pause the business.

1. Go to the [Loyalty Program](https://docs.perkville.com/features/settings/loyalty-program.md) page and deactivate the earning rules you no longer want customers to use.
2. Leave the [redeeming rules](https://docs.perkville.com/features/redeeming-rules.md) active for any rewards customers should still be able to redeem.
3. Review any program-wide participation settings that could affect redemption. In particular, if you use membership settings, remember that **Only active members can participate in the rewards program** applies across the program rather than to an individual rule or reward.
4. Review your point-expiration settings separately if you want remaining balances to expire on a particular schedule. For example, Perkville supports point expiration by inactivity and, when membership features are enabled, expiration after membership cancellation through Membership settings.

{% hint style="info" %}
Deactivating earning rules and expiring existing point balances are separate decisions. Turning off earning does not require you to deactivate the rewards customers should still be able to redeem.
{% endhint %}

## Winding down one location in a multi-location program

If one location is leaving Perkville while the rest of the business remains active, do not treat deleting the location as the first step. Plan the wind-down before removing the location from Perkville.

1. **Review location-scoped earning rules.** Remove or deactivate earning opportunities for the departing location while preserving the rules that should remain available at other locations.
2. **Review location-scoped redeeming rules.** Decide which rewards customers should still be able to use and at which remaining locations, and update the affected rules accordingly.
3. **Plan for outstanding points and customer communication.** Decide how customers associated with the departing location should use existing balances and communicate any relevant deadlines or changes before the cutoff.
4. **Coordinate the location removal with Perkville.** Before deleting the location, contact Perkville Support to confirm the appropriate timing and any effects on integrations, historical reporting, or account configuration.
5. **Coordinate contract or billing changes with Perkville Support.** Location removal in the product and subscription or contract changes are separate steps.

See [Locations](https://docs.perkville.com/features/settings/location-setup/locations.md) for location settings.

## When a closing location's members move to another location

A location closing is different from turning off point earning: members may still need to earn and redeem points at the destination location. Coordinate the transition with [Perkville Support](https://docs.perkville.com/overview/support.md) and the team that manages your POS or membership integration.

1. **Identify both locations.** Provide the closing and destination location names, their Perkville location IDs, and their external POS or membership-system location IDs.
2. **Agree on the effective date.** Confirm when the old location stops recording activity and when members should begin appearing at the new location.
3. **Update the source membership system.** Coordinate any member/home-location reassignment in the source system, then confirm how the integration sends the updated location into Perkville.
4. **Review earning and redemption availability.** Verify that the destination location is enabled for the earning and redeeming rules customers should continue using. Determine how existing point balances and rewards will be handled.
5. **Test with representative member records.** After the transition, verify membership/home location, a new qualifying activity, point balance, and reward eligibility in Perkville.
6. **Confirm reporting and billing separately.** Ask Support how the change affects historical location reports and coordinate any subscription or contract changes independently of the product configuration.

Do not delete the old location before confirming the transition plan. See [Locations](https://docs.perkville.com/features/settings/location-setup/locations.md) for settings and [Membership settings](https://docs.perkville.com/features/settings/memberships/settings.md) for participation rules.


---

# 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/faqs/points/how-do-i-stop-customers-from-earning-new-points-but-let-them-use-existing-points.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.
