Contacts Color Coding v.16
Partner color coding to score contacts and make rational decisions in any business area. Color codes. Customer scoring
Has your company ever lost money because a manager forgot some important details about a partner? With this tool, it will hardly happen again. This Odoo app introduces a system of highly available and efficiently manageable color codes for Odoo partners.
Automatic color codes
Automatic color codes do not assume any user involvement. Configure rules once, and all matched contacts will receive configured color codes
Use automatic color codes in case you can strictly describe which partners receive those color codes
Define a rule as a set of criteria a contact should satisfy. You may use any partner field in the same way you define a search filter in Odoo
There might be as many criteria combined by 'any' or 'all' operators as you like
For a single color code, you may have an unlimited number of automatic rules. Matching any of those rules would lead to this color code assignment
Automatic rules are applied in real-time. As soon as you configured a new one, open/reload any form and check contact color codes
Automatic scoring rules might be applied to almost any business scenario
Typical use case: A contact already has some sort of manual tag. For example, the 'Danger!' tag should lead to the red color code
Typical use case: All contacts with set 'Blacklist' field should be assigned the black color code
Typical use case: Customers with a low credit limit (e.g. with less than $2000) receive the orange color code
Typical use case: Mark gray contacts without mobile and phone entered
Typical use case: Define color codes based on a country or a region, based on the 'Degree of trust you have in this debtor', or based on your own custom field.
Flexible codes classifier
Have as many color codes as you like. They may relate to any business facet. For example, introduce 'Black List', 'Not trusted', 'Strategic partners', 'Low credit limit', etc.
Apply any color shade for your code
Each color code may have a few notes. For example, 'John Brown' is black-listed since (a) his parent company has a huge debt; (b) he is not available by phone and mobile; (c) he has the tag 'potential fraud' assigned by a financial security officer
As soon as you installed the tool, Odoo would prepare a few default color codes. You may simply update or delete those codes to reflect your own color codes' logic
To configure the codes classifier go to the Odoo General Settings and find the section 'Contact Color Codes'.
Frequently Asked Questions about Contacts Color Coding Odoo v.16
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.
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.
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.
Odoo demonstration databases (live previews)
For this app, we might provide a free personalized demo database.
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.
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.
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.
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 system245€
The tool to build a deep and structured knowledge base for internal and external use. Knowledge System. KMS. Wiki-like revisions.298€
The tool for time-based service management from booking appointments to sales and reviews398€
The tool to automatically synchronize Odoo attachments with Google Drive files in both ways394€
The tool to automatically synchronize Odoo attachments with OneDrive files in both ways394€
The tool to plan, share and control employees shifts in a form of weekly timetables. Work schedule. Work shift calendar148€
The tool combines users in roles and simplifies security group assigning. Access group management. Users mass updating48€
The tool to add new fields for Odoo contacts without any technical knowledge38€