---
title: "Subscriptions"
description: "A non-technical ecosystem overview of Subscriptions in RevCent, focused on how recurring customer billing relationships are created from Products and Subscription Profiles, renewed through Subscription Renewals, connected to Sales, Product Sales, Trials, payments, shipping, fulfillment, customer support, recovery workflows, AI, voice, shops, and BigQuery reporting across the RevCent relationship graph."
type: "item"
company: "RevCent"
canonical: "https://revcent.com/documentation/markdown/ecosystem/item/Subscription.md"
relationships:
  - name: "Product"
    url: "https://revcent.com/documentation/markdown/ecosystem/feature/Product.md"
  - name: "Subscription Profile"
    url: "https://revcent.com/documentation/markdown/ecosystem/feature/SubscriptionProfile.md"
  - name: "Subscription Renewal"
    url: "https://revcent.com/documentation/markdown/ecosystem/item/SubscriptionRenewal.md"
technical_links:
  web_app: "https://kb.revcent.com/en/revenue/subscription"
  api:
    section: "https://revcent.com/docs/api/v2#section-subscriptions"
    operations:
      - name: "Get Subscriptions"
        operation_id: "GetSubscriptions"
        operation: "https://revcent.com/docs/api/v2#operation-GetSubscriptions"
        schema: "https://revcent.com/documentation/files/api/operation/GetSubscriptions.json"
      - name: "Get A Subscription"
        operation_id: "GetSubscription"
        operation: "https://revcent.com/docs/api/v2#operation-GetSubscription"
        schema: "https://revcent.com/documentation/files/api/operation/GetSubscription.json"
      - name: "Edit A Subscription"
        operation_id: "EditSubscription"
        operation: "https://revcent.com/docs/api/v2#operation-EditSubscription"
        schema: "https://revcent.com/documentation/files/api/operation/EditSubscription.json"
      - name: "Activate A Subscription"
        operation_id: "ActivateSubscription"
        operation: "https://revcent.com/docs/api/v2#operation-ActivateSubscription"
        schema: "https://revcent.com/documentation/files/api/operation/ActivateSubscription.json"
      - name: "Suspend A Subscription"
        operation_id: "SuspendSubscription"
        operation: "https://revcent.com/docs/api/v2#operation-SuspendSubscription"
        schema: "https://revcent.com/documentation/files/api/operation/SuspendSubscription.json"
      - name: "Cancel A Subscription"
        operation_id: "CancelSubscription"
        operation: "https://revcent.com/docs/api/v2#operation-CancelSubscription"
        schema: "https://revcent.com/documentation/files/api/operation/CancelSubscription.json"
      - name: "Renew A Subscription"
        operation_id: "RenewSubscription"
        operation: "https://revcent.com/docs/api/v2#operation-RenewSubscription"
        schema: "https://revcent.com/documentation/files/api/operation/RenewSubscription.json"
      - name: "Search Subscriptions"
        operation_id: "SearchSubscriptions"
        operation: "https://revcent.com/docs/api/v2#operation-SearchSubscriptions"
        schema: "https://revcent.com/documentation/files/api/operation/SearchSubscriptions.json"
  mcp:
    overview: "https://revcent.com/documentation/markdown/mcp/operation/OverviewSubscription.md"
    operations:
      - name: "Get Subscriptions"
        operation_id: "GetSubscriptions"
        markdown: "https://revcent.com/documentation/markdown/mcp/operation/GetSubscriptions.md"
        available_via_ai: true
      - name: "Get A Subscription"
        operation_id: "GetSubscription"
        markdown: "https://revcent.com/documentation/markdown/mcp/operation/GetSubscription.md"
        available_via_ai: true
      - name: "Edit A Subscription"
        operation_id: "EditSubscription"
        markdown: "https://revcent.com/documentation/markdown/mcp/operation/EditSubscription.md"
        available_via_ai: true
      - name: "Activate A Subscription"
        operation_id: "ActivateSubscription"
        markdown: "https://revcent.com/documentation/markdown/mcp/operation/ActivateSubscription.md"
        available_via_ai: true
      - name: "Suspend A Subscription"
        operation_id: "SuspendSubscription"
        markdown: "https://revcent.com/documentation/markdown/mcp/operation/SuspendSubscription.md"
        available_via_ai: true
      - name: "Cancel A Subscription"
        operation_id: "CancelSubscription"
        markdown: "https://revcent.com/documentation/markdown/mcp/operation/CancelSubscription.md"
        available_via_ai: true
      - name: "Renew A Subscription"
        operation_id: "RenewSubscription"
        markdown: "https://revcent.com/documentation/markdown/mcp/operation/RenewSubscription.md"
        available_via_ai: true
      - name: "Search Subscriptions"
        operation_id: "SearchSubscriptions"
        markdown: "https://revcent.com/documentation/markdown/mcp/operation/SearchSubscriptions.md"
        available_via_ai: true
  bigquery_schema: "https://revcent.com/documentation/files/bigquery/dataset.json"
  bigquery_tables:
    - "subscription"
---

# Subscriptions

Subscriptions are one of the most important items in RevCent because they represent ongoing customer relationships and recurring revenue.

A Subscription is created when a customer purchases a Product that has subscription behavior attached to it through a Subscription Profile. The Product explains what the customer is buying. The Subscription Profile explains how the recurring relationship should renew. The Subscription is the customer-specific billing relationship that is created from that purchase.

At the simplest level:

```text
Product is configured for subscription billing
    ↓
Customer buys the Product
    ↓
RevCent creates a Sale and Product Sale
    ↓
RevCent creates a Subscription
    ↓
Subscription Profile controls future renewals
    ↓
Each renewal creates a Subscription Renewal
```

For ecosystem graphing, Subscriptions are important because they connect Products, customers, payment methods, renewals, trials, recurring shipments, revenue recovery, emails, AI workflows, voice workflows, and BigQuery reporting.

## Why Subscriptions Are an Item

Subscriptions are an item because they are created from real commerce activity.

A business configures Products, Subscription Profiles, Payment Profiles, Shipping Profiles, Email Templates, AI Assistants, AI Voice Agents, Shops, Customer Portal, and other features. Those features define what can happen.

A Subscription is what happens when a customer actually enters into a recurring billing relationship.

The distinction is important:

```text
Product = what can be sold on a recurring basis
Subscription Profile = the renewal rules for recurring billing
Subscription = the customer's recurring relationship
Subscription Renewal = one renewal cycle for that Subscription
```

A Subscription is not just a schedule. It is a living customer record that changes over time as renewals succeed, fail, become overdue, recover, suspend, cancel, or reach their occurrence limit.

## Core Purpose

The core purpose of a Subscription is to manage recurring revenue for a specific customer.

A Subscription helps RevCent and the business understand:

- Which customer is being billed.
- Which Product the customer subscribed to.
- Which Subscription Profile controls the renewal behavior.
- When the Subscription started.
- When it last renewed.
- When it should renew next.
- Whether it is active, overdue, suspended, cancelled, replaced, or complete.
- Which renewal records have been created.
- Which payment records are attached to renewals.
- Which shipments, tax, discounts, refunds, and recovery actions are connected.
- Which shop, campaign, or source produced the Subscription.
- Which communication, AI, voice, and support workflows should respond.

This makes Subscriptions a central recurring-revenue item inside RevCent.

## Where Subscriptions Fit in the RevCent Ecosystem

Subscriptions sit between the original purchase and future recurring activity.

Conceptually:

```text
Product
    ↓
Product Sale
    ↓
Subscription
    ├─ Subscription Profile
    ├─ Subscription Renewals
    ├─ Customer
    ├─ Original Sale
    ├─ Trial, when applicable
    ├─ Payment records
    ├─ Shipping and fulfillment, when applicable
    ├─ Tax and discounts
    ├─ Pending Refunds
    ├─ Salvage Transactions and recovery workflows
    ├─ Email Templates
    ├─ Functions
    ├─ AI Assistants
    ├─ AI Voice Agents
    ├─ Customer Portal
    ├─ Shops
    └─ BigQuery reporting
```

A Subscription is the long-running relationship. Subscription Renewals are the recurring events inside that relationship.

## Technical Links

| Area | Link |
|---|---|
| Web App | `https://kb.revcent.com/en/revenue/subscription` |
| API | `https://revcent.com/docs/api/v2#section-subscriptions` |
| MCP | `https://revcent.com/documentation/markdown/mcp/operation/OverviewSubscription.md` |
| BigQuery Schema | `https://revcent.com/documentation/files/bigquery/dataset.json` |
| BigQuery Table | `subscription` |

These links show where Subscriptions can be viewed, managed, retrieved, automated, and used for relationship/reporting context.

## Relationship Summary

| Related Item or Feature | Relationship to Subscriptions |
|---|---|
| Product | A Subscription is created when a customer buys a subscription-capable Product. |
| Subscription Profile | Controls the renewal behavior, cadence, occurrence rules, payment profile, and renewal shipping behavior. |
| Subscription Renewal | Created each time the Subscription reaches a renewal cycle. |
| Sale | The original purchase event that can create the Subscription. |
| Product Sale | The line item inside the Sale that identifies the subscription Product purchased. |
| Customer | The person or account being billed on the recurring relationship. |
| Trial | A trial can lead into subscription behavior and may share lifecycle timing with the Subscription. |
| Transaction | Credit-card renewal payment attempts can create Transaction records. |
| PayPal Transaction | PayPal-related subscription activity can connect to PayPal transaction records where applicable. |
| Offline Payment | Alternate or externally handled payment activity can connect to Offline Payments where applicable. |
| Shipping | Shippable subscription Products can create recurring shipment records. |
| Tax | Renewal billing and subscription-related purchases can create tax records. |
| Pending Refund | Refunds tied to Subscription activity or Subscription Renewals can create Pending Refund records. |
| Salvage Transaction | Failed renewal payments can create recovery opportunities. |
| Third Party Shop | Subscriptions can be associated with a connected WooCommerce or external shop. |
| Email Template | Sends subscription lifecycle emails. |
| Function | Automates external notifications and custom subscription workflows. |
| AI Assistant | Reviews subscription events, overdue renewals, recovery opportunities, and lifecycle changes. |
| AI Voice Agent | Supports inbound subscription calls and outbound recovery or retention calls. |
| Customer Portal | Gives customers a self-service path for subscription and account needs. |
| BigQuery | Supports recurring revenue, lifecycle, recovery, retention, and relationship reporting. |

## Product Relationship

Products are the starting point for Subscriptions.

A Product can be a one-time purchase, a trial, a bundle, a subscription, or part of a larger ecommerce workflow. When a Product is configured with subscription behavior and sold to a customer, RevCent can create a Subscription from that purchase.

This makes Products versatile. The same Product ecosystem can support:

- recurring product refills,
- subscription boxes,
- memberships,
- digital access,
- recurring services,
- finite payment plans,
- trial-to-subscription offers,
- shippable recurring products,
- WooCommerce subscription products powered by RevCent.

The Product is what the customer bought. The Subscription is the recurring relationship that follows from buying it.

## Subscription Profile Relationship

Subscription Profiles are the rules behind Subscriptions.

A Subscription Profile can define the recurring behavior for many Subscriptions. It can represent patterns such as every 30 days, every month, quarterly, yearly, a specific number of renewals, or other recurring schedules.

In the ecosystem:

```text
Subscription Profile = recurring billing rules
Subscription = customer-specific recurring billing relationship
```

This separation is important because a business can reuse the same Subscription Profile across many Products and customers, while each customer still receives their own Subscription record.

## Custom Subscription Timing

Some customers need custom billing timing.

For example, a customer may want a product every 45 days instead of every 30 days, every 6 weeks instead of monthly, or quarterly instead of monthly.

RevCent can support customer-specific subscription behavior without changing the global Subscription Profile used by other customers.

This is important for retention because it lets a business adapt to the customer's usage pattern instead of losing the customer completely.

Conceptually:

```text
Customer wants a custom schedule
    ↓
Business adjusts that customer's Subscription behavior
    ↓
Other customers using the standard Subscription Profile remain unaffected
```

This is one of the reasons Subscriptions are more than recurring charges. They are customer relationships that can be managed, retained, and personalized.

## Subscription Renewal Relationship

A Subscription Renewal is one renewal cycle for a Subscription.

A Subscription can have many Subscription Renewals over time.

Each renewal can create or connect to:

- payment attempts,
- successful renewal revenue,
- failed renewal context,
- overdue status,
- shipping for recurring products,
- tax,
- discounts,
- refunds,
- recovery workflows,
- Email Templates,
- AI Assistant review,
- AI Voice Agent outreach,
- reporting.

Conceptually:

```text
Subscription = the ongoing recurring relationship
Subscription Renewal = one scheduled renewal event inside that relationship
```

Subscription Renewals make recurring revenue measurable. They show how the Subscription performs over time.

## Subscription Lifecycle

A Subscription can move through multiple lifecycle states.

Common lifecycle concepts include:

| Lifecycle State | Meaning |
|---|---|
| Active | The Subscription is currently active and expected to renew. |
| Overdue | A renewal did not successfully complete and needs attention or recovery. |
| Suspended | The Subscription is paused and not currently renewing. |
| Cancelled | The Subscription has been permanently ended. |
| Occurrence Limit | The Subscription reached its configured number of renewal cycles. |
| Replaced | The Subscription was replaced by another Subscription, often after a product change. |

These states matter because they change what the business should do next.

An active Subscription may simply continue. An overdue Subscription may need recovery. A suspended Subscription may need reactivation. A cancelled Subscription is a churn signal. A replaced Subscription shows that the customer moved to a different recurring relationship.

## Cancel vs Suspend vs Activate

Cancellation and suspension are not the same.

Suspension is useful when a customer wants to pause or hold a Subscription temporarily. A suspended Subscription can be restarted later.

Cancellation is used when the customer or business truly wants to end the Subscription permanently. Cancellation should be treated carefully because it represents a more final lifecycle change.

Activation is used when a suspended Subscription is restarted.

In plain language:

```text
Suspend = pause the relationship
Activate = restart a paused relationship
Cancel = permanently end the relationship
```

For retention, suspension can be valuable because it preserves the possibility of future revenue. If a customer is unsure, needs a break, has too much product, is traveling, or wants to delay shipments, suspension or schedule adjustment may be better than cancellation.

## Manual Renewal

RevCent automatically handles scheduled subscription renewals based on the Subscription Profile.

A manual renewal is different. It means the business is choosing to renew the Subscription now instead of waiting for the scheduled process.

Manual renewal can be useful when:

- the customer asks for an early refill,
- support needs to process a renewal immediately,
- the customer has authorized an immediate charge,
- a recovery workflow has confirmed the customer wants to continue,
- the business intentionally wants to renew now.

Manual renewal should not be treated as a status check or casual support action. It can affect the future renewal schedule because the Subscription Profile uses the renewal timing to determine the next cycle.

## Trial Relationship

Trials can be closely related to Subscriptions.

A trial lets the customer start with a delayed billing or conversion period. When the trial expires, RevCent can attempt to convert the customer into paid recurring activity depending on the Product and Subscription configuration.

A trial can also affect subscription timing. For example, changing the next renewal timing of a Subscription that is still in trial mode can affect the related trial timing as well.

For ecommerce businesses, trials are a powerful acquisition tool, but they need strong recovery and communication support. Trial expiration success, trial expiration failure, payment recovery, Email Templates, AI Assistants, AI Voice Agents, and Customer Portal all help turn trial users into paying subscribers.

## Payment Relationship

Subscriptions connect recurring billing to payment infrastructure.

A Subscription may be tied to different payment paths depending on the original purchase and renewal behavior. Credit-card renewals are especially important because RevCent can store the customer's payment method securely and use it for future renewals.

Subscriptions may connect to:

- credit-card Transactions,
- Customer Cards,
- PayPal Transactions,
- Offline Payments,
- payment recovery records,
- refunds,
- failed or declined renewal attempts,
- salvage/recovery opportunities.

This is why subscription billing belongs in the backend commerce system. The Subscription needs to understand not only the schedule, but also the customer, payment method, payment result, recovery options, and financial outcome.

## Payment Profiles and Gateway Behavior

Subscription renewal billing depends on the payment behavior attached through Subscription Profiles and Payment Profiles.

In plain language:

```text
Subscription Profile decides when renewal should happen.
Payment Profile helps decide how the renewal payment is attempted.
```

RevCent can also support gateway behavior for recurring payments, such as using a preferred or forced gateway depending on subscription settings and business needs.

This matters for merchants that manage multiple gateways, payment rules, and recurring revenue risk. It lets the business control how recurring charges are attempted instead of treating every renewal the same way.

## WooCommerce and Shops

For WooCommerce and other connected Shops, RevCent should be treated as the subscription billing backend.

The best mental model is:

```text
WooCommerce = storefront / cart / checkout surface
RevCent = subscription billing and commerce backend
```

WooCommerce can display and sell the Product, but RevCent should own the recurring billing lifecycle. This helps avoid duplicate billing systems, conflicting subscription states, duplicate emails, customer confusion, bad reporting, and fulfillment problems.

A WooCommerce subscription flow should work conceptually like this:

```text
Customer buys a subscription Product in WooCommerce
    ↓
RevCent receives the order/payment context
    ↓
RevCent creates the Sale and Product Sale
    ↓
RevCent creates the Subscription
    ↓
RevCent handles renewals, recovery, emails, fulfillment, customer support, and reporting
```

For businesses running WooCommerce, this makes RevCent the system of record for recurring revenue while WooCommerce remains the storefront.

## Shippable Subscriptions

Many ecommerce Subscriptions involve physical products.

Examples include supplements, skincare, coffee, pet products, subscription boxes, food, health products, replacement supplies, and recurring refills.

For shippable subscriptions, the Subscription connects billing to fulfillment.

A renewal can lead to:

```text
Subscription Renewal
    ↓
Payment attempt
    ↓
Shipping calculation
    ↓
Shipment creation
    ↓
Fulfillment Account notification
    ↓
Tracking and shipment status updates
    ↓
Customer shipment email and support visibility
```

This is a major benefit of RevCent. Recurring billing does not live separately from fulfillment. The Subscription can connect to the shipment lifecycle so the business understands not only whether the customer was charged, but also whether the recurring product was shipped.

## Subscription Shipping

Initial Sale shipping and renewal shipping can be different.

For example, a WooCommerce customer may choose a shipping method at checkout for the initial order. Later subscription renewals need RevCent to determine shipping for the recurring shipment.

Subscription Profiles and Shipping Profiles help control renewal shipping behavior.

This is important because recurring shipments need predictable shipping rules. A subscription box, supplement refill, or recurring physical product needs to know what shipping should be charged and how fulfillment should happen on each renewal.

## Refund Relationship

Subscriptions can connect to refunds in several ways.

A business may need to refund:

- a full Subscription Renewal,
- part of a renewal,
- a Product Sale connected to a Subscription,
- shipping connected to a renewal,
- tax connected to a renewal,
- a payment connected to subscription billing.

Refunds can create Pending Refund records. Those refund records help support, finance, and reporting understand what was refunded, why, and which Subscription or Subscription Renewal was involved.

This is especially important in recurring revenue because refunds can affect customer lifetime value, churn analysis, support workload, and recovery performance.

## Revenue Recovery

Revenue recovery is one of the biggest benefits of RevCent Subscriptions.

A failed renewal is not only a failure. It is a possible recovery opportunity.

When a renewal fails or becomes overdue, the business may be able to recover revenue through:

- payment update emails,
- Customer Portal payment updates,
- AI Assistant review,
- AI Voice Agent outreach,
- support follow-up,
- salvage workflows,
- retry logic where appropriate,
- custom retention offers,
- suspension instead of cancellation,
- future renewal timing changes.

Conceptually:

```text
Renewal fails
    ↓
Subscription becomes overdue or needs review
    ↓
RevCent records the context
    ↓
Email, AI, voice, portal, support, or salvage workflow attempts recovery
    ↓
Subscription is recovered, suspended, cancelled, or left for further review
```

This is a major advantage over basic recurring billing. RevCent helps turn failed renewal data into actionable retention workflows.

## Salvage Transactions and Failed Renewals

When a subscription renewal payment fails, RevCent may create recovery context through Salvage Transactions where applicable.

A Salvage Transaction represents revenue that may be recovered later after a failed or partially successful payment attempt.

For Subscriptions, salvage is valuable because recurring revenue is often recoverable. A customer may have insufficient funds today, an expired card, a temporary bank issue, or a payment method that needs to be updated.

A good recovery process does not blindly retry every failure. It reviews the decline reason, customer value, subscription status, timing, and customer contact options before deciding what to do next.

## Email Templates and Subscriptions

Email Templates are essential for subscription communication.

Subscription-related emails can include:

- upcoming renewal reminders,
- successful renewal confirmations,
- failed renewal notices,
- overdue subscription notices,
- payment update requests,
- cancellation confirmations,
- suspension notices,
- reactivation confirmations,
- shipment notifications for recurring products,
- trial expiration reminders,
- internal alerts for high-value subscription issues.

RevCent Email Templates are valuable because they can use RevCent's backend subscription context instead of relying only on storefront or plugin data.

For WooCommerce shops, RevCent should generally be the authoritative system for subscription lifecycle emails to avoid duplicate, incomplete, or conflicting customer communication.

## Functions and Subscriptions

Functions can extend subscription workflows into external systems.

Common examples include:

- notifying Slack when a high-value Subscription becomes overdue,
- creating a support ticket when a customer requests cancellation,
- sending subscription updates to a CRM,
- notifying operations about recurring shipment problems,
- calling an external retention platform,
- syncing subscription lifecycle changes to another business system.

Functions are best used as supplemental automation around the Subscription lifecycle. They help RevCent communicate with the rest of the business ecosystem.

## AI Assistants and Subscriptions

AI Assistants can help monitor, review, and act on subscription events.

They are useful because subscription decisions often require context. A failed renewal may be recoverable or hopeless. A cancellation may need a save attempt or a note. A high-value overdue customer may need a phone call. A custom-cycle request may need support review.

AI Assistants can help with:

- monitoring Subscription status changes,
- reviewing overdue Subscriptions,
- analyzing failed renewal context,
- deciding whether recovery is worthwhile,
- triggering Email Templates,
- triggering AI Voice Agents,
- creating notes,
- creating AI Memos,
- tagging records with metadata,
- routing issues to support or finance,
- reviewing salvage opportunities,
- summarizing Subscription history for customer support,
- running scheduled BigQuery-based subscription reviews.

In the relationship graph, AI Assistants act like reasoning-driven operators attached to Subscription lifecycle events.

## AI Voice Agents and Subscriptions

AI Voice Agents are useful for both inbound subscription support and outbound recovery.

Inbound examples include customers asking:

- When is my next renewal?
- Why was I charged?
- Can I pause my Subscription?
- Can I cancel?
- Can I update my payment method?
- Where is my subscription shipment?
- Can I change my renewal schedule?

Outbound examples include:

- calling a customer after a failed renewal,
- helping a customer update payment information,
- calling high-value customers before suspension,
- supporting failed trial conversion recovery,
- handling retention calls before cancellation,
- following up on shipment or refill issues.

AI Voice Agents should use RevCent Subscription data as the source of truth. They should not guess billing, payment, cancellation, or shipment status.

## Customer Portal and Self-Service

The Customer Portal can reduce support workload for subscription businesses.

Customers may need a place to:

- view account context,
- understand active Subscriptions,
- update payment information,
- review orders and renewals,
- manage support needs,
- access subscription-related account pages.

For WooCommerce stores, the Customer Portal can be embedded into the storefront while RevCent powers the backend subscription experience.

This creates a better customer experience because the storefront remains customer-facing, while RevCent handles subscription data, payments, renewals, and lifecycle logic.

## Bulk Subscription Management

RevCent includes bulk subscription management concepts for businesses that need to modify groups of Subscriptions.

This is useful when a business needs to manage subscriptions by:

- campaign,
- Product,
- Subscription Profile,
- status,
- payment profile,
- gateway behavior,
- next renewal date,
- metadata.

Bulk actions are powerful and should be used carefully. They can affect many customers at once, including renewal timing, status, metadata, or payment behavior.

From an ecosystem standpoint, bulk management is important because it lets a business manage recurring revenue as a portfolio instead of only one Subscription at a time.

## Business Benefits

Subscriptions help ecommerce businesses build recurring revenue and stronger customer relationships.

Key benefits include:

| Benefit | Why It Matters |
|---|---|
| Predictable revenue | Recurring billing creates more stable revenue forecasting. |
| Customer lifetime value | Subscribers can generate value over many renewal cycles. |
| Product stickiness | Recurring products keep customers connected to the business. |
| Replenishment automation | Physical products can be shipped again when customers need them. |
| Recovery workflows | Failed renewals can be recovered through email, AI, voice, and portal flows. |
| Better support visibility | Support can see status, renewals, payments, shipments, and refunds in one ecosystem. |
| Shop flexibility | WooCommerce can remain the storefront while RevCent manages the subscription backend. |
| Reporting depth | BigQuery can show lifecycle, renewal, churn, revenue, and recovery patterns. |
| Retention tooling | Suspend, activate, custom schedules, Customer Portal, AI, and voice help reduce churn. |

## BigQuery Relationship and Reporting Context

The `subscription` BigQuery table helps show how Subscriptions connect to other RevCent records.

At a business level, it can help connect Subscription activity to:

- Products,
- Subscription Profiles,
- Subscription Renewals,
- Customers,
- Sales,
- Product Sales,
- Trials,
- Third Party Shops,
- Campaigns,
- Shipping,
- Transactions,
- Payment recovery activity,
- Metadata,
- AI and voice workflows through related records.

BigQuery can support subscription reporting such as:

- active Subscriptions by status,
- recurring revenue by Product,
- recurring revenue by Subscription Profile,
- subscriptions by WooCommerce shop,
- overdue Subscriptions,
- failed renewal recovery opportunities,
- churn and cancellation patterns,
- subscription lifetime value,
- shippable subscription performance,
- renewal performance by campaign,
- subscription recovery outcomes,
- AI Assistant and AI Voice Agent recovery impact.

The goal is not to treat BigQuery as a schema reference inside this document. The goal is to understand that the `subscription` table is a relationship and reporting signal for recurring revenue across the RevCent ecosystem.

## Common Ecosystem Patterns

### Replenishment Product

```text
Product is sold as a recurring refill
    ↓
Subscription is created
    ↓
Each renewal creates payment and shipment context
    ↓
Fulfillment sends the customer the next refill
    ↓
Email, AI, voice, and reporting monitor the lifecycle
```

This works well for supplements, skincare, food, coffee, pet products, and other recurring physical goods.

### Subscription Box

```text
Customer buys subscription box Product
    ↓
Subscription controls recurring billing
    ↓
Subscription Renewals create recurring shipment needs
    ↓
Shipping and fulfillment records track delivery
    ↓
BigQuery reports box performance, churn, and fulfillment quality
```

This helps a business understand both revenue and operations.

### WooCommerce Storefront, RevCent Backend

```text
Customer checks out in WooCommerce
    ↓
RevCent creates Sale and Product Sale
    ↓
Subscription is created in RevCent
    ↓
RevCent manages future billing, recovery, emails, fulfillment, and reporting
```

This keeps WooCommerce as the storefront while RevCent manages the subscription engine.

### Failed Renewal Recovery

```text
Subscription Renewal fails
    ↓
Subscription becomes overdue
    ↓
AI Assistant reviews context
    ↓
Email Template or AI Voice Agent contacts customer
    ↓
Customer updates payment method through Customer Portal
    ↓
Subscription is recovered
```

This is one of the highest-value subscription workflows.

## Common Mistakes to Avoid

- Treating a Subscription as just a recurring charge instead of a full customer relationship.
- Creating subscription Products without clear Subscription Profile behavior.
- Using WooCommerce subscription plugins alongside RevCent subscription billing.
- Letting duplicate systems create conflicting subscription states or duplicate charges.
- Cancelling a Subscription when suspension would preserve the customer relationship.
- Forgetting that shippable Subscriptions need renewal shipping and fulfillment behavior.
- Ignoring overdue renewals instead of using recovery workflows.
- Retrying failed renewals without reviewing context.
- Sending duplicate lifecycle emails from both WooCommerce and RevCent.
- Treating BigQuery as a technical schema reference instead of a relationship/reporting layer.

## Ecosystem Summary

Subscriptions are the recurring billing backbone of RevCent.

They begin with Products and Subscription Profiles, then become customer-specific recurring relationships. Each renewal creates a Subscription Renewal, and each renewal can connect to payments, shipping, tax, refunds, recovery workflows, emails, AI, voice, customer support, and reporting.

For ecommerce businesses, Subscriptions are not only about charging customers again. They are about managing ongoing customer value, product replenishment, customer retention, payment recovery, recurring fulfillment, customer communication, and recurring revenue analytics.

In the RevCent ecosystem, Subscriptions connect:

```text
Product
    + Subscription Profile
    + Customer
    + Sale / Product Sale
    + Subscription Renewals
    + Payments
    + Shipping / Fulfillment
    + Trials
    + Refunds
    + Recovery Workflows
    + Email Templates
    + Functions
    + AI Assistants
    + AI Voice Agents
    + Customer Portal
    + Shops
    + BigQuery
```

A Subscription is the long-running customer relationship that turns a single purchase into recurring revenue.


---
Document Parent Directory
* [Items](https://revcent.com/documentation/markdown/ecosystem/item/index.md) - Non-technical markdown documentation for items within the RevCent ecosystem. An item is an entity that is spawned as a result of a feature or operation conducted within the RevCent ecosystem.