> 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/loyalty-activity-controls/activation-and-transaction-dates.md).

# Activation and transaction dates

Understand when loyalty begins and which dated transactions can qualify.

An **activation date** controls when normal loyalty activity may begin. An **earliest transaction date** controls the oldest dated transaction that may qualify. These controls are independent.

The earliest transaction date also applies to allowed activities. Transactions before the effective cutoff are excluded, even when imported later. Previously skipped transactions are not automatically reprocessed.

### Effective cutoffs

If no business cutoff is set, the business activation date is the safe default. If no location cutoff is set, the location activation date is the safe default.

A location can use a later, more restrictive cutoff. It cannot use an earlier, more permissive cutoff than the business. This prevents unwanted historical backfills after activation.

### Examples

**Business activation:** A business activates November 15. It accepts transactions dated January 1 or later for milestone calculations. Normal loyalty activity still begins November 15.

**Later location rollout:** A business is active. A new location activates December 1 and sets its earliest transaction date to December 1. Older imported transactions do not qualify for that location.

{% hint style="warning" %}
A permissive cutoff can allow an integration backfill to process older transactions. Review the effective cutoff before saving.
{% endhint %}

See [Business program status](https://docs.perkville.com/features/settings/business/business-program-status.md) and [Location program status](https://docs.perkville.com/features/settings/location-setup/locations/location-program-status.md) for status-specific setup.


---

# 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/loyalty-activity-controls/activation-and-transaction-dates.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.
