One approval workflow, every document that touches a product
Gate products, sales orders, purchase orders and invoices behind a single configurable approval framework — with conditional routing, multi-level sign-off and a consolidated queue every approver can act from.
Odoo lets any user with product-creation rights add a product that is instantly orderable, purchasable and invoiceable — with no review step for pricing errors, incomplete specs, or unvetted vendors. Sales orders, purchase orders and invoices referencing that product carry no control gate either, so mistakes and non-compliant sourcing flow straight through to customers, vendors and the books.
Product Approval holds new and edited products in a review state until a Product or Purchasing Manager signs off, then extends that same discipline to sales order confirmation, purchase order confirmation and invoice posting. Conditional rules route each document to the right approver by category, value or partner, and every approver works from one consolidated queue.
Everything a control gate needs
Every capability below is implemented in the module.
Draft/hold product state
Products created by non-managers enter a "To Approve" state that blocks their use in sales, purchasing and invoicing until an approver signs off.
Conditional, rule-based routing
Configure routing rules by product category, order value and partner tag so low-risk records skip steps that high-risk ones require.
Multi-level approval sequencing
Define one or several ordered steps per rule (e.g. Product Manager, then Purchasing) so higher-risk records pass through more checkpoints.
Exclusive approval enforcement
A user who approves one stage of a workflow is automatically barred from approving a later stage on the same record.
Consolidated approval queue
One kanban and list view shows every pending product, sales order, purchase order and invoice approval, with mass approve and mass reject actions.
Cross-document blocking
Sales order confirmation, purchase order confirmation and invoice posting are all blocked while a referenced product is still pending approval.
Sales credit-limit validation
Sales orders can be checked against a customer's credit limit as part of the approval gate, routing over-limit orders to a Product Manager review.
Required rejection reasons
Rejecting a request requires a written reason, surfaced directly to the submitter and logged permanently on the record's chatter.
Configurable notification preferences
Each approver chooses immediate, daily digest or no notifications for approval activity, right from their user preferences.
How it works
Configure rules
An administrator defines routing rules per document type — category, value threshold, partner tag — and the ordered approval steps for each.
Record enters review
A new product, or a sales order, purchase order or invoice that matches a rule, is held and a request is submitted with the matching rule's steps.
Approvers act from the queue
Approvers see their pending items in the consolidated queue and approve or reject — with a required reason on rejection — one at a time or in bulk.
Document unblocks
Once every step is approved the source record is marked Approved and the sale, purchase or invoice can proceed — all logged in the chatter audit trail.
See it in action
The consolidated queue, configurable rules, and approval status on the product itself.
The consolidated Approval Queue kanban — every pending product, sales order, purchase order and invoice approval in one place, grouped by state.
The same queue as a list, with document type, amount, requester and current step visible at a glance — ready for mass approve or mass reject.
An individual approval request mid-workflow, showing the ordered Approval Steps notebook and the full chatter audit trail.
Configured approval rules by document type, ready to route products, sales orders, purchase orders and invoices differently by condition.
A two-step rule form — category and threshold conditions on top, the ordered approval steps in the Steps notebook below.
A pending product's own form — approval state statusbar, Submit for Approval button, and a smart button straight to its approval requests.
The approval state is integrated directly into the product catalog list, so catalog managers see review status without opening each record.
Frequently asked
Which documents can this module gate?
Products, sales orders, purchase orders and customer/vendor invoices. Each document type has its own routing rules and can be gated independently.
Will this break existing admin or automated workflows?
No. Users who hold the Approval Administrator role — including Administrator — are exempt from the auto-hold on creation, so scripted imports and other modules that create products as admin are unaffected.
Can the same person approve every step of a workflow?
No. Exclusive approval enforcement bars a user who already approved an earlier step from acting on a later step of the same request.
What happens if a rejected product is edited and resubmitted?
A rejection is recorded with its reason on the record's audit trail. Editing the governed price field on an already-approved product automatically sends it back to review and opens a fresh approval request.
Get in Touch
Have questions or need customization? Every purchase includes 30 days of free support — we are here to help.
Visit Our Website
www.cerevantix.comExplore our apps, services, and portfolio.
Explore our other apps
A growing suite of Odoo apps.
Empowering growth through technology.
A unified, conditional approval framework for products, sales orders, purchase orders and invoices — with multi-level routing, a consolidated approval queue and a full audit trail.
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Discuss (mail)
• Invoicing (account) • Purchase (purchase) • Sales (sale_management) |
| Lines of code | 1169 |
| Technical Name |
cerevantix_product_approval |
| License | OPL-1 |
| Website | https://cerevantix.com |
Odoo Proprietary License v1.0 This software and associated files (the "Software") may only be used (executed, modified, executed after modifications) if you have purchased a valid license from the authors, typically via Odoo Apps, or if you have received a written agreement from the authors of the Software (see the COPYRIGHT file). You may develop Odoo modules that use the Software as a library (typically by depending on it, importing it and using its resources), but without copying any source code or material from the Software. You may distribute those modules under the license of your choice, provided that this license is compatible with the terms of the Odoo Proprietary License (For example: LGPL, MIT, or proprietary licenses similar to this one). It is forbidden to publish, distribute, sublicense, or sell copies of the Software or modified copies of the Software. The above copyright notice and this permission notice must be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
Please log in to comment on this module