> For the complete documentation index, see [llms.txt](https://docs.nalpeiron.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nalpeiron.com/zentitle2-docs/use-cases/use-case-directory/subscription-grace-periods.md). # Subscription grace periods Build a grace period into a subscription's expiration date so customers can keep using your application, notified via API status updates, while they renew after the official end date. {% embed url="" %} One of the most helpful features when managing subscription-based customers is building contingency into license expiration dates. Here's what we mean: If you have a one-year subscription starting January 1st and ending December 31st, the renewal process can be challenging since year-end is often chaotic. To address this, you can implement what we call a "grace period"—an extension built into the license itself. For example, a one-year subscription might officially expire on December 31st but include a grace period until January 14th. This allows customers to continue using your application through January 14th. During this grace period (January 1st–14th), your application will receive status updates through our APIs indicating that the customer is in a grace period. You can then notify the customer with messages like "You're in a grace period—please renew your license before January 14th." This provides additional flexibility in managing customer relationships. When processing the renewal, the system uses the official expiration date as the reference point. So, extending the license for another year will update from January 1st, 2024, to December 31st, 2024. We use the expiration date for all renewals and updates, but the grace period provides that crucial safety zone for working out arrangements with your customer. --- # 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.nalpeiron.com/zentitle2-docs/use-cases/use-case-directory/subscription-grace-periods.md?ask=&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.