> For the complete documentation index, see [llms.txt](https://docs.peakcommerce.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.peakcommerce.com/product/settings/billing-catalog/plan-entitlement-features.md). # Feature Vocabulary **Settings → Billing & Catalog → Feature vocabulary** is where you define the named capabilities and limits your application gates on — before you grant any of them to a plan. A feature here is a stable key your app checks at runtime ("does this account get advanced reporting?", "how many seats?"), independent of which plans currently include it. ## Adding a feature Use **New feature** to add one. Each feature is the vocabulary term your app reads — give it a clear name and the key it is **sent to your app as**, because that key is the contract: your code looks it up by that exact key, so it should not change once your app depends on it. Features start life unused — *No features yet. Add one to start gating your app on it.* — and stay that way until a plan grants them on the [**Plan Entitlements**](/product/settings/billing-catalog/plan-entitlements.md) screen. ## How it relates to plan entitlements Feature vocabulary is the **definition** layer; **Plan Entitlements** is the **grant** layer: * Define a feature once here (name + key + shape of its value). * Then, per plan, decide whether that feature is included and with what value on the Plan Entitlements grid. Keeping the vocabulary separate means the same feature can be granted differently across plans (off on one, a numeric limit on another, unlimited on a third) without redefining what the feature *is*. --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.peakcommerce.com/product/settings/billing-catalog/plan-entitlement-features.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.