> 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/business/business-program-status.md).

# Business program status

Control loyalty status, activation, and inactive behavior across your business.

Use **Business program status** to control loyalty across your business.

Business program status does not automatically activate every location. Each location has its own [Location program status](https://docs.perkville.com/features/settings/location-setup/locations/location-program-status.md).

<figure><img src="https://2181708597-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FSiE75SeColbiBVbet0NZ%2Fuploads%2FIU1scwJVIWjUmMeF6GSs%2Fbusinessstatus.jpeg?alt=media&amp;token=081665da-dc56-4b1d-90de-258941ef7566" alt=""><figcaption></figcaption></figure>

### Current status

| Status                   | Effect                                                                                                  |
| ------------------------ | ------------------------------------------------------------------------------------------------------- |
| **Active**               | Locations can run normal loyalty activity when their location program status also permits it.           |
| **Inactive**             | Normal loyalty activity pauses at every location, regardless of its saved location status.              |
| **Scheduled activation** | The business becomes active on the selected date. Location participation remains separately configured. |

### Scheduled activation

Choose **Scheduled activation**, then enter an activation date. Change or clear the date from this page before it occurs.

Locations set to **Activate With Business** activate with the scheduled business activation. Review the confirmation screen and affected-location summary before saving.

### Allowed activities

Choose limited activities that can continue while the business is inactive. See [Allowed activities while inactive](https://docs.perkville.com/features/settings/loyalty-activity-controls/allowed-activities-while-inactive.md).

### Customer message while inactive

Write the customer message shown while the business is inactive. Connected applications use this message when the business is inactive.

### Earliest transaction date

Set the oldest transaction date that can qualify. This is separate from the activation date. See [Activation and transaction dates](https://docs.perkville.com/features/settings/loyalty-activity-controls/activation-and-transaction-dates.md).

### Review and save

Review the status, activation date, allowed activities, customer message, and earliest transaction date. Confirm the affected-location summary, then save.

If the business has no locations, add and configure a location next. A business cannot start normal location loyalty activity without a configured location.

### What happens when the business is inactive

Balances, history, settings, location statuses, schedules, allowed-activity choices, and messages remain saved.

Normal activity pauses at every location. Allowed activities remain subject to each location's restrictions.

See [Pause and reactivate a loyalty program](https://docs.perkville.com/guides/pause-and-reactivate-a-loyalty-program.md) for temporary pauses.


---

# 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/business/business-program-status.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.
