e3fee2cf46
Prior to this commit, the Odoo documentation was mainly split between
two repositories: odoo/odoo/doc and odoo/documentation-user. Some bits
of documentation were also hosted elsewhere (e.g., wiki, upgrade, ...).
This was causing several problems among which:
- The theme, config, Makefile, and similar technical resources had to
be duplicated. This resulted in inconsistent layout, features, and
build environments from one documentation to another.
- Some pages did not fit either documentation as they were relevant
for both users and developers. Some were relevant to neither of the
two (e.g., DB management).
- Cross-doc references had to be absolute links and they broke often.
- Merging large image files in the developer documentation would bloat
the odoo/odoo repository. Some contributions had to be lightened to
avoid merging too many images (e.g., Odoo development tutorials).
- Long-time contributors to the user documentation were chilly about
going through the merging process of the developer documentation
because of the runbot, mergebot, `odoo-dev` repository, etc.
- Some contributors would look for the developer documentation in the
`odoo/documentation-user` repository.
- Community issues about the user documentation were submitted on the
`odoo/odoo` repository and vice-versa.
Merging all documentations in one repository will allow us to have one
place, one theme, one work process, and one set of tools (build
environment, ...) for all of the Odoo docs.
As this is a good opportunity to revamp the layout of the documentation,
a brand new theme replaces the old one. It features a new way to
navigate the documentation, centered on the idea of always letting the
reader know what is the context (enclosing section, child pages, page
structure ...) of the page they are reading. The previous theme would
quickly confuse readers as they navigated the documentation and followed
cross-application links.
The chance is also taken to get rid of all the technical dangling parts,
performance issues, and left-overs. Except for some page-specific JS
scripts, the Odoo theme Sphinx extension is re-written from scratch
based on the latest Sphinx release to benefit from the improvements and
ease future contributions.
task-2351938
task-2352371
task-2205684
task-2352544
Closes #945
70 lines
2.5 KiB
ReStructuredText
70 lines
2.5 KiB
ReStructuredText
=================================
|
|
Get an accurate probable turnover
|
|
=================================
|
|
|
|
As you progress in your sales cycle, and move from one stage to another,
|
|
you can expect to have more precise information about a given
|
|
opportunity giving you an better idea of the probability of closing it,
|
|
this is important to see your expected turnover in your various reports.
|
|
|
|
Configure your kanban stages
|
|
============================
|
|
|
|
By default, Odoo Kanban view has four stages: New, Qualified,
|
|
Proposition, Won. Respectively with a 10, 30, 70 and 100% probability of
|
|
success. You can add stages as well as edit them. By refining default
|
|
probability of success for your business on stages, you can make your
|
|
probable turnover more and more accurate.
|
|
|
|
.. image:: media/turnover01.png
|
|
:align: center
|
|
|
|
.. image:: media/turnover02.png
|
|
:align: center
|
|
|
|
Every one of your opportunities will have the probability set by default
|
|
but you can modify them manually of course.
|
|
|
|
Set your opportunity expected revenue & closing date
|
|
====================================================
|
|
|
|
When you get information on a prospect, it is important to set an
|
|
expected revenue and expected closing date. This will let you see your
|
|
total expected revenue by stage as well as give a more accurate probable
|
|
turnover.
|
|
|
|
.. image:: media/turnover03.png
|
|
:align: center
|
|
|
|
See the overdue or closing soon opportunities
|
|
=============================================
|
|
|
|
In your pipeline, you can filter opportunities by how soon they will be
|
|
closing, letting you prioritize.
|
|
|
|
.. image:: media/turnover04.png
|
|
:align: center
|
|
|
|
As a sales manager, this tool can also help you see potential ways to
|
|
improve your sale process, for example a lot of opportunities in early
|
|
stages but with near closing date might indicate an issue.
|
|
|
|
View your total expected revenue and probable turnover
|
|
======================================================
|
|
|
|
While in your Kanban view you can see the expected revenue for each of
|
|
your stages. This is based on each opportunity expected revenue that you
|
|
set.
|
|
|
|
.. image:: media/turnover05.png
|
|
:align: center
|
|
|
|
As a manager you can go to :menuselection:`CRM --> Reporting --> Pipeline Analysis`
|
|
by default *Probable Turnover* is set as a measure. This report will take
|
|
into account the revenue you set on each opportunity but also the
|
|
probability they will close. This gives you a much better idea of your
|
|
expected revenue allowing you to make plans and set targets.
|
|
|
|
.. image:: media/turnover06.png
|
|
:align: center
|