CRM Check List and Approval Process v.17
The tool to make sure required jobs are carefully done on each CRM pipeline stage. CRM checklists
Making a customer from an opportunity is the only goal of the CRM pipeline. To achieve that goal sales staff needs to undertake a specific sequence of actions. Each of those actions is important on a definite funnel stage. Efficient companies know that missing any step might result in a long-run failure. This is an Odoo tool to make sure such a failure will not happen. The app provides a checklist for each pipeline stage to control requirements' fulfillment and to make sure that each action is fully approved by responsible users.
Stage-specific CRM checklists
Checklists are assigned per each opportunity stage. For instance, actions for the 'new' and 'proposition' stages might be different. Prepare any number of checkpoints for each CRM stage
Team-specific checkpoints
Checklists might be optionally distinguished by sales teams. Thus, the set of actions per stage may be different for 'America' and 'Europe'
Actions ensured to be done
To move a CRM lead forward in your funnel, its checklist should be fully confirmed ('moving forward' implies any change of stage from a lesser to a bigger sequence). For certain stages - e.g. for 'Canceled' - you may want to avoid such restrictions. Then, mark this stage as 'No need for checklist'
Highlighted opportunity progress
Fulfillment progress is shown on opportunities kanban and form views for instant overview
Approval history for managerial control
Checklist actions are saved in history. If an opportunity was moved back, already-done check items will be recovered. Turn on the setting 'not saved' to avoid that behavior for specific approval points
Multiple CRM checklist roles
The app lets assign security groups for each checklist point. In such a case, only users from those groups will be able to confirm a related item
Prohibit stage skipping
Configure specific stages as required, so salespersons would not be able to skip those. Then, the stages with the 'Forbid skipping this stage' option will be always visited and their checklists will be fulfilled. The setting does not influence 'No need for checklist', for example, when you cancel a case
Forbid opportunity regression
With the tool, configure the CRM pipeline to disallow moving opportunities back. To that goal, turn on the option 'Forbid regression to this stage' for particular states. For example, to make sure no leads become 'New' again
Super approval admins
The role 'Checklist Super User' allows (a) to confirm any checkpoints disregarding defined security groups; (b) to move any opportunity further (progress) without fulfilling checklists; (c) skip any states; (d) to move any opportunity back (regress) even a new stage does not allow that.
Frequently Asked Questions about CRM Check List and Approval Process Odoo v.17
Anybody who has access to stage settings can modify the value of check lists.
If set to "true", a lead/opportunity might be moved to this stage without fulfilling a check list. Usually used for "lost" stage, since it doesn't require any sort of extra actions. In such a case users can move any lead/opportunity to "lost" from any stage without doing anything (e.g. new > lost, proposition > lost).
If set to "false", a checklist of a current stage is required to be entered if moved to this stage (in case it is further through the pipeline). For example, "won" state requires certain actions. If you move a lead/opportunity from "proposition" to "won", you should confirm check points of the "proposition" stage. "False" is the default value for "no need for checklist" field.
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 calculate sales trends and make predictions for future sales statistically
98€The tool to make sure a sale order is ready for the next stage. Sale checklists. Sale approval. Multi quotation confirmation
The tool to add new fields for Odoo CRM opportunities without any technical knowledge
38€