> For the complete documentation index, see [llms.txt](https://docs.b2b-sellers.com/b2b-platform/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.b2b-sellers.com/b2b-platform/1/user-guide/configuration/license-purchaseable-addons-and-features-configuration.md). # License, purchaseable Addons and Features configuration Everything you need to know to use features and addons {% hint style="info" %} Since version 1.0.4 you can store a LicenseID in the license settings. If you don't have it at hand, you can get your LicenseId here {% endhint %} ### Enable Features and Addons in Shopware Administration It couldn't be simpler. After the installation you can click in the administration in the main menu on B2B settings, then you come directly to the license settings.

Ease to manage features and addons in the B2Bsellers License Overview

#### What are the license restrictions? This page is divided into the license restrictions, which are, for example, the maximum number of Sales representatives. #### What are features? These are free features that you can easily activate and use. These are included in the CORE license. Once you activate a feature you can make "Config Settings" on the left side. Good to know: All settings are normal Shopware config.xml settings like in every plugin. {% hint style="info" %} You can use different settings in each saleschannel. {% endhint %} #### What are addons? Addons are paid functions (which have to be licensed additionally). With B2BsellersCore you get the complete source code of all B2Bsellers Suite features. --- # 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.b2b-sellers.com/b2b-platform/1/user-guide/configuration/license-purchaseable-addons-and-features-configuration.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.