> For the complete documentation index, see [llms.txt](https://help.openloyalty.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.openloyalty.io/implementation-guide/plan-and-foundations/implementation-phases.md).

# Implementation Phases

The phases of an Open Loyalty implementation and who is responsible for what in each of them.

An implementation usually runs through six phases. They overlap — configuration starts while the integration is being built — but each has a clear outcome that the next one depends on.

{% stepper %}
{% step %}

### Discovery

Agree what the programme does: how members join, how they earn, what they can spend on, which channels take part, and which existing systems (e-commerce, POS, CRM, marketing automation) exchange data with Open Loyalty.

**Outcome:** a list of use cases, each mapped to an Open Loyalty capability — the module checklists in this guide.
{% endstep %}

{% step %}

### Design

Make the decisions that are expensive to change later:

* how members are identified across systems — see [Member identity](https://help.openloyalty.io/implementation-guide/plan-and-foundations/member-identity.md);
* where the integration logic lives — see [Integration architecture](https://help.openloyalty.io/implementation-guide/plan-and-foundations/integration-architecture.md);
* tenants, wallets and brands — see [Multi-brand programmes and wallets](https://help.openloyalty.io/implementation-guide/plan-and-foundations/multi-brand-and-wallets.md);
* which events Open Loyalty sends to other systems, and which it receives.

**Outcome:** an integration design with a sequence diagram per use case.
{% endstep %}

{% step %}

### Build

Configure the programme in the Admin Panel on the staging environment (wallets, campaigns, rewards, tiers…) and build the integration against the staging API.

**Outcome:** every use case works end to end on staging.
{% endstep %}

{% step %}

### Test and UAT

Run each use case with test members, including failures and retries. Business users accept the configuration and the member experience.

**Outcome:** signed-off use cases, and a known list of anything going live later.
{% endstep %}

{% step %}

### Go-live

Move the configuration to production, migrate existing members and balances, switch the channels over, and tell members.

**Outcome:** the programme running in production — see the [go-live checklist](https://help.openloyalty.io/implementation-guide/data-and-go-live/go-live-checklist.md).
{% endstep %}

{% step %}

### Hypercare and run

Watch the integration closely for the first weeks (failed requests, webhook deliveries, unexpected rewards) — see [After go-live](https://help.openloyalty.io/implementation-guide/data-and-go-live/after-go-live.md) — then move to normal support through the helpdesk.
{% endstep %}
{% endstepper %}

## Who does what

| Area                    | Open Loyalty                                       | Your team (or integrator)                                                  |
| ----------------------- | -------------------------------------------------- | -------------------------------------------------------------------------- |
| Environments            | Provides staging and production tenants and access | Requests tenants, creates API keys and admin users                         |
| Programme configuration | Advises on how to model the programme              | Configures wallets, campaigns, rewards, tiers, segments in the Admin Panel |
| Integration             | API, webhooks, documentation                       | Builds and runs the integration layer and the member-facing channels       |
| Member experience       | —                                                  | All screens, messages and notifications members see                        |
| Data migration          | Import tools and guidance                          | Prepares and validates the data, runs the imports                          |
| Testing                 | —                                                  | Test plan, test members, UAT sign-off                                      |
| Go-live                 | Confirms production readiness, limits increases    | Cutover plan, member communication                                         |
| Support                 | Platform support via the helpdesk                  | First-line support for members                                             |

{% hint style="info" %}
Open Loyalty is headless: it stores the programme, runs the rules and keeps balances, but it has no member-facing screens. Everything a member sees is built by your team on top of the API.
{% endhint %}


---

# 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://help.openloyalty.io/implementation-guide/plan-and-foundations/implementation-phases.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.
