Purchase Order Approval Check Lists v.12

The tool to make sure a purchase order is ready for the next stage

28€ 25€

The price is valid till August, 15 (according to the promo campaign July-August 2024).
The tool does not require extra dependencies beside standard Odoo apps.
Current version:

Procurement is a complex and vulnerable process. It assumes various required steps and usually involves a number of users from different departments. Any error might lead to drastic money losses and reputation damages. This tool is to make sure that a purchase order is always ready to the next stage and all intermediary actions are approved. The app let you prepare a check list per each procurement step, force users to confirm all points, and control approval by responsible managers.

Check lists per order state and company

Checklists are defined for a company in general. Purchase managers specify what and on which order state should be done and approved. A set is unlimited, might reflect custom stages, and it is as unique as you want.
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.


Procurement checklist settings per company

Check list per company and order state

Check list is unique per order state and a company

Approval points per RFQ state

Purchase multi approval flow

In order to move an order to a new state, a purchase manager needs to enter all confirmation points and should get approval for those he doesn't have a right to confirm.
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.


Purchase approval involves various user roles

Check point security access

Order state can't be changed until checklist is confirmed

Check list mist be done to move an RFQ further

Odoo scans check list progress for any attempt of state update

Send by email button check list

Approval history

If a user marks a check point as done or as not done, the action is carefully recorded in the history. Thus, you always can investigate who and when makes a purchase order approval. It guarantees transparency and employees commitment.

Indicative checklist to-do

Not yet done check points are shown right on the tree of purchase orders or request for quotations. You may distinguish those by colors and always search them by key words.


Check lists to-do on tree views

Orders tree with check items

RFQ search by approval activities

Search by purchase check lists

Super checklist user

In any workflows you may encounter exceptions. Sometimes purchase users would reasonably like to move an order forward although not everything is done. For example, when the special prices are valid for a short period.
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.


Super checklist user has full rights for any check list

Check list super access level

Frequently Asked Questions about Purchase Order Approval Check Lists Odoo v.12

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.

  1. Unzip the source code of the purchased tools in one of your Odoo add-ons' directories;

  2. Re-start the Odoo server;

  3. Turn on the developer mode (technical settings);

  4. Update the apps' list (the apps' menu);

  5. Find the app and push the button 'Install';

  6. 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).

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.

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.

You may also like the tools
Cloud Storage Solutions

The technical core to synchronize your cloud storage solution with Odoo

245€ 220€
KnowSystem: Knowledge Base System

The tool to build deep and structured knowledge base for internal and external use. Knowledge System. KMS

OneDrive / SharePoint Odoo Integration

The tool to automatically synchronize Odoo attachments with OneDrive files in both ways

394€ 354€
Universal Appointments and Time Reservations

The tool for time-based service management from booking appointment to sale and reviews

398€ 358€
Google Drive Odoo Integration

The tool to automatically synchronize Odoo attachments with Google Drive files in both ways

394€ 354€
Advanced Variant Prices

The tool to configure variant prices based on attributes coefficients and surpluses

Product Management Interface

The tool to search, select and mass update product templates

Stocks by Locations

The tool to make inventory data essential and comfortable for elaboration

Stock Demand Trends and Forecast

The tool to calculate stock demand trends and make prediction for future demand statistically. Stock Forecast

98€ 88€