Approval for replenishment
by CLuedoo https://www.cluedoo.com/shop/lic-clu-set-pur-0078-approval-for-replenishment-6704$ 150.86
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Inventory (stock)
• Purchase (purchase) • Approvals (approvals) • Discuss (mail) • Employees (hr) • Invoicing (account) |
| Lines of code | 316 |
| Technical Name |
fal_replenishment_approval |
| License | OPL-1 |
| Website | https://www.cluedoo.com/shop/lic-clu-set-pur-0078-approval-for-replenishment-6704 |
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Inventory (stock)
• Purchase (purchase) • Approvals (approvals) • Discuss (mail) • Employees (hr) • Invoicing (account) |
| Lines of code | 316 |
| Technical Name |
fal_replenishment_approval |
| License | OPL-1 |
| Website | https://www.cluedoo.com/shop/lic-clu-set-pur-0078-approval-for-replenishment-6704 |
STORY BEHIND THE FEATURE
ODOO BEHAVIOUR
Odoo allows users to configure Reordering Rules (Replenishment Rules) that automatically or manually trigger the creation of Request for Quotation (RFQ) when stock falls below minimum levels.
❌ However, Odoo does not provide any approval workflow before generating the RFQ:
-
RFQs are created immediately when replenishment is triggered, either manually or via scheduled actions.
-
No way to hold, validate, or control automatic purchase creation.
-
Difficult to enforce internal purchasing policies or budget approvals.
CLUEDOO BEHAVIOUR
✅ Introduces an Approval Workflow for replenishment operations:
-
For each Replenishment Rule , users can configure whether approval is required before creating RFQs.
✅ When replenishment is triggered (manual or automatic):
-
The system checks if approval is needed.
-
If so, it creates an Approval Request instead of generating the RFQ.
-
The RFQ will only be created after the request is approved .
✅ Seamlessly integrates with Odoo's Approval module:
-
Supports standard approval templates, users, and steps.
-
Ensures traceability of who approved and when.
✅ Applies to all standard replenishment flows:
-
Manual Replenishment from the UI.
-
Scheduled Replenishment Actions (cron job).
✅ Ensures cleaner procurement operations:
-
Prevents unauthorized purchases.
-
Adds a layer of control for critical or expensive items.
-
Aligns with internal control and audit practices.
COMPARISON: ODOO AND CLUEDOO
🟠 Odoo:
- ❌ No built-in control for reviewing or validating replenishment requests
- ❌ Lacks an audit trail for who initiated or approved a replenishment.
-
Allows manual or automatic replenishment.
-
Directly creates RFQ without any approval step.
-
All products follow the same rule without differentiation by approval needs.
🟢 Cluedoo:
-
✅ Adds an approval layer before RFQ creation based on Replenishment Rule settings.
- ✅Supports both manual and automatic replenishment flows with validation control.
- ✅Generates an Approval Request instead of RFQ when approval is required.
- ✅ Fully integrates with Odoo’s native Approval module.
BUSINESS CASE
A company requires employees to submit approval requests before creating purchase orders. Each request is linked to a specific project or cost center , which must be tracked via analytic accounts for budgeting and financial reporting.
OUR FEATURES AS SOLUTIONS
Add Approval for replenishment
How to use module
|
1
Go to Inventory > Choose or create a product > now you can enable "Need approval for replenishment"
|
|
|
2
Go to Replenishment >set product route "Buy" > click order > RFQ Approval will be created.
|
|
|
3
Go to Approval > create RFQ > a RFQ will be created
|
|
|
4
If the Approver refuse, "Create RFQ" button will not appear.
|
|
|
5
You also can do it from product template
|
|
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