Purchase Order Type
Adds a configurable type on the purchase orders. This type can be used in filters and groupbys.
Table of contents
Configuration
To configure this module, you need to:
Go to Purchases > Configuration > Purchase types
Modify / create the purchase order types
Enable Default on the order type a purchase order gets when its vendor has no order type. One default can be set per company, plus one for all companies.
To make an order type mandatory on purchase orders:
Go to Purchases > Configuration > Settings
Enable Require Purchase Order Type. The setting applies per company.
A purchase order then cannot be saved in the form without an order type. New installations do not require an order type. Upgraded installations keep requiring it for every existing company; companies created later do not require it until the setting is enabled.
Usage
To use this module, you need to:
Attribute a type when editing purchase orders
Known issues / Roadmap
Suggestion: add a default configuration attached to the types
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
Guewen Baconnier <guewen.baconnier@camptocamp.com>
Pimolnat Suntian <pimolnats@ecosoft.co.th>
Roger Sans <roger.sans@sygel.es>
Hudson Amadeus Leonardy <https://solusiaglis.co.id>
Bastian Guenther <Bastian.Guenther@ametras.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.
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 odoo-addon-purchase-order-type 19.0.3.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 | Reset |
|---|---|---|---|---|
| odoo_addon_purchase_order_type-19.0.3.0.0-py3-none-any.whl | Python 3 | none | any | Details |
Release files / odoo_addon_purchase_order_type-19.0.3.0.0-py3-none-any.whl
| Download URL | odoo_addon_purchase_order_type-19.0.3.0.0-py3-none-any.whl |
|---|---|
| Size | 128.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
ffd352501da968938933bd31cfeb8e98143f3f2c97d5c1edbd38d75a7162b071
|
|
BLAKE2b-256 checksum How to use checksums |
51f42c6b1102aeeb42bcc82d8e772066eb6a94ad110eda85edd595e1777956a0
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.14.4
|
Security for odoo-addon-purchase-order-type 19.0.3.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.