--- title: "Subscription Renewals" description: "A non-technical ecosystem overview of Subscription Renewals in RevCent, focused on how individual recurring billing events connect Products, Subscriptions, Subscription Profiles, customers, payments, shipping, refunds, recovery workflows, Email Templates, Functions, AI, voice, shops, and BigQuery relationship/reporting context." type: "item" company: "RevCent" canonical: "https://revcent.com/documentation/markdown/ecosystem/item/SubscriptionRenewal.md" relationships: - name: "Product" url: "https://revcent.com/documentation/markdown/ecosystem/feature/Product.md" - name: "Subscription" url: "https://revcent.com/documentation/markdown/ecosystem/item/Subscription.md" - name: "Subscription Profile" url: "https://revcent.com/documentation/markdown/ecosystem/feature/SubscriptionProfile.md" technical_links: web_app: "https://kb.revcent.com/en/revenue/subscription/subscription-renewal" api: section: "https://revcent.com/docs/api/v2#section-subscription_renewals" operations: - name: "Get Subscription Renewals" operation_id: "GetSubscriptionRenewals" operation: "https://revcent.com/docs/api/v2#operation-GetSubscriptionRenewals" schema: "https://revcent.com/documentation/files/api/operation/GetSubscriptionRenewals.json" - name: "Get A Subscription Renewal" operation_id: "GetSubscriptionRenewal" operation: "https://revcent.com/docs/api/v2#operation-GetSubscriptionRenewal" schema: "https://revcent.com/documentation/files/api/operation/GetSubscriptionRenewal.json" - name: "Refund A Subscription Renewal" operation_id: "RefundSubscriptionRenewal" operation: "https://revcent.com/docs/api/v2#operation-RefundSubscriptionRenewal" schema: "https://revcent.com/documentation/files/api/operation/RefundSubscriptionRenewal.json" mcp: overview: "https://revcent.com/documentation/markdown/mcp/operation/OverviewSubscriptionRenewal.md" operations: - name: "Get Subscription Renewals" operation_id: "GetSubscriptionRenewals" markdown: "https://revcent.com/documentation/markdown/mcp/operation/GetSubscriptionRenewals.md" available_via_ai: true - name: "Get A Subscription Renewal" operation_id: "GetSubscriptionRenewal" markdown: "https://revcent.com/documentation/markdown/mcp/operation/GetSubscriptionRenewal.md" available_via_ai: true - name: "Refund A Subscription Renewal" operation_id: "RefundSubscriptionRenewal" markdown: "https://revcent.com/documentation/markdown/mcp/operation/RefundSubscriptionRenewal.md" available_via_ai: true bigquery_schema: "https://revcent.com/documentation/files/bigquery/dataset.json" bigquery_tables: - "subscription_renewal" --- # Subscription Renewals Subscription Renewals are the individual recurring billing events inside a RevCent Subscription. A Subscription represents the customer's ongoing recurring billing relationship. A Subscription Profile defines the schedule and renewal rules. A Subscription Renewal is what happens each time that recurring relationship reaches a billing cycle and RevCent attempts to renew it. In business terms, Subscription Renewals are the heartbeat of recurring revenue. They show whether recurring revenue is actually being collected, whether a customer is staying active, whether a product is performing over time, whether payment recovery is needed, and whether fulfillment should happen again for shippable subscription products. For ecosystem graphing, Subscription Renewals are important because they connect the long-running Subscription to real recurring activity: payments, shipments, tax, discounts, refunds, failed-payment recovery, customer communication, AI automation, voice recovery, support workflows, and reporting. ## Why Subscription Renewals Are an Item Subscription Renewals are an item because they are created as individual records from real subscription lifecycle activity. A business creates Products and Subscription Profiles as reusable configuration. A customer purchases a subscription Product, which creates a Subscription. After that, each renewal cycle creates a Subscription Renewal. The distinction is important: - Product is what the business sells. - Subscription Profile is how recurring billing should behave. - Subscription is the customer's recurring billing relationship. - Subscription Renewal is one recurring billing cycle or renewal attempt inside that relationship. A Subscription can exist for months or years. A Subscription Renewal represents one specific moment in that ongoing lifecycle. That makes Subscription Renewals especially useful for reporting and relationship graphing. They let a business look beyond the existence of a Subscription and see the recurring events that actually produce revenue, failures, refunds, shipments, recovery activity, and customer outcomes. ## Core Purpose The core purpose of a Subscription Renewal is to represent one renewal cycle for a Subscription. A Subscription Renewal helps RevCent and the business understand: - Which Subscription reached a renewal cycle. - Which Product is being renewed. - Which Subscription Profile shaped the renewal timing. - Which customer is involved. - Whether the renewal succeeded or became overdue. - Which payment records were created or attempted. - Whether a salvage or recovery opportunity was created. - Whether shipping, tax, discounts, or refunds are connected. - Whether the renewal produced customer communication or internal alerts. - Whether AI or voice workflows reviewed, recovered, or escalated the renewal. - How the renewal contributes to revenue, churn, retention, and lifetime value. This makes Subscription Renewals one of the clearest signals of recurring revenue health in RevCent. ## Where Subscription Renewals Fit in the RevCent Ecosystem Subscription Renewals sit inside the recurring revenue layer of RevCent. A Product can be configured for subscription billing through a Subscription Profile. When that Product is sold, RevCent creates a Subscription. Each time the Subscription reaches its scheduled renewal point, RevCent creates a Subscription Renewal. In the relationship graph, Subscription Renewals connect outward to: - Products being renewed. - Subscription Profiles that define renewal behavior. - Parent Subscriptions that own the recurring relationship. - Customers being billed. - Product Sales and Sales that started the relationship. - Third Party Shops, including WooCommerce stores, when the original subscription came from a connected shop. - Campaigns and source context. - Payment records such as Transactions, PayPal Transactions, Offline Payments, and checks where applicable. - Shipping records for recurring shipments. - Tax and discounts attached to renewal activity. - Pending Refunds when a renewal is refunded. - Salvage Transactions when renewal payment recovery is possible. - Chargebacks and fraud/risk records where applicable. - Email Templates used for lifecycle communication. - Functions used to connect renewal activity to external systems. - AI Assistants and AI Voice Agents used for recovery, support, and retention. - Customer Portal workflows used for payment updates and self-service. - BigQuery reporting that measures renewal performance and recurring revenue. This makes the Subscription Renewal item a dense relationship node. It is not just a billing record. It is a recurring commerce event that ties together product, customer, payment, fulfillment, support, automation, and analytics. ## Relationship to Products Subscription Renewals always trace back to the Product being renewed. The Product explains what the customer is receiving. The Subscription Renewal shows that the Product reached another recurring billing cycle. This relationship matters because recurring revenue is product-specific. A business needs to know which Products are renewing successfully, which Products create the most overdue renewals, which Products create the most refunds, and which Products need better recovery, shipping, or retention workflows. Product-level renewal visibility helps answer questions such as: - Which subscription Products renew most reliably? - Which Products create the most recurring revenue? - Which Products have the highest failed-renewal rate? - Which Products lead to recurring shipment issues? - Which Products produce the most refunds or chargebacks after renewal? - Which Products are best suited for AI or voice recovery workflows? This is why Subscription Renewals are essential for understanding Product performance over time. The initial Sale shows acquisition. Subscription Renewals show ongoing value. ## Relationship to Subscription Profiles A Subscription Profile defines how renewal behavior should work. The Subscription Profile answers questions such as: - How often should the Subscription renew? - Is the renewal schedule based on days, weeks, months, calendar timing, or fiscal timing? - Should the Subscription renew indefinitely or stop after a set number of occurrences? - How many overdue renewals should be allowed before suspension? - Which Payment Profile should process renewal billing? - Should special shipping behavior apply for shippable subscription Products? A Subscription Renewal is the event produced by those rules. If a Subscription Profile says the Subscription renews every 30 days, the Subscription Renewal is the recurring record created for that cycle. If the profile defines a finite installment plan, each Subscription Renewal represents one installment cycle. If the profile has custom customer-specific timing, each renewal reflects that custom schedule. This relationship is important because renewal outcomes are often profile-driven. A poor renewal schedule, overly aggressive overdue behavior, unclear payment routing, or mismatched shipping strategy can affect recurring revenue. BigQuery reporting can help compare Subscription Profile performance by renewal success, failure, refund rate, recovery rate, and customer retention. ## Relationship to Subscriptions A Subscription Renewal belongs to a parent Subscription. The Subscription is the long-running customer relationship. The Subscription Renewal is one cycle within that relationship. A customer may have one Subscription with many Subscription Renewals over time. Each renewal becomes part of the Subscription's history and helps tell the story of the customer's recurring relationship. For example, a Subscription's history may show: - Successful early renewals. - One failed renewal due to a payment issue. - A recovery attempt using Email Templates or Customer Portal. - A salvage transaction that later recovered the payment. - A recurring shipment created after a successful renewal. - A refund on one renewal. - A later suspension or cancellation. Without Subscription Renewals, the Subscription only shows the overall relationship. With Subscription Renewals, the business can see the recurring events that shaped that relationship. ## Automatic Renewal Billing RevCent automatically handles scheduled subscription renewal billing. When a Subscription reaches its next renewal point, RevCent uses the Subscription Profile and payment context to create and process the renewal. The customer does not need to re-enter payment information for every credit-card renewal because RevCent can use stored payment data inside its PCI Level 1 environment. For ecommerce businesses, this is a major reason to use RevCent as the subscription billing backend. RevCent is not just tracking recurring orders. It is managing the recurring billing lifecycle, payment attempts, recovery context, shipments, refunds, support visibility, and reporting around those renewals. This is especially important for WooCommerce stores. WooCommerce can remain the storefront and checkout surface, while RevCent owns the subscription billing backend. That helps avoid duplicate billing, conflicting subscription states, inconsistent emails, and fragmented reporting. ## Manual Renewal Context Most Subscription Renewals are created by RevCent's automatic renewal process. Manual renewal is different. A manual renewal means someone intentionally wants to renew the Subscription now, usually because the customer requested an immediate renewal, an early refill, an authorized support action, or a controlled recovery attempt. Manual renewal should not be treated as a status check, a reporting tool, or a casual retry button. It can charge the customer immediately and may affect the future renewal schedule because the next renewal date can be based on the manual renewal date and the Subscription Profile's timing rules. In a non-technical ecosystem sense, the rule is simple: automatic renewals are the normal path; manual renewal is an intentional business action. ## Successful Renewals A successful Subscription Renewal means the recurring billing cycle produced a successful payment outcome. Successful renewals can create or connect to: - Revenue for the Product and Subscription. - Payment records. - Shipping records for shippable subscription Products. - Tax and discount records. - Customer lifetime value updates. - Email Templates confirming renewal success. - Customer Portal history. - Product and Subscription reporting. - Campaign and shop reporting. Successful renewals are the foundation of recurring revenue. They show that a customer continued the relationship and that the business successfully captured another cycle of value. ## Failed or Overdue Renewals A failed Subscription Renewal does not just represent a failed payment. It represents a recoverable moment in the customer lifecycle. When a renewal fails, the Subscription may become overdue or gain overdue renewal context. That failure can trigger support, communication, recovery, and automation workflows. Failed renewals can happen for many reasons, such as insufficient funds, expired cards, bank declines, disabled payment methods, gateway issues, or other payment problems. Some failures are recoverable. Others should not be retried aggressively. This is why Subscription Renewals are critical to revenue recovery. They give RevCent and the business a concrete event to review, classify, communicate about, and potentially recover. Failed or overdue renewals can connect to: - Email Templates that notify the customer. - Customer Portal links for payment updates. - AI Assistants that classify recoverability. - AI Voice Agents that call eligible customers. - Functions that notify external systems. - Salvage Transactions that represent recoverable revenue. - Notes or Metadata that preserve support context. - BigQuery reporting that measures failure and recovery patterns. The best recurring revenue businesses treat failed renewals as structured recovery opportunities, not as simple dead ends. ## Relationship to Payments Subscription Renewals connect recurring billing to payment records. Depending on the payment type and configuration, a renewal can relate to: - Credit-card Transactions. - PayPal Transactions. - Offline Payments. - Check records. - Pending Refunds. - Chargebacks. - Salvage Transactions. Payment context matters because not every payment type behaves the same way. Credit-card renewals can use stored payment data and Payment Profiles. PayPal renewals depend on PayPal-related configuration and records. Offline or alternate payments may have different refund, recovery, and support behavior. For relationship graphing, Subscription Renewals are the bridge between a customer's recurring relationship and the actual payment activity that happened during a specific cycle. ## Relationship to Salvage Transactions and Revenue Recovery One of the most important relationships for Subscription Renewals is the relationship to Salvage Transactions. When a renewal payment fails or is only partially successful, RevCent may create a Salvage Transaction where recovery is possible. The Salvage Transaction represents revenue that may be recovered later after the right wait period, communication, or payment update. This matters because subscription revenue is often recovered after the first failure. A customer may update a card. Funds may become available. A bank decline may be temporary. A customer may respond to an email or call. A good recovery workflow can involve: - Renewal failure is detected. - Customer context is reviewed. - Decline or payment issue is evaluated. - Email Template sends a payment update message. - Customer Portal gives the customer a safe way to update payment details. - AI Assistant determines whether recovery is worthwhile. - AI Voice Agent calls high-value or eligible customers. - Function notifies a CRM or support system. - Salvage recovery is attempted only when appropriate. - Outcome is stored for future reporting. This turns Subscription Renewals into a core revenue-recovery signal. ## Relationship to Shipping and Fulfillment Many subscription businesses sell shippable Products: supplements, coffee, beauty products, subscription boxes, replenishment goods, pet products, or other recurring physical items. When a shippable Subscription renews successfully, RevCent may create Shipping records and fulfillment activity for that renewal. This creates an important business distinction: - The initial shop purchase may use shipping information from the checkout experience. - Future subscription renewals need RevCent to calculate and manage recurring shipment behavior. For this reason, Subscription Renewals connect recurring billing to fulfillment operations. A renewal may succeed financially, but the business still needs the product shipped, tracking created, fulfillment updated, and customer communication sent. Subscription Renewal visibility helps identify: - Renewals that created shipments. - Renewals that should have created shipments but did not. - Shippable subscription Products with fulfillment issues. - Recurring shipment delays. - Renewal shipments that need customer communication. - Product or Subscription Profile configurations that may need shipping review. ## Relationship to Tax and Discounts Subscription Renewals can also connect to Tax and Discount records. This matters because recurring revenue is not always a simple gross amount. A renewal can include taxes, discounts, coupons, refunded portions, fees, or other adjustments. For ecommerce businesses, this allows more accurate recurring revenue reporting. Instead of only asking whether a renewal happened, a business can understand the real economics of the renewal: what was charged, what was discounted, what was refunded, what was taxable, and what net value remained. This is especially useful for reporting by Product, Subscription Profile, shop, campaign, customer segment, or billing model. ## Relationship to Pending Refunds Subscription Renewals can be refunded. When a renewal is refunded, a Pending Refund record can connect the refund back to the renewal and related items such as Product Sales, Shipping, Tax, Transactions, PayPal Transactions, or Offline Payments. This relationship is important because subscription refunds often need to be understood at the renewal level. A customer may not be refunding the entire Subscription history. They may be refunding one renewal cycle, one shipment, one tax amount, or one payment event. Subscription Renewal refund visibility helps support and finance teams understand: - Which renewal was refunded. - Whether the refund was full or partial. - Whether product, shipping, or tax portions were involved. - Which payment processor or payment record was connected. - How refunds affect recurring revenue metrics. - Whether certain Products or profiles create higher renewal refund rates. ## Relationship to Chargebacks, Fraud, and Risk Subscription Renewals can also connect to chargeback or risk context when disputes or fraud-related events occur around renewal payments. This is important because recurring billing can create different risk patterns than initial purchases. A customer may forget about a renewal, dispute a charge, or contact support after a recurring payment. A failed or disputed renewal may also reveal product, messaging, timing, or customer expectation issues. By connecting renewal records to chargebacks, risk signals, customers, Products, shops, and campaigns, RevCent gives businesses a clearer view of recurring revenue quality. This can help answer questions such as: - Which Products create the most renewal disputes? - Which Subscription Profiles have higher chargeback risk? - Are customers disputing because renewal timing is unclear? - Do certain shops, campaigns, or offers create higher renewal friction? - Should Email Templates warn customers earlier before renewal? ## Relationship to Customers Every Subscription Renewal is part of a customer relationship. Renewal history helps support teams understand where a customer is in the subscription lifecycle. It can show whether a customer has been renewing successfully, whether they are overdue, whether they have recurring payment issues, whether they received shipments, whether they requested refunds, and whether recovery workflows have already been attempted. This is valuable for customer support because a customer may ask: - Why was I charged? - When did my subscription renew? - Why did my renewal fail? - When will my renewal shipment arrive? - Can I update my payment method? - Can I pause, cancel, or restart my subscription? - Can I get a refund for this renewal? Subscription Renewals give support, AI, voice, and Customer Portal experiences the context needed to answer those questions accurately. ## Relationship to Shops and WooCommerce Subscription Renewals can retain shop context when the subscription originated from a connected Third Party Shop such as WooCommerce. This matters because many ecommerce businesses want WooCommerce to remain the storefront, while RevCent manages the subscription billing backend. In that model: - WooCommerce presents the storefront and checkout experience. - RevCent stores and manages the Product, Subscription, and Subscription Profile relationship. - RevCent handles future Subscription Renewals. - RevCent manages renewal payment attempts, recovery, fulfillment, refunds, customer communication, and reporting. This gives a shop-level view of recurring revenue. A business can understand renewal revenue, failed renewals, recovery outcomes, refunds, and fulfillment issues by WooCommerce store or other shop source. It also helps prevent the operational confusion that can happen when WooCommerce subscription plugins and RevCent both try to manage recurring billing. When RevCent is connected, RevCent should be treated as the subscription billing system of record. ## Relationship to Email Templates Email Templates are a major part of Subscription Renewal communication. Renewal-related email workflows may include: - Upcoming renewal notices. - Successful renewal confirmations. - Failed renewal notices. - Payment update reminders. - Overdue subscription notices. - Recurring shipment confirmations. - Recurring shipment tracking emails. - Refund confirmations. - Cancellation or suspension notices. - Internal alerts for high-value failed renewals. Because RevCent has the authoritative renewal, payment, customer, Product, and shipment context, RevCent Email Templates are often better suited than shop-only emails for subscription lifecycle communication. For relationship graphing, Email Templates connect Subscription Renewals to customer communication and recovery behavior. ## Relationship to Functions Functions can connect Subscription Renewal events to external systems or custom business logic. A business may use Functions to: - Notify a support system when a renewal fails. - Send high-value renewal failures to a CRM. - Add renewal outcomes to internal analytics systems. - Trigger custom webhook-style workflows. - Notify fulfillment or operations teams about renewal shipment exceptions. - Route special subscription cases to internal teams. Functions should be seen as the extension layer around Subscription Renewals. They help the business connect renewal events to systems outside RevCent while RevCent remains the source of truth for the renewal relationship. ## Relationship to AI Assistants AI Assistants can make Subscription Renewal workflows more intelligent. A failed renewal is not always worth the same response. Some customers are high value. Some declines are recoverable. Some payment failures should be skipped. Some renewal shipments need review. Some customers should receive email, while others may need voice follow-up or human support. AI Assistants can help by reviewing the renewal and its surrounding graph: - Customer history. - Product and Product Group. - Subscription Profile. - Payment type. - Decline or overdue context. - Salvage Transaction availability. - Prior recovery attempts. - Refund or chargeback history. - Shop or campaign source. - Shipping and fulfillment context. - Customer value. Based on that context, an AI Assistant can decide whether to send an Email Template, trigger a Voice Agent, create a note, create an AI Memo, call a Function, wait before recovery, or skip an unrecoverable case. This makes Subscription Renewals one of the strongest use cases for AI Assistants in RevCent because they combine customer value, recurring revenue, payment outcomes, and operational urgency. ## Relationship to AI Voice Agents AI Voice Agents can support Subscription Renewals through inbound customer service and outbound recovery. Inbound voice use cases include: - A customer asks why a renewal happened. - A customer asks when the next renewal is due. - A customer asks why a renewal failed. - A customer wants help updating payment information. - A customer asks about a renewal shipment. - A customer wants to pause, cancel, or restart a Subscription. - A customer wants a custom renewal cycle. Outbound voice use cases include: - Calling eligible customers after failed renewals. - Recovering overdue subscription revenue. - Helping customers update payment methods. - Contacting high-value customers before suspension. - Following up on salvage recovery opportunities. - Supporting trial-to-subscription conversion recovery. The best pattern is to use AI Assistants for backend reasoning and AI Voice Agents for live customer conversations. The Assistant can decide whether a renewal is appropriate for voice follow-up, while the Voice Agent handles the customer interaction. ## Relationship to Customer Portal Customer Portal is important for Subscription Renewal recovery and self-service. When a renewal fails, customers often need a safe way to update payment information, view subscription status, understand renewal history, or confirm account details. Customer Portal can reduce support friction by giving customers a place to resolve common subscription issues. Email Templates and AI Voice Agents can point customers toward Customer Portal when self-service is appropriate. For relationship graphing, Customer Portal connects Subscription Renewals to customer self-service, payment updates, support reduction, and retention. ## Relationship to BigQuery Reporting The `subscription_renewal` table in BigQuery gives businesses relationship and reporting visibility into recurring billing events. This table can help answer business questions such as: - How much recurring revenue came from renewals over time? - Which Products generate the most renewal revenue? - Which Subscription Profiles perform best? - Which shops or campaigns create the strongest recurring revenue? - Which renewals failed or became overdue? - Which renewal failures later recovered through salvage workflows? - Which Products create the most renewal refunds? - Which renewal cycles produce shipment issues? - Which customers have repeated renewal failures? - Which AI Assistant or AI Voice Agent workflows improve recovery outcomes? - Which Subscription Profiles should be adjusted because renewal performance is weak? BigQuery is especially valuable because Subscription Renewals connect to many other tables in the RevCent ecosystem, including Products, Subscriptions, Subscription Profiles, Customers, Sales, Product Sales, Shipping, Tax, Discounts, Transactions, Salvage Transactions, Pending Refunds, Chargebacks, Shops, Campaigns, AI Voice Calls, and related automation context. The purpose of BigQuery here is not just raw analytics. It is relationship visibility. It lets a business see how renewal events connect across the whole RevCent graph. ## API, MCP, and AI Context Subscription Renewals can be accessed through the RevCent web app, API, MCP, and AI-enabled workflows. In the web app, users can view Subscription Renewals and inspect renewal-related activity. Through API and MCP, systems and AI tools can retrieve renewal records for operational review. AI Assistants and AI Voice Agents can use renewal context to support customers, recover failed payments, and explain subscription status. For reporting, BigQuery is the better path. Operational retrieval is useful when a user or workflow needs to inspect a specific renewal or a limited set of renewals. BigQuery is better for revenue trends, performance comparisons, failure rates, refund rates, recovery measurement, and relationship graph analysis. ## Business Benefits Subscription Renewals help ecommerce businesses manage recurring revenue with more precision. Key benefits include: - Clear visibility into recurring billing activity. - Product-level recurring revenue measurement. - Subscription Profile performance analysis. - Better failed-payment recovery. - More accurate customer support context. - Renewal-specific refund visibility. - Recurring shipment and fulfillment tracking. - Shop and campaign performance reporting. - Better customer communication through Email Templates. - Smarter automation through Functions and AI Assistants. - Voice-based recovery and support through AI Voice Agents. - Customer self-service through Customer Portal. - BigQuery reporting across revenue, churn, recovery, fulfillment, and retention. Subscription Renewals make recurring revenue observable. They turn subscription billing from a hidden background process into a measurable, actionable part of the RevCent ecosystem. ## Ecosystem Relationship Summary Subscription Renewals are connected to many parts of RevCent: - Product: the item being renewed. - Subscription Profile: the rule set that determines renewal timing and behavior. - Subscription: the customer-level recurring relationship that owns the renewal. - Customer: the person or account being billed. - Sale and Product Sale: the original commerce context and line-item history. - Third Party Shop: the store or WooCommerce source when applicable. - Payment records: the actual payment activity for the renewal. - Shipping: recurring fulfillment for shippable subscription Products. - Tax and Discounts: financial adjustments around the renewal. - Pending Refunds: refund workflows tied to a specific renewal. - Salvage Transactions: recovery opportunities from failed or partial renewal attempts. - Chargebacks and risk records: dispute or fraud context when applicable. - Email Templates: customer and internal communication. - Functions: external automation and integrations. - AI Assistants: reasoning-driven recovery, review, and support automation. - AI Voice Agents: customer conversations and renewal recovery calls. - Customer Portal: payment update and self-service support. - BigQuery: reporting and relationship visibility across the entire renewal graph. ## Summary Subscription Renewals are the recurring billing events that make RevCent Subscriptions measurable, recoverable, and operationally useful. A Subscription is the customer's ongoing recurring relationship. A Subscription Profile defines how that relationship should renew. A Subscription Renewal is one actual renewal cycle or renewal attempt inside that relationship. This item is pivotal for recurring revenue businesses because it connects Products, customers, payment outcomes, failed-renewal recovery, refunds, shipments, communication, AI, voice, support, shops, campaigns, and BigQuery reporting. In the RevCent ecosystem, Subscription Renewals are where recurring billing becomes visible. They show what renewed, what failed, what was recovered, what was shipped, what was refunded, and where the business can improve retention and recurring revenue performance. --- 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.