2020-07-08 22:27:14 +07:00
|
|
|
====================
|
|
|
|
|
Renew a subscription
|
|
|
|
|
====================
|
|
|
|
|
|
|
|
|
|
The key feature of a subscription business model is the recurring nature of payments. In this model,
|
|
|
|
|
customers pay a recurring amount in exchange for access to a product or a service.
|
|
|
|
|
|
|
|
|
|
.. raw:: html
|
|
|
|
|
|
|
|
|
|
<div align="center" style="color:#AD5E99; font-size: 2rem ;margin: 20px 0"> <b>The renewal of a
|
|
|
|
|
subscription is the process followed by each customer when willing to pursue a
|
|
|
|
|
subscription.</b> </div>
|
|
|
|
|
|
|
|
|
|
Each subscriber experiences this renewal process monthly, annually, or sometimes more, depending on
|
|
|
|
|
the duration of the contract. Most subscription companies choose to automate their renewal processes
|
|
|
|
|
but, in some cases, manual subscription renewals are still the preferred option.
|
|
|
|
|
|
|
|
|
|
With **Odoo Subscriptions**, you can have all your subscriptions in one application, suggest an
|
|
|
|
|
automatic subscription renewal to your customers (as well as a manual one) and, finally, filter all
|
|
|
|
|
your subscriptions and easily find those to renew (with the help of the tag *To renew*).
|
|
|
|
|
|
|
|
|
|
Renew your first subscription
|
|
|
|
|
=============================
|
|
|
|
|
|
|
|
|
|
Before renewing a subscription, be sure to check out our documentation on how to
|
2023-04-07 15:35:45 +07:00
|
|
|
:doc:`Create a quotation <../subscriptions>` using subscription
|
2020-07-08 22:27:14 +07:00
|
|
|
products. Indeed, once confirmed, a quotation becomes a sales order and a new subscription is
|
|
|
|
|
automatically created. Therefore, this subscription has the status *In progress*. From there, you
|
|
|
|
|
have the possibility to renew the subscription. In the Other Info tab, underneath the To Renew
|
|
|
|
|
section, you can activate the *To renew* option. When activated, a yellow tag automatically appears
|
|
|
|
|
in the upper right corner of the subscription.
|
|
|
|
|
|
[MOV] content/*: move resource files into their related page's directory
Since odoo/documentation#903, the guideline for the location of new
resource (images, downloadable files, RST includes...) files is to place
those inside the directory of the RST page that references them.
For example, if `doc1.rst` has a reference to `image.png` and to
`download.zip`, the file structure should look like this:
├── parent_doc/
│ └── doc1/
│ │ └── image.png
│ │ └── download.zip
│ └── doc1.rst
│ └── doc2.rst
├── parent_doc.rst
Before this commit, most of the resource files were still located inside
'media' directories holding all the resource files referenced by RST
pages located at the same level as these directories. In the example
above, a single 'media' directory would hold all the resource files
referenced by both `doc1.rst` and `doc2.rst`. Doing so prevented us from
figuring out easily which resource file was referenced by which RST page
and, thus, lead to unused resource files piling up in the repository. It
also made it more complicated to define codeowners regex rules because a
team could not simply be assigned to `/some_page.*` but needed to be
assigned to both `/some_page\.rst` and to the location of 'media'.
In order to help new content writers figure out the guideline when
taking examples from other RST pages, this commit retroactively applies
the guideline to existing resource files and 'media' directories. The
left-over resource files that are not referenced by any RST page are
removed.
task-2497965
Part-of: odoo/documentation#2068
2022-05-20 16:54:32 +07:00
|
|
|
.. image:: renewals/renew-your-subscription.png
|
2020-07-08 22:27:14 +07:00
|
|
|
:align: center
|
|
|
|
|
:alt: Renew your subscription with Odoo Subscriptions
|
|
|
|
|
|
|
|
|
|
.. important::
|
|
|
|
|
The *To renew* tag is automatically ticked when a payment fails. This indicator also appears
|
|
|
|
|
on the customer portal. To visualize that, you just have to click on the *Customer preview*
|
|
|
|
|
button. The tag *To renew* appears on the top right corner.
|
|
|
|
|
|
[MOV] content/*: move resource files into their related page's directory
Since odoo/documentation#903, the guideline for the location of new
resource (images, downloadable files, RST includes...) files is to place
those inside the directory of the RST page that references them.
For example, if `doc1.rst` has a reference to `image.png` and to
`download.zip`, the file structure should look like this:
├── parent_doc/
│ └── doc1/
│ │ └── image.png
│ │ └── download.zip
│ └── doc1.rst
│ └── doc2.rst
├── parent_doc.rst
Before this commit, most of the resource files were still located inside
'media' directories holding all the resource files referenced by RST
pages located at the same level as these directories. In the example
above, a single 'media' directory would hold all the resource files
referenced by both `doc1.rst` and `doc2.rst`. Doing so prevented us from
figuring out easily which resource file was referenced by which RST page
and, thus, lead to unused resource files piling up in the repository. It
also made it more complicated to define codeowners regex rules because a
team could not simply be assigned to `/some_page.*` but needed to be
assigned to both `/some_page\.rst` and to the location of 'media'.
In order to help new content writers figure out the guideline when
taking examples from other RST pages, this commit retroactively applies
the guideline to existing resource files and 'media' directories. The
left-over resource files that are not referenced by any RST page are
removed.
task-2497965
Part-of: odoo/documentation#2068
2022-05-20 16:54:32 +07:00
|
|
|
.. image:: renewals/customer-preview-of-a-renewal.png
|
2020-07-08 22:27:14 +07:00
|
|
|
:align: center
|
|
|
|
|
:alt: Customer preview of a renewal with Odoo Subscriptions
|
|
|
|
|
|
|
|
|
|
When a subscription needs to be renewed, you have the possibility to use a new button called
|
|
|
|
|
*Renewal quotation*. By clicking on it, a new quotation is created. From there, start a basic sales
|
|
|
|
|
flow allowing you to send the quotation by email to your customers or to confirm it. It is better to
|
|
|
|
|
first *Send by email* the quotation to your customers in order to have their confirmation and, then,
|
|
|
|
|
*Confirm* it in **Odoo Sales**.
|
|
|
|
|
|
|
|
|
|
.. note::
|
|
|
|
|
In the Chatter of this new quotation, it is mentioned that "This renewal order has been created
|
|
|
|
|
from the previous subscription". Once confirmed by your customers, this quotation becomes a
|
|
|
|
|
sales order and a new sale is mentioned in the upper right corner of the subscription.
|
|
|
|
|
|
[MOV] content/*: move resource files into their related page's directory
Since odoo/documentation#903, the guideline for the location of new
resource (images, downloadable files, RST includes...) files is to place
those inside the directory of the RST page that references them.
For example, if `doc1.rst` has a reference to `image.png` and to
`download.zip`, the file structure should look like this:
├── parent_doc/
│ └── doc1/
│ │ └── image.png
│ │ └── download.zip
│ └── doc1.rst
│ └── doc2.rst
├── parent_doc.rst
Before this commit, most of the resource files were still located inside
'media' directories holding all the resource files referenced by RST
pages located at the same level as these directories. In the example
above, a single 'media' directory would hold all the resource files
referenced by both `doc1.rst` and `doc2.rst`. Doing so prevented us from
figuring out easily which resource file was referenced by which RST page
and, thus, lead to unused resource files piling up in the repository. It
also made it more complicated to define codeowners regex rules because a
team could not simply be assigned to `/some_page.*` but needed to be
assigned to both `/some_page\.rst` and to the location of 'media'.
In order to help new content writers figure out the guideline when
taking examples from other RST pages, this commit retroactively applies
the guideline to existing resource files and 'media' directories. The
left-over resource files that are not referenced by any RST page are
removed.
task-2497965
Part-of: odoo/documentation#2068
2022-05-20 16:54:32 +07:00
|
|
|
.. image:: renewals/renew-a-quotation.png
|
2020-07-08 22:27:14 +07:00
|
|
|
:align: center
|
|
|
|
|
:alt: Renew a quotation with Odoo Subscriptions
|
|
|
|
|
|
|
|
|
|
By clicking on the *Sales* button, you have a summary of your sales orders in a list view.
|
|
|
|
|
The only difference between your two quotations is the description underneath the
|
|
|
|
|
*Subscription Management* category. There, you can easily visualize which one is your renewal.
|
|
|
|
|
|
[MOV] content/*: move resource files into their related page's directory
Since odoo/documentation#903, the guideline for the location of new
resource (images, downloadable files, RST includes...) files is to place
those inside the directory of the RST page that references them.
For example, if `doc1.rst` has a reference to `image.png` and to
`download.zip`, the file structure should look like this:
├── parent_doc/
│ └── doc1/
│ │ └── image.png
│ │ └── download.zip
│ └── doc1.rst
│ └── doc2.rst
├── parent_doc.rst
Before this commit, most of the resource files were still located inside
'media' directories holding all the resource files referenced by RST
pages located at the same level as these directories. In the example
above, a single 'media' directory would hold all the resource files
referenced by both `doc1.rst` and `doc2.rst`. Doing so prevented us from
figuring out easily which resource file was referenced by which RST page
and, thus, lead to unused resource files piling up in the repository. It
also made it more complicated to define codeowners regex rules because a
team could not simply be assigned to `/some_page.*` but needed to be
assigned to both `/some_page\.rst` and to the location of 'media'.
In order to help new content writers figure out the guideline when
taking examples from other RST pages, this commit retroactively applies
the guideline to existing resource files and 'media' directories. The
left-over resource files that are not referenced by any RST page are
removed.
task-2497965
Part-of: odoo/documentation#2068
2022-05-20 16:54:32 +07:00
|
|
|
.. image:: renewals/subscription-management-category.png
|
2020-07-08 22:27:14 +07:00
|
|
|
:align: center
|
|
|
|
|
:alt: Renewal as Subscription Management form in Odoo Subscriptions
|
|
|
|
|
|
|
|
|
|
Visualize your subscriptions to renew
|
|
|
|
|
=====================================
|
|
|
|
|
|
|
|
|
|
Finally, if you want to visualize all your subscriptions and easily find those to renew, you can go
|
|
|
|
|
to your *Subscriptions dashboard* and use the filter *To renew*.
|
|
|
|
|
|
[MOV] content/*: move resource files into their related page's directory
Since odoo/documentation#903, the guideline for the location of new
resource (images, downloadable files, RST includes...) files is to place
those inside the directory of the RST page that references them.
For example, if `doc1.rst` has a reference to `image.png` and to
`download.zip`, the file structure should look like this:
├── parent_doc/
│ └── doc1/
│ │ └── image.png
│ │ └── download.zip
│ └── doc1.rst
│ └── doc2.rst
├── parent_doc.rst
Before this commit, most of the resource files were still located inside
'media' directories holding all the resource files referenced by RST
pages located at the same level as these directories. In the example
above, a single 'media' directory would hold all the resource files
referenced by both `doc1.rst` and `doc2.rst`. Doing so prevented us from
figuring out easily which resource file was referenced by which RST page
and, thus, lead to unused resource files piling up in the repository. It
also made it more complicated to define codeowners regex rules because a
team could not simply be assigned to `/some_page.*` but needed to be
assigned to both `/some_page\.rst` and to the location of 'media'.
In order to help new content writers figure out the guideline when
taking examples from other RST pages, this commit retroactively applies
the guideline to existing resource files and 'media' directories. The
left-over resource files that are not referenced by any RST page are
removed.
task-2497965
Part-of: odoo/documentation#2068
2022-05-20 16:54:32 +07:00
|
|
|
.. image:: renewals/subscriptions-dashboard-with-the-to-renew-filter.png
|
2020-07-08 22:27:14 +07:00
|
|
|
:align: center
|
|
|
|
|
:alt: List view of all subscriptions and use of the filter to renew in Odoo Subscriptions
|
|
|
|
|
|
|
|
|
|
.. seealso::
|
2023-04-07 15:35:45 +07:00
|
|
|
- :doc:`../subscriptions`
|
|
|
|
|
- :doc:`plans`
|
|
|
|
|
- :doc:`products`
|