Sales commissions - Geo assignation
Configure sales agents assigning them to a specific geographical area.
Then, automatically assign agents to customers, according to their geographical area.
A “Do not allow update with Geo Assign” setting can be activated in partner to prevent server action from editing set agents.
Table of contents
Configuration
Go to
Sales > Commissions Management > Agents
A user must be in the ‘Contact Creation’ group in order to access this action
For every agent, you can set Countries, States or ZIP range
Usage
Go to Sales > Agents > open a record: in tab “Agent information”, set geographic criteria.
When using server action, this agent will be assigned to customers whose address match the set criteria.
To assign agents, go to:
Sales > Customers
Select the customers you want to assign agents to and click
Action > Add agents with geo assign
Activating flag “Replace existing agents” will remove agents set in partner and replace them according to geographic criteria.
Activating flag “Do not add new agents if agents are already assigned” will prevent assignation if agents are already set in partner.
Deactivating both flags will simply add agents to existing ones in partner according to geographic criteria.
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
iwkse <https://ooops404.com>
PyTech SRL <info@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-geo-assign 14.0.1.1.3
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_geo_assign-14.0.1.1.3-py3-none-any.whl | Python 3 | none | any | Details for odoo14_addon_sale_commission_geo_assign-14.0.1.1.3-py3-none-any.whl |
Release files / odoo14_addon_sale_commission_geo_assign-14.0.1.1.3-py3-none-any.whl
| Download URL | odoo14_addon_sale_commission_geo_assign-14.0.1.1.3-py3-none-any.whl |
|---|---|
| Size | 33.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
9cc0e2192407d2f146231e66b40236ccd440575256bb5fe7883db8a92d5e6204
|
|
BLAKE2b-256 checksum How to use checksums |
a6d5b36610d102e5674c3bb4ca57d3bb66a96bf22d169dcc3a8a3c6347dd1fba
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.1.1 CPython/3.12.3
|
Security for odoo14-addon-sale-commission-geo-assign 14.0.1.1.3
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.
