Skip to main content
Pre-release

This release is a pre-release and may not be stable for production use.

Purchase Partner Approval

Alpha License: AGPL-3 OCA/purchase-workflow Translate me on Weblate Try me on Runboat

Require partners to be approved before thay can be used on Purchase 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 Purchase Order validation rules are configurable. By default Purchase Order confirmation is prevented is the Vendor or Drop Ship Address is not approvaed to be used in Purchase.

To configure Purchase Order validations navigate to Purchase / Configuration / Purchase Exception Rules. You need to belong to the Exception Manager security group to see this menu option.

For new vendor 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 Purchase”

  • Edit the “Draft” stage: check “Default Stage” and uncheck “Approved for Purchase”

Usage

To approve a Partner to be used in purchase:

  • Edit the Partner form, and in the “Sales & Purchase” tab check the “Candidate to Purchase” box.

  • Make sure the Parter is in a Stage that has the “Approved for Purchase” checkbox enabled. If this is the case, the Partner will automatically have enabled the “Can Purchase To” checkbox. found next to the “Candidate to Purchase” checkbox.

The “Candidate to Purchase” checkbox is only available in a draft/to approve Stage. The “Can Purchase 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 Purchase To”. This means that removing from Can Purchase state also needs to go through an approval.

On a Purchase Order:

  • The “Vendor” and “Drop Ship Address” selection lists only propose partners you “Can Purchase To”.

  • The CONFIRM button will show a blocking exception message if the selected Customeror Drop Ship Address do not have the “Can Purchase 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 to smash it by providing a detailed and welcomed feedback.

Do not contact contributors directly about support or help with technical issues.

Credits

Authors

  • Open Source Integrators

Contributors

Maintainers

This module is maintained by the OCA.

Odoo Community Association

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:

dreispt

This module is part of the OCA/purchase-workflow project on GitHub.

You are welcome to contribute. To learn how please visit https://odoo-community.org/page/Contribute.

Metadata

Release files for odoo14-addon-purchase-partner-approval 14.0.1.0.1.dev6

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Built distribution (wheel)

Table of built distributions (wheels) for odoo14-addon-purchase-partner-approval 14.0.1.0.1.dev6
File Interpreter ABI Platform Actions
odoo14_addon_purchase_partner_approval-14.0.1.0.1.dev6-py3-none-any.whl Python 3 none any Details for odoo14_addon_purchase_partner_approval-14.0.1.0.1.dev6-py3-none-any.whl

Release files / odoo14_addon_purchase_partner_approval-14.0.1.0.1.dev6-py3-none-any.whl

Download URL odoo14_addon_purchase_partner_approval-14.0.1.0.1.dev6-py3-none-any.whl
Size 33.2 kB
Tags Python 3
SHA-256 checksum
How to use checksums
2c1dd04e3fe3b717629eaf51879be3151ba4d68053e8c41978e2943f6c2b26f2
BLAKE2b-256 checksum
How to use checksums
98b250bf121a73517eaa7e784dfaab7c5d53ee1433b5c6aa921e57bd3d8dba06
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-purchase-partner-approval 14.0.1.0.1.dev6

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.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page