After routing, the message is moved to other messages. You can find it in the technical menu "Messages", from which you can reroute it to the right object’s thread.

You can specify the models for routing. For that, open the module's settings by clicking on the tab 'Configuration', find the section 'Lost messages allowed models', define the models, which could be used to route messages to, and click 'Save'. After that, only stated in this field models will be available for a user to attach a message.

Yes, you can route any Odoo message. To that goal, admin users in developer mode should go to the menu Settings > Technical > Discuss > Messages; select required ones, push the Action > Route Manual.

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.

Please note that the faOtools team does not control those policies. For all questions, please contact the Odoo Apps Store representatives directly.

The most straightforward approach is to use the Odoo store's 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. Log in to your account, then click 'Create a new repo' or use an existing one. Please ensure 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 the Deploy button. In the pop-up window, submit the decision and click 'Continue.' This action will trigger the installation process.

These steps will install the app for your project's 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. Ensure none of the app folders/files are ignored (i.e., not included in your repo's .gitignore). Repositories are automatically created by odoo.sh and may include some crucial items by default (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, if your settings assume that, wait until it is automatically built.

Yes, sure. Simultaneously, Odoo automatically adds all dependencies to a cart, so you should exclude previously purchased tools to avoid double payment.

A red/orange warning does not influence the app's features. Regretfully, sometimes our modules do not pass standard automatic tests since the latter assume behavior that conflicts with our app's goals. For example, we change the price calculation, while the standard Odoo module tests compare the final price to a standard algorithm.

So, first of all, please check the deployed database features. Does everything work correctly?

If you still assume that the warning influences real features, please contact us and forward full installation logs and the full list of deployed modules (including core and third-party ones).

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

Regretfully, we do not have the technical means to provide individual prices. 

No, third-party apps can not be used on Odoo Online. Unfortunately, Odoo SaaS blocks such a possibility.

Yes, our tool requires all modules marked in dependencies to work correctly. The price marked on the app page already includes all necessary dependencies.

The price for our modules is set in euros. The Odoo store converts prices to other currencies according to its internal exchange rate. Thus, the price in US Dollars may change when the exchange rate is updated.