Sale Commission Product Criteria
This module allows to set in the same Commission Type different commission rates according to the product on SO/invoice line.
This is made possible since this module adds a new “Product criteria” type to Commission Type and applies commission rates with the same logic of sale pricelist items.
For example, such a Commission Type can grant:
10% on a specific Product A, 10$ on Product B, 4% on products in Category 1 and 5$ on all other products.
In SO/invoice, system will apply different commissions based on variant/product/category or global, applied hierarchically. This means that for the example above, if product A is assigned to Category 1, commission assigned is 10%, as per variant/product/category/global rule application order.
Furthermore, these commission type items can be accessed and created by a specific menu, to facilitate their management in environments with lots of records.
The form for commission type item can be extended by future modules with further conditions to decide when to apply a specific item.
Table of contents
Usage
To use features of this module, you need to:
Go to Sales > Commission Management > Commission Types.
Create a Commission Type with type = “Product criteria”.
Create multiple rules based on variant/product/category or global
These rules will be sorted according to the same logic of sale pricelist.
Rest flow is according to OCA sale_commission module.
Bug Tracker
Bugs are tracked on GitHub Issues. In case of trouble, please check there if your issue has already been reported. If you spotted it first, help us to smash it by providing a detailed and welcomed feedback.
Do not contact contributors directly about support or help with technical issues.
Credits
Contributors
-
Ilyas <irazor147@gmail.com>
-
Simone Rubino <simone.rubino@pytech.it>
Maintainers
This module is maintained by the OCA.
OCA, or the Odoo Community Association, is a nonprofit organization whose mission is to support the collaborative development of Odoo features and promote its widespread use.
Current maintainers:
This module is part of the OCA/commission project on GitHub.
You are welcome to contribute. To learn how please visit https://odoo-community.org/page/Contribute.
1 maintainer
Metadata
1 maintainer
Release files for odoo14-addon-sale-commission-product-criteria 14.0.1.2.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| odoo14_addon_sale_commission_product_criteria-14.0.1.2.0-py3-none-any.whl | Python 3 | none | any | Details for odoo14_addon_sale_commission_product_criteria-14.0.1.2.0-py3-none-any.whl |
Release files / odoo14_addon_sale_commission_product_criteria-14.0.1.2.0-py3-none-any.whl
| Download URL | odoo14_addon_sale_commission_product_criteria-14.0.1.2.0-py3-none-any.whl |
|---|---|
| Size | 43.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
c9fb6c3e31252131f0887fe005e24a6a3337612bfcfa715bde261549001f7d46
|
|
BLAKE2b-256 checksum How to use checksums |
66127ca3658704e0657e3d064ba0d495fed8c1db735ac856363311aa907856ff
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.12.3
|
Security for odoo14-addon-sale-commission-product-criteria 14.0.1.2.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
