Purchase Order Approval Check Lists v.13
The tool to make sure a purchase order is ready for the next stage
Check lists per order state and company
As a result when a purchase order of this company gets its state updated, a check list would be automatically prepared.
How check list points might be missed
Often an order state change does not require fulfilment of all requirements. For example, when you cancel a purchase it seems unreasonable to approve vendor prices.
In such a case you should merely define states moving to which doesn't need confirmation. It is possible to do right under the check list settings on a checklist form.
One of important use cases is also the state 'RFQ sent'. Sometimes, approval is required for an order confirmation but not for contacting a vendor. This step might be even missed. In that situation you should define the same check points for the states 'RFQ' and 'RFQ Sent', while 'RFQ Sent' should be added as a no-checklist-required step.
Screenshots
Procurement checklist settings per company
![Check list per company and order state](/web/image/12163/purchase_checklist.png)
Check list is unique per order state and a company
![Approval points per RFQ state](/web/image/12164/purchase_order_checklist_main.png)
Purchase multi approval flow
Since the tool let assign user groups for each checklist line, you may force various employees from different departments to take part in procurement. In such a way it is guaranteed that all actions are done and carefully checked.
When Odoo would warn purchase users to confirm check lists
Odoo will scan check lists as soon as a user tries to change an order state. In particular it happens when:
- A user tries to confirm an order ('RFQ' > 'Purchase Order' and 'RFQ Sent' > 'Purchase Order').
- An order is triggered for approval ('RFQ' > 'Approval' and 'RFQ Sent' > 'Approval').
- A user locks ('Purchase order' > 'Locked') or unlocks ('Locked' > 'Purchase order') a purchase.
- A user prints or sends an RFQ ('RFQ' > 'RFQ Sent').
- A user cancels an order (any state > 'Cancelled') or re-set cancelled RFQ ('Cancelled' > 'Draft').
Surely, you are not obliged to have a check list for each state. Scanning of empty checklist is always considered as successful.
Besides, if you had custom stages, transitions to those would be also taken into account.
Screenshots
Purchase approval involves various user roles
![Check point security access](/web/image/12165/approval_user_roles.png)
Order state can't be changed until checklist is confirmed
![Check list must be done to move an RFQ further](/web/image/12166/no_state_change_before_approved.png)
Odoo scans check list progress for any attempt of state update
![Send by email button check list](/web/image/12167/send_non_approved_purchase_order.png)
Approval history
Indicative checklist to-do
Screenshots
Check lists to-do on tree views
![Orders tree with check items](/web/image/12168/purchases_list_to_do.png)
RFQ search by approval activities
![Search by purchase check lists](/web/image/12169/purchase_search_to_approve_points.png)
Super checklist user
In such a case you should assign the super check list access level for yourself or for any responsible manager. A user with such rights would be able both to change an order sate without approving check list and confirm any check point disregarding security restrictions.
Screenshots
Super checklist user has full rights for any check list
![Check list super access level](/web/image/12170/purchase_checklist_superuser.png)
Bug reporting
In case you have faced any bugs or inconsistent behavior, do not hesitate to contact us. We guarantee to provide fixes within 60 days after the purchase, while even after this period we are strongly interested to improve our tools.
No phone number or credit card is required to contact us: only a short email sign up which does not take more than 30 seconds.
Please include in your request as many details as possible: screenshots, Odoo server logs, a full description of how to reproduce your problem, and so on. Usually, it takes a few business days to prepare a working plan for an issue (if a bug is confirmed) or provide you with guidelines on what should be done (otherwise).
Public features requests and module ideas (free development)
We are strongly motivated to improve our tools and would be grateful for any sort of feedback. In case your requirements are of public use and might be efficiently implemented, the team would include those in our to-do list.
Such a to-do list is processed on a regular basis and does not assume extra fees. Although we cannot promise deadlines and final design, it might be a good way to get desired features without investments and risks.
No phone number or credit card is required to contact us: only a short email sign up which does not take more than 30 seconds.
The technical core to synchronize your cloud storage solution with Odoo
379€The tool to build deep and structured knowledge base for internal and external use. Knowledge System. KMS
298€The tool for time-based service management from booking appointment to sale and reviews
398€The tool to automatically synchronize Odoo attachments with OneDrive files in both ways
468€The tool to automatically synchronize Odoo attachments with Google Drive files in both ways
468€The tool to configure variant prices based on attributes coefficients and surpluses
98€