> ## Documentation Index
> Fetch the complete documentation index at: https://docs.digifist.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Subscription Lifecycle

> How Back-in-Stock subscriptions move through PENDING, ACTIVE, NOTIFIED, and CANCELLED states in Galantis.

Every Back-in-Stock subscription in Galantis has a status that tracks where it is in its lifecycle — from the moment a customer submits their WhatsApp number through to notification delivery or cancellation. Status determines whether a subscriber receives a restock notification and prevents customers from being notified multiple times for the same restock event.

## What this covers

* All four subscription statuses and their meaning
* How status transitions are triggered
* The role of status in notification eligibility
* Viewing and managing subscriptions

## Subscription statuses

| Status      | Meaning                                                              | Eligible for notification |
| ----------- | -------------------------------------------------------------------- | ------------------------- |
| `PENDING`   | Newly submitted — awaiting activation                                | No                        |
| `ACTIVE`    | Enrolled — will receive a notification when the variant is restocked | Yes                       |
| `NOTIFIED`  | Notification sent — subscription expires after notification          | No                        |
| `CANCELLED` | Customer unsubscribed                                                | No                        |

Only subscriptions in `ACTIVE` status receive restock notifications. All other statuses are excluded from the notification dispatch.

## Status transitions

### PENDING

A subscription enters `PENDING` status the moment a customer submits their WhatsApp number through the storefront widget. At this point the subscription has been recorded but has not yet been activated.

### ACTIVE

Once activated, the subscription enters `ACTIVE` status and the customer is enrolled to receive a notification when the subscribed variant is restocked. A customer can hold multiple `ACTIVE` subscriptions simultaneously — one per variant they have subscribed to, across different products.

`ACTIVE` is the only status eligible for restock notification dispatch. When the `BACK_IN_STOCK` trigger fires for a variant, Galantis queries all `ACTIVE` subscriptions for that variant and enrolls each one in the notification flow.

### NOTIFIED

After a restock notification is successfully sent, the subscription status moves to `NOTIFIED`. This is a terminal status for that subscription record — a notified subscription does not receive a second notification if the same variant is restocked again.

`NOTIFIED` status provides duplicate notification protection. Without it, a variant that fluctuates between zero and positive inventory multiple times (a common pattern during high-demand restocks) could send repeated notifications to the same customer for the same restock event.

If a customer wants to receive future notifications for the same variant, they must re-subscribe through the widget — which creates a new subscription record in `PENDING` status.

<Note>
  Moving to `NOTIFIED` does not mean the customer received and read the message — it means the notification was dispatched by Galantis. If the message failed to deliver (due to a phone number issue, an expired conversation window, or insufficient credits), the subscription still moves to `NOTIFIED`. Check the automation activity log for delivery status details on the notification message itself.
</Note>

### CANCELLED

A subscription moves to `CANCELLED` when a customer unsubscribes.

`CANCELLED` subscriptions are permanently excluded from notification dispatch. A cancelled subscription cannot be reactivated — if the customer wants to subscribe again, they must submit a new subscription through the widget.

## Consent state and subscription status

Subscription status and marketing consent (`marketing_state`) are two independent checks that both apply before a notification is sent:

1. **Subscription status must be `ACTIVE`**
2. **Customer's `marketing_state` must be `SUBSCRIBED`**

A customer with an `ACTIVE` subscription but `UNSUBSCRIBED` or `REDACTED` consent status will not receive a notification — the consent check excludes them even though their subscription is technically eligible. This ensures a customer who opted out of WhatsApp marketing through any channel is not messaged via the Back-in-Stock pipeline.

<Warning>
  Consent state takes precedence over subscription status. An `ACTIVE` subscription on an `UNSUBSCRIBED` customer will never trigger a notification send. If a customer subscribed through the widget but has since replied STOP to another message, their Back-in-Stock subscription becomes effectively inactive even though its status remains `ACTIVE`.
</Warning>

## Viewing and managing subscriptions

Navigate to **Back-in-Stock → Subscriptions** to view all subscription records. The list can be filtered by status, product, variant, and date range.

Per-subscription details show:

* The customer's WhatsApp number and name
* The specific product and variant subscribed to
* The current status and status history
* The timestamp of subscription creation and any status transition

Individual subscription records can be cancelled by an admin from the subscription detail view — useful for removing subscriptions submitted in error or for customers who request cancellation through a support channel.

## Related guides

* [Widget Installation](./widget-installation) — How subscriptions are created through the storefront widget
* [Notification Logic](./notification-logic) — How `ACTIVE` subscriptions are enrolled into the notification pipeline
* [Product & Inventory Rules](./product-inventory-rules) — Per-variant subscription limits and eligibility
* [Consent & Opt-outs](/whatsapp/audience/consent-optouts) — How `marketing_state` interacts with subscription status