> For the complete documentation index, see [llms.txt](https://docs.codegiganten.de/plugin-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.codegiganten.de/plugin-documentation/en/apps/affiliate-marketing/configuration/standard-provision.md). # Standard provision #### Also give provisions for products that are not in affiliate product groups With this configuration, all products that are not in affiliate product groups can be provisioned/commissioned with a standard rate. If it has been deactivated, then only products from affiliate product groups will be commissioned. The default rate will of course be overridden by the values from affiliate product groups, if they have been set. This option can be helpful, for example, when importing products using dynamic product groups or categories is out of the question or when the product portfolio changes frequently. It is also used when all products receive the same rate - in this case it is possible to use the extension entirely without creating affiliate product groups. Standard provisions and affiliate product groups can be combined well, as mentioned before. #### Default provision rate (if enabled) If the configuration described above has been activated, the standard provision/commission rate can be set here as a percentage. The entry of 10, for example, corresponds to a 10 % provision on the product value. --- # 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.codegiganten.de/plugin-documentation/en/apps/affiliate-marketing/configuration/standard-provision.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.