Purchase Order Approval Check Lists v.16
The tool to make sure a purchase order is ready for the next stage. Purchase checklists. Purchase approval. Multi RFQ confirmation
Procurement is a complex and vulnerable process. It assumes various required steps and it usually involves a number of users from different departments. Any error might lead to drastic money losses and reputation damages. This Odoo tool is to make sure that a purchase order is always ready for the next stage and that all intermediary actions are approved. The app lets you prepare a checklist per each state, so it forces users to confirm all points and controls the approval process.
Checklists per procurement stage and company
Checklists are defined for a company in general. Purchase managers specify what and in which order state should be done and approved. A set is unlimited and might reflect custom procurement stages
Actions ensured to be done
In order to move an RFQ to a new state, a purchase manager needs to enter all confirmation points and should get approval for those he/she doesn't have a right to confirm
Indicative checklist to-do
Not yet done checkpoints are shown right on the tree of purchase orders or requests for quotations. You may distinguish those by colors and may always search them by keywords
Approval history for managerial control
Checklist actions are saved in history. If an order state is changed, already-done check items would be recovered. Turn on the setting 'not saved' to avoid that behavior for specific approval points
Multiple purchase approval roles
The app lets assign security groups for each checklist point. In such a case, only users from those groups would be able to confirm a related item
Super approval admins
The role 'Checklist Super User' allows (a) to confirm any checkpoints disregarding defined security groups and (b) to move any request for quotation further without fulfilling checklists.
Configurable purchase multi approval
Ensured approval workflow
-
Check items are generated based on a purchase order company and state. Thus, the set of actions to be done is different for each stage
-
Odoo scans checklists as soon as a user tries to change an order state. If not all actions are undertaken or confirmed, an RFQ can't be moved forward
-
You are not obliged to have a checklist for each state. Scanning an empty checklist is always considered as successful
-
The app lets configure checkpoints for each standard or custom purchase state
Typical scenarios for checklists
-
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 > 'Canceled') or re-set canceled RFQ ('Canceled' > 'Draft').
Frequently Asked Questions about Purchase Order Approval Check Lists Odoo v.16
Purchase Managers can modify the value of check lists. To manage checklists go to Purchase > Configuration> Check lists.
Please, make sure, that your user hasn't "Purchase Order Checklist Super User" rights. As they allow to confirm any checkpoints disregarding chosen security groups and to move any task further without fulfilling any of them.
When making a checklist you can choose the user groups for each checklist's statement. Only these user groups will be able to mark the statement as done. If someone else tries to mark the statement done, then the system will not let them save it and the warning will appear.
According to the current Odoo Apps Store policies:
- every module bought for version 12.0 and prior gives you access to all versions up to 12.0.
- starting from version 13.0, every module version should be purchased separately.
- disregarding the version, purchasing a tool grants you a right to all updates and bug fixes within a major version.
Take into account that the faOtools team does not control those policies. For all questions, please contact the Odoo Apps Store representatives directly.
The easiest approach is to use the Odoo store built-in workflow:
1. Open the module's page and click the button Deploy on odoo.sh
2. After that, you will be redirected to the GitHub page. Login to your account and click 'Create a new repo' or use the existing one. Please, make sure, that your repository is private. It is not permitted to publish the apps under the OPL-1 license. If necessary, create a new repo for your Odoo.sh project
3. Then, go to odoo.sh and click on the deploy button, submit the decision in the pop-up window and click 'Continue'. The action will trigger the installation process.
These steps will install the app for your project production branch. If you want to deploy the apps for other branches or update the module, you should undertake the following actions:
1. Upload the source code for the app from the Odoo store
2. Commit the module to a required GitHub repository. Make sure that none of the app folders/files are ignored (included in the .gitignore of your repo). Repositories are automatically created by odoo.sh, which might add by default some crucial items there (e.g. /lib). You should upload all module directories, subdirectories, and files without exceptions
3. Deploy a target branch of the odoo.sh project or wait until it is automatically built if your settings assume that.
Unzip the source code of the purchased tools in one of your Odoo add-ons' directories;
Re-start the Odoo server;
Turn on the developer mode (technical settings);
Update the apps' list (the apps' menu);
Find the app and push the button 'Install';
Follow the guidelines on the app's page if those exist.
Yes, sure. Take into account that Odoo automatically adds all dependencies to a cart. You should exclude previously purchased tools.
A red/orange warning itself does not influence features of the app. Regretfully, sometimes our modules do not pass standard automatic tests, since the latter assumes behavior which is in conflict with our apps goals. For example, we change price calculation, while standard Odoo module tests compare final price to standard algorithm.
So, first of all, please check deployed database features. Does everything work correctly?
If you still assume that warning influences real features, please contact us and forward full installation logs and the full lists of deployed modules (including core and third party ones).
No, we distribute the tools only through the official Odoo apps store
Regretfully, we do not have a technical possibility to provide individual prices.
No, third party apps can not be used on Odoo Online.
Yes, all modules marked in dependencies are absolutely required for a correct work of our tool. Take into account that price marked on the app page already includes all necessary dependencies.
The price for our modules is set up in euros. The Odoo store converts prices in others currencies according to its internal exchange rate. Thus, the price in US Dollars may change, when exchange rate changes.
Odoo demonstration databases (live previews)
For this app, we might provide a free personalized demo database.
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.
By your request, we will prepare an individual live preview database, where you would be able to apply any tests and check assumptions for 14 days.
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 tool to flexibly structure Odoo attachments in folders and synchronize directories with cloud clients: Google Drive, OneDrive/SharePoint, Nextcloud/ownCloud, and Dropbox. DMS. File Manager. Document management system
245€The tool to build a deep and structured knowledge base for internal and external use. Knowledge System. KMS. Wiki-like revisions.
298€The tool to automatically synchronize Odoo attachments with OneDrive files in both ways
394€The tool for time-based service management from booking appointments to sales and reviews
The tool to configure variant prices based on attributes coefficients and surpluses
The tool to calculate stock demand trends and make predictions for future demand statistically
The tool to make inventory data essential and comfortable for elaboration. Stocks analysis
38€