When purchasing, users can indicate a usage from a list, for every item in the purchase order.
Usages can be associated with specific accounts. When the supplier invoice is created from that purchase order line, the account defined for that usage will be proposed, instead of the product's default expense account. This proposal will only be effective if the product is a consumable or a service.
Usages can be very diverse, like internal use, marketing use, testing use. So a product "Paper" could potentially translate to marketing expense, or an office expense, irrespective of what is the expense account defined in the product "Paper".
auto_awesome What this module does
AI-generated from the code · Odoo 14.0Lets buyers tag each purchase order line with a "usage" (e.g. marketing, internal use) and automatically proposes the expense account linked to that usage on the vendor bill.
This module adds a new concept called a Product Usage, which you can create and manage in Odoo. A usage has a description, an optional code, a company, an optional default product, and an optional expense account.
- On a purchase order line you can now pick a Usage next to the product. If the usage has a default product and the line has no product yet, that product is filled in automatically.
- When the vendor bill is created from the purchase order, the account defined on the usage is proposed on the invoice line instead of the product's normal expense account. This only applies when the purchase line is linked to the bill line.
- Usages are managed from Purchase > Configuration > Purchase Product Usages. The list shows code, description and account, and you can archive usages you no longer need.
- Only users in the "Define Purchase Product Usages" group (purchase managers get it automatically) can create or change usages; other purchase users can only view them.
The module touches purchase.order.line (new Usage field), account.move.line (account proposal) and adds the new purchase.product.usage model.
Depends on
Required by other modules
Menus it adds
Models and fields (3)
- account.move.line · extends an existing model
- purchase.order.line · extends an existing modelusage_id (Usage)
- purchase.product.usage · new modelcode (Code), name (Description), active, account_id (Account), company_id (Company), product_id (Default Product)
Text generated by AI (DeepSeek) from reading the Odoo 14.0 code on GitHub; it may contain mistakes, so check the code before deciding. View the code on GitHub
Availability by version
Reviewed: 2026-11-03Confirmation status: 3 confirmed, 6 with no information of 9 versions.
Sources · Odoo 14.0
Confirmed on 2026-11-03 in branch 14.0 of OCA/purchase-workflow.
terminal Installation and usage
OCA documentation · Odoo 14.0Configuration
Source · Odoo 14.0In order to be able to define usages, assign users to the group "Define Purchase Product Usages". The group is proposed by default to users in the group "Purchase Manager"
Go to Purchase / Configuration / Purchase Product Usages and define the usages, indicating the description and optionally the code, default product and account to use.
Usage
Source · Odoo 14.0In the PO line set the usage of the purchased product. If the usage has a default product it will be set in the PO line. If the product is a consumable or a service then the invoice will take the account from the usage. In any other case the normal behavior is expected.
No verified information in OCA: Installation.
Installation instructions, the distribution package, dependencies and configuration steps are not shown because they have not yet been verified in the module documentation for any version.
Data imported from GitHub: this sheet reflects the latest catalog review, not a live lookup. Always check the module documentation and staging before installing in production.