Skip to main content

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

This module provides different configuration option to manage packagings on purchase orders.

The creation/update of purchase order line will be blocked (by constraints) if the data on the purchase.order.line does not fit with the configuration of the product’s packagings.

It’s also possible to force the quantity to purchase during creation/modification of the purchase order line if the “Force purchase quantity” is ticked on the packaging and the “Purchase only by packaging” is ticked on product.

For example, if your packaging is set to purchase by 5 units and the employee fill the quantity with 3, the quantity will be automatically replaced by 5 (it always rounds up).

Table of contents

Configuration

Following options are available to define which packaging level can be purchased and which product can only be purchased by packaging.

  • Purchase only by packaging: On product template model, this checkbox restricts purchases of these products if no packaging is selected on the purchase order line. If no packaging is selected, it will either be auto-assigned if the quantity on the purchase order line matches a packaging quantity or an error will be raised.

  • Force purchase quantity (on the packaging): force rounds up the quantity during creation/modification of the purchase order line with the factor set on the packaging.

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

  • Camptocamp

  • BCIM

Contributors

Other credits

The development of this module has been financially supported by:

  • Camptocamp

This module feature was extracted from the original sale-workflow/sale_by_packaging module.

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.

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.

Release files for odoo-addon-purchase-only-by-packaging 16.0.1.0.2.3

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 odoo-addon-purchase-only-by-packaging 16.0.1.0.2.3
File Interpreter ABI Platform
odoo_addon_purchase_only_by_packaging-16.0.1.0.2.3-py3-none-any.whl Python 3 none any Details

Release files / odoo_addon_purchase_only_by_packaging-16.0.1.0.2.3-py3-none-any.whl

Download URL odoo_addon_purchase_only_by_packaging-16.0.1.0.2.3-py3-none-any.whl
Size 44.2 kB
Tags Python 3
SHA-256 checksum
How to use checksums
a2a4b5fbe9237019f98bc489aa41d5ad8d182b42933a8982caaddd71cb6ef149
BLAKE2b-256 checksum
How to use checksums
f9d0a9f559cf835e1c068c2e552c576a14c5c3e1617b2c723be62056fbb96743
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/6.2.0 CPython/3.12.3
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