Require partners to be approved before thay can be used on Sales Orders.
This does not require, but was designed to be used with Partner Tier Validation (partner_tier_validation module).
Using that module, rules can be configured on who must approve, before the Partner Stage can be changed to an apptoved one.
Table of contents
Configuration
The Sales Order validation rules are configurable. By default Sale Order confirmation is prevented is the Customer or Invoice Address is not approvaed to be used in sales.
To configure Sales Order validations navigate to Sales / Configuration / Sales Orders / Sale Exception Rules. You need to belong to the Exception Manager security group to see this menu option.
For new customer to require approval before being sold to, configure the Contact Stages appropriately. For example:
Navigate to Contacts / Configuration / Contact Stages
Edit the “Active” stage: uncheck “Default Stage” and check “Approved for Sales”
Edit the “Draft” stage: check “Default Stage” and uncheck “Approved for Sales”
Usage
To approve a Partner to be used in sales:
Edit the Partner form, and in the “Sales & Purchase” tab check the “Candidate to Sell” box.
Make sure the Parter is in a Stage that has the “Approved for Sales” checkbox enabled. If this is the case, the Partner will automatically have enabled the “Can Sell To” checkbox. found next to the “Candidate to Sell” checkbox.
The “Candidate to Sell” checkbox is only available in a draft/to approve Stage. The “Can Sell To” will only be set when moving to a Stage that is not draft/to approve. Moving from an approved Stage to a draft one will not automatically reset the “Can Sell To”. This means that removing from Can Sale state also needs to go through an approval.
On a Sales Order:
The “Customer” and “Invoice Address” selection lists only propose partners you “Can Sell To”.
The CONFIRM button will show a blocking exception message if the selected Customeror Invoice Address do not have the “Can Sell To” flag checked (this may vary depending how the exception rules are configured).
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 smashing it by providing a detailed and welcomed feedback.
Do not contact contributors directly about support or help with technical issues.
Credits
Contributors
-
Daniel Reis <dreis@opensourceintegrators.com>
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 maintainer:
This module is part of the OCA/sale-workflow 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-partner-approval 14.0.2.0.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_partner_approval-14.0.2.0.0-py3-none-any.whl | Python 3 | none | any | Details for odoo14_addon_sale_partner_approval-14.0.2.0.0-py3-none-any.whl |
Release files / odoo14_addon_sale_partner_approval-14.0.2.0.0-py3-none-any.whl
| Download URL | odoo14_addon_sale_partner_approval-14.0.2.0.0-py3-none-any.whl |
|---|---|
| Size | 30.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
5e8aaeecd71233262fcf758c2a163c9ee216b1b5ebda891fd43113764169a2a7
|
|
BLAKE2b-256 checksum How to use checksums |
8006064746ef63548e99fe3d0a9101f2fa1565bb593d3df8e3308fc244370cad
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.3.0 pkginfo/1.7.0 requests/2.25.1 setuptools/60.3.1 requests-toolbelt/0.9.1 tqdm/4.58.0 CPython/3.8.5
|
Security for odoo14-addon-sale-partner-approval 14.0.2.0.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.
