OmniApproval™ - Purchase Approvals
by Viindoo
| Lines of Code | 1507 |
| Technical name | viin_approval_purchase |
| License | OPL-1 |
| Website | https://viindoo.com/apps/modules/18.0/viin_approval_purchase |
| Read description for | v 17.0 v 19.0 |
| Required Apps | Invoicing (account) Purchase (purchase) Discuss (mail) Employees (hr) |
| Included Dependencies | Viindoo Base OmniApproval™: One platform. Every approval. Advanced HR Management OmniApproval™ - Accounting Approvals OmniApproval™ - Analytic Accounting Approvals Safe IR Metadata Proxies |
| Extensions | OmniApproval™ - Purchase Stock Approvals Bridge |
Approve the purchase order, with the order on the request
Purchase orders and their lines on the approval request - so the approver sees the vendor, the amount and what is being bought.
OmniApproval™ - Purchase Approvals (technical name viin_approval_purchase) is an Odoo 18.0 app for Odoo Community and Odoo Enterprise and Viindoo Cloud, built for buyer, approver, finance, administrator.
At a Glance
The facts of OmniApproval™ - Purchase Approvals, version 0.1.2, in one place. Published by Viindoo.
How It Works
Three screens.
The request carries the order
The order, its amount and the lines - on the request itself.
Configured per type
Approvers in sequence, minimum approvals, and which purchase fields the request carries.
The order it is about
Purchasing works as before; the approval sits beside it.
What You Get
Purchase order and purchase order lines on the approval request
One order or several, one line or several
Field toggles per approval type, on header and lines
The order opens from the request
Sequential approvers, minimum approvals and deadlines from the engine
Ordinary purchase flow otherwise unchanged
More Screens
Everything below was taken on a database seeded with real business data, on this series - not a mock-up and not a screenshot from an older version.
Field toggles per type
What This App Does Not Do
Read this before you buy. Everything below is something the app deliberately leaves to another app or to you.
Blocking is the approval state on the document, from the engine.
Thresholds live in the approval type's rules.
This is the purchasing bridge to that engine.
Which is deliberate - a monthly batch is one decision.
Works Well With
Apps from the same stack, built to fit this one:
OmniApproval™ - Procurement Approvals
Approving the need before the order.
OmniApproval™ - Procurement ApprovalsWho Should Use OmniApproval™ - Purchase Approvals?
Buyer
Sends the order for approval with the order attached.
Approver
Sees the vendor, the amount and the lines before signing.
Finance
Knows which purchases were approved by whom.
Administrator
Configures per type what a purchase request must carry.
Frequently Asked Questions
What does OmniApproval™ - Purchase Approvals do?
Purchase orders and their lines on the approval request - so the approver sees the vendor, the amount and what is being bought.
What does OmniApproval™ - Purchase Approvals not do?
It does not block confirmation by itself. Blocking is the approval state on the document, from the engine. It does not set spending limits. Thresholds live in the approval type's rules. It needs OmniApproval. This is the purchasing bridge to that engine. One request can cover several orders. Which is deliberate - a monthly batch is one decision.
Who is OmniApproval™ - Purchase Approvals for?
Buyer: Sends the order for approval with the order attached. Approver: Sees the vendor, the amount and the lines before signing. Finance: Knows which purchases were approved by whom. Administrator: Configures per type what a purchase request must carry.
Which Odoo version and editions does it support?
Odoo 18.0 - Odoo Community, Odoo Enterprise, Viindoo Cloud. Upgrades to a newer Odoo series are a separate purchase for that series.
What does it depend on?
It installs on top of: viin_approval_account, purchase. Odoo installs them with it.
How do I set it up?
Three screens.
What works well with it?
OmniApproval (viin_approval): The engine this extends. Procurement Approval (viin_approval_procurement): Approving the need before the order. Purchase Landed Costs (to_purchase_landed_cost): The freight that comes with the order.
Can I try it before buying?
Yes - the Live Preview button at the top of this page opens a working database.
How do I get support?
Write to apps.support@viindoo.com with your Odoo version and the technical name viin_approval_purchase; pre-sales questions go to sales@viindoo.com.
See OmniApproval™ - Purchase Approvals in Action
Live demo: v18demo-int.viindoo.com
Need help with OmniApproval™ - Purchase Approvals?
For questions, implementation support or a custom feature, contact Viindoo.
Pre-Sales & Partnership
sales@viindoo.comUpgrades to a newer Odoo series are a separate purchase for that series.
All Viindoo apps: Viindoo Apps
Technical Requirement
Changes log
0.1.2 - Latest on the 17.0 line
- Purchase fields are available on request lines as well as on the header.
OmniApproval™ - Purchase Approvals
For buyers, purchasing managers, approvers and approval administrators.
Note
Extends OmniApproval™ - see its documentation for roles, approvers, snapshots and every other engine feature. This guide only describes what the Purchase Order approval type adds.
Note
Builds on Purchase and OmniApproval™ Accounting.
Overview
A request for quotation or a purchase order is a commitment to a vendor. The module adds an approval type named Purchase Order to every company, so that a buyer submits the order for approval, an approver decides on it and the buyer then confirms the order as usual.
| Role | What they do | Access right to assign |
|---|---|---|
| Buyer | Prepares the request for quotation or order, submits it for approval and confirms it once approved. | Purchase: User |
| Purchasing manager | Follows the orders of the team. Holding the Purchase Administrator right alone gives no approval role. | Purchase: Administrator |
| Approver | Decides on the requests that reach them. | Team Approver or Officer |
| Approval administrator | Adjusts the Purchase Order approval type. | Administrator (Approvals) |
The Team Approver, Officer and Administrator rights are described in the Roles and Access Rights section of the OmniApproval™ guide.
Setup (for the Administrator)
- Go to Apps, search for OmniApproval™ - Purchase Approvals and click Install.
- Open Approval > Configuration > Approval Types. Each company now has an approval type named Purchase Order, ready to use.
- Give each person the access right of their role under Settings > Users & Companies > Users.
The Purchase Order type asks the employee's manager for the first approval step and names no approver. Who approves, and in how many steps, is yours to decide: add approvers to the type as described in the Approvers section of the OmniApproval™ guide. The approval steps run one after another.
What the Purchase Order type adds
Only orders in the RFQ, RFQ Sent or To Approve stage can be submitted for approval.
The request is filled in from the order:
| On the order | On the request |
|---|---|
| Order reference | Order Number |
| Vendor and company | Vendor and the company |
| Buyer | Buyer |
| Expected arrival | Expected Arrival |
| Each line: product, section or note, unit of measure, quantity, analytic distribution, description | The same columns of the request lines |
| Each line: unit price, discount, taxes | Unit Price, Discount (%), Taxes |
The order number, the unit price, the discount and the taxes only travel from the order to the request: the request never changes them on the order.
The request lines are shown under Order Lines and include the Discount (%) column. The discount is applied exactly as on the order, so the total of the request equals the total of the order.
Using the Purchase Order approval
Submitting an order (Buyer)
Purchase approvals always start from the order itself: the Purchase Order type does not create orders of its own. The usual process is to prepare the request for quotation first and to get it approved afterwards.
- Open the request for quotation or the order and click Action > Get Approved.
- Check the approval type and the order shown in the Submit for Approval window.
- Click Create Approval Request.
The request opens in Draft, with the order lines under Order Lines.
Click Submit to send it to the approvers. Approving, refusing and the other decisions work as described in the OmniApproval™ guide.
Confirming the approved order (Buyer)
Once the request is approved, confirm the order with its usual Confirm Order button. Confirming the order is not a change to what was approved: the request records no note.
Approval never blocks Confirm Order by itself. See the Business Documents section of the OmniApproval™ guide to add a block.
Changes made after submission
If someone edits a line of the order after the request was submitted - for example its quantity or its discount - the request shows a warning and its chatter notes the change once, with the difference. Nothing is blocked and nobody has to approve again. The Snapshots and Diff section of the OmniApproval™ guide explains the comparison.
Cancelling or refusing a request
When a request is cancelled, refused or reset to Draft, the order it was submitted from stays as it is. If the request had generated a purchase order or lines of its own, those are removed as described in the Cancelling, Refusing and Resetting to Draft section of the OmniApproval™ guide.
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.
