Sale Order Approval Check Lists v.11

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

15.0 14.0 13.0 12.0 11.0

~~48€~~ 43€

Buy in the Odoo Apps Store Request Free Demo Database

The price is valid till October, 15 (according to the promo campaign September-October 2022).

The tool does not require extra dependencies beside standard Odoo apps.

Current version: 11.0.1.0.3

Enterprise

Community

Odoo.sh

Check list mist be done to move an order further

To make a sale, each company undertakes a specific sequence of actions which usually involves various user roles and various requirements to be fulfilled. Control of that process is both complex and extremely important. If a salesperson misses a step, a promising deal might evolve to a drastic failure. This tool is to make sure that a sale order is always ready to the next stage and all intermediary results are approved. The app let you prepare a check list per each state, force users to confirm all points, and control approval by responsible managers.

Check lists per sales team and order state

Checklists are defined for each sales team what let you reflect various work flows depending on applied sales typology. Sale managers by themselves 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 sale order has an assigned team and 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 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.

Screenshots

Sale team checklist settings

Check list is unique per order state and team

Sale order multi approval flow

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

When Odoo would warn salespersons to confirm check lists

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.

Screenshots

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

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

Indicative checklist to-do

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

Screenshots

Check lists to-do on tree views

Search orders by check point to be done

Super checklist user

In any workflows you may encounter exceptions. Sometimes sales persons would reasonably like to move an order forward although not everything is done. For example, when a customer is super perspective or is a loyal partner.
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

Frequently Asked Questions about Sale Order Approval Check Lists Odoo v.11

What are the update policies of your tools?

According to the current Odoo Apps Store policies:

every module bought for the version 12.0 and prior gives you an access to the all versions up to 12.0.
starting from the version 13.0, every version of the module should be purchased separately.
disregarding the version, purchasing a tool grants you a right for all updates and bug fixes within a major version.

Take into account that faOtools team does not control those policies. By all questions please contact the Odoo Apps Store representatives directly.

How can I install your app on Odoo.sh?

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 would install the app for your project production branch. If you wanted 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.

How should I install your app on my own server?

Unzip source code of purchased tools in one of your Odoo add-ons directory
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.

I noticed that your app has extra add-ons. May I purchase them afterwards?

Yes, sure. Take into account that Odoo automatically adds all dependencies to a cart. You should exclude previously purchased tools.

May I buy your app from your company directly?

No, we distribute the tools only through the official Odoo apps store

I would like to get a discount

Regretfully, we do not have a technical possibility to provide individual prices.

May I install the app on my Odoo Online (SaaS) database?

No, third party apps can not be used on Odoo Online.

Your tool has dependencies on other app(s). Should I purchase those?

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.

I deployed your app on Odoo.sh and see warning / error in tests

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

What is the price for the module in US Dollars? Why did it change?

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.

Request Demo Database (Live Preview) ^free

Bug Report Raise Question Share Features Ideas

Request Individual Customization

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.

New features and extra Odoo services (individual development)

Each of our apps might be customized and extended to suit your specific requirements.

Our customization team (itlibertas.com) fulfills not only such jobs but also provides a full range of Odoo services. From simple modifications and consultations to complex enterprise projects. The team has completed over 100 implementations since 2012 and might help with any technical or business needs.

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