Sale Order Approval Check Lists
by faOtools https://faotools.com/apps/18.0/sale-order-approval-check-lists-18-0-sale-order-checklist-955$ 29.06
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Discuss (mail)
• Invoicing (account) |
| Lines of code | 351 |
| Technical Name |
sale_order_checklist |
| License | See License tab |
| Website | https://faotools.com/apps/13.0/sale-order-approval-check-lists-13-0-sale-order-checklist-422 |
| Versions | 11.0 12.0 13.0 14.0 15.0 16.0 17.0 18.0 |
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Discuss (mail)
• Invoicing (account) |
| Lines of code | 351 |
| Technical Name |
sale_order_checklist |
| License | See License tab |
| Website | https://faotools.com/apps/13.0/sale-order-approval-check-lists-13-0-sale-order-checklist-422 |
| Versions | 11.0 12.0 13.0 14.0 15.0 16.0 17.0 18.0 |
Check lists per sales team and order state
As a result when a sale order has an assigned team and gets its state updated, a check list would be automatically prepared.
Often an order state change does not require fulfilment of all requirements. For example, when you cancel a sale it seems unreasonable to approve customer credibility.
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 team form.
One of important use cases is also the state 'Quotation sent'. Sometimes, approval is required for an order confirmation but not for its forwarding to a client. This step might be even missed. In that situation you should define the same check points for the states 'Quotation' and 'Quotation Sent', while 'Quotation Sent' should be added as a no-checklist-required step.
Sale team checklist settings
Check list is unique per order state and team
Sale order multi approval flow
Since the tool let assign user groups for each checklist line, you may force various employees to take part in a sale evolvement. In such a way it is guaranteed that all actions are done and carefully checked.
Odoo will scan check lists as soon as a user tries to change sale state. In particular it happens when:
- A user tries to confirm an order ('Quotation' > 'Sale Order' and 'Quotation Sent' > 'Sale Order').
- A user locks ('Sale order' > 'Locked') or unlocks ('Locked' > 'Sale order') a sale.
- A user prints or sends a draft quotation ('Quotation' > 'Quotation Sent').
- A user cancels a quotation (any state > 'Cancelled') or re-set cancelled quotation ('Cancelled' > 'Quotation').
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.
Approval involves various user roles
Quotation state can't be changed until checklist is confirmed
Odoo scans check list progress for any attempt of state update
Approval history
Indicative checklist to-do
Check lists to-do on tree views
Search orders by check point to be done
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.
Super checklist user has full rights for any check list
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.
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 'Activate'/'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).
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.
Sale team checklist settings
Check list is unique per order state and team
Approval involves various user roles
Quotation state can't be changed until checklist is confirmed
Odoo scans check list progress for any attempt of state update
Check lists to-do on tree views
Search orders by check point to be done
Super checklist user has full rights for any check list
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.
To send us a bug report: press the "Website" link on the top of this page and push the button "Bug Report" (the tab Support). Alternatively, copy the link https://faotools.com/s/x0rv2j
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.
To share ideas: press the "Website" link on the top of this page and push the button "Share Features Ideas" (the tab Support). Alternatively, copy the link https://faotools.com/s/bm2nxo
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.
Questions and misc issues
Feel free to contact us with any other concerns, doubts, or questions: press the "Website" link on the top of this page and push the button "Raise Question" (the tab Support). Alternatively, copy the link https://faotools.com/s/9y27vp
About the team
faOtools (faotools.com, former odootools.com) is the developers and business analysts team that helps you extend Odoo's potential. We have communicated with end users to whom the software became the primary business tool since 2012. As a result, we are proud of the dozens of successful apps that have been developed. We are open to new ideas and challenges to create the best Odoo tools for business needs worldwide.
You may like the tools
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 make sure required jobs are carefully done on this pipeline stage
68
The tool to calculate sale trends and make prediction for future sales statistically. Sales Forecast
98Odoo Proprietary License v1.0 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.
Please log in to comment on this module