2020-07-08 22:27:14 +07:00
|
|
|
|
=====================
|
|
|
|
|
|
Upsell a subscription
|
|
|
|
|
|
=====================
|
|
|
|
|
|
|
|
|
|
|
|
Subscriptions are recurrent and go on indefinitely. As time passes by, our customers may want to
|
|
|
|
|
|
modify them. We must then be able to adapt the prices or change the products’ quantities to
|
|
|
|
|
|
accommodate their needs. Two situations can happen:
|
|
|
|
|
|
|
|
|
|
|
|
1. **Loyal customers:** This kind of customers already trust you as a brand. Therefore, you are
|
|
|
|
|
|
confident regarding what you offer since they keep paying for your products and services.
|
|
|
|
|
|
Consequently, it is easier to sell them something additional than it would be to a
|
|
|
|
|
|
new customer.
|
|
|
|
|
|
|
|
|
|
|
|
2. **New customers:** For this kind of customers, you have to come with something new, something
|
|
|
|
|
|
attractive. What about discounts? Typically, every subscription ends after a certain given time.
|
|
|
|
|
|
Making these types of offers for new customers strengthens your relationships with them and also
|
|
|
|
|
|
increases their retention.
|
|
|
|
|
|
|
|
|
|
|
|
.. raw:: html
|
|
|
|
|
|
|
|
|
|
|
|
<div align="center" style="color:#AD5E99; font-size: 2rem ;margin: 20px 0"> <b>Upselling can make
|
|
|
|
|
|
a subscription last longer!</b> </div>
|
|
|
|
|
|
|
|
|
|
|
|
Configuration
|
|
|
|
|
|
=============
|
|
|
|
|
|
|
|
|
|
|
|
As previously explained, to upsell a subscription to new customers, it is recommended to offer
|
|
|
|
|
|
*Discounts*. To activate this option, go to :menuselection:`Sales --> Configuration --> Settings` and,
|
|
|
|
|
|
under the *Pricing* category, you have the possibility to grant discounts on sales order lines.
|
|
|
|
|
|
|
[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:: upselling/configuration-to-upsell-a-subscription.png
|
2020-07-08 22:27:14 +07:00
|
|
|
|
:align: center
|
|
|
|
|
|
:alt: Activation of the discount option in Odoo Sales
|
|
|
|
|
|
|
|
|
|
|
|
Upsell your first subscription
|
|
|
|
|
|
==============================
|
|
|
|
|
|
|
|
|
|
|
|
Before upselling 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 upsell your 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:: upselling/upsell-your-subscription.png
|
2020-07-08 22:27:14 +07:00
|
|
|
|
:align: center
|
|
|
|
|
|
:alt: Upsell your subscription with Odoo Subscriptions
|
|
|
|
|
|
|
|
|
|
|
|
By using the smart button *Upsell*, you are able to create a new quotation with new subscription
|
|
|
|
|
|
products and send it to your customers for approval.
|
|
|
|
|
|
|
[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:: upselling/use-of-the-upsell-button-in-odoo-sales.png
|
2020-07-08 22:27:14 +07:00
|
|
|
|
:align: center
|
|
|
|
|
|
:alt: Add products to your subscription via the upsell option in Odoo Subscriptions
|
|
|
|
|
|
|
|
|
|
|
|
.. important::
|
|
|
|
|
|
When the quotation is confirmed by your customers, the products are added to the initial
|
|
|
|
|
|
subscription. Quotation prices are, then, prorated to the remaining time of the current invoicing
|
|
|
|
|
|
period.
|
|
|
|
|
|
|
|
|
|
|
|
Of course, before sending this new quotation to your customers, you can change the unit price, taxes,
|
|
|
|
|
|
and, even the discount you want to offer. The smart button *Customer preview* is useful for mimicking
|
|
|
|
|
|
the customer's reaction. In this case, we can confidently say that the customer will *Sign and pay*
|
|
|
|
|
|
this new quotation. When it is done, you have to go back in edit mode, confirm the quotation, and
|
|
|
|
|
|
click on the smart button *Subscriptions* to visualize all updates. From there, you can see that an
|
|
|
|
|
|
additional line has been added to the subscription with the new extra service the customer wanted to
|
|
|
|
|
|
purchase.
|
|
|
|
|
|
|
[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:: upselling/subscriptions-updates.png
|
2020-07-08 22:27:14 +07:00
|
|
|
|
:align: center
|
|
|
|
|
|
:alt: Visualize all your subscriptions updates with Odoo Subscriptions
|
|
|
|
|
|
|
|
|
|
|
|
In addition, by clicking on the *Sales* button, you have a summary of your sales orders in a list
|
|
|
|
|
|
view.
|
|
|
|
|
|
|
[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:: upselling/sales-order-updates.png
|
2020-07-08 22:27:14 +07:00
|
|
|
|
:align: center
|
|
|
|
|
|
:alt: List view of all sales orders created for a subscription
|
|
|
|
|
|
|
|
|
|
|
|
The only difference between your two sales orders is the description underneath the
|
|
|
|
|
|
*Subscription Management* category. There, you can easily visualize which one is your upselling.
|
|
|
|
|
|
|
|
|
|
|
|
.. seealso::
|
2023-04-07 15:35:45 +07:00
|
|
|
|
- :doc:`../subscriptions`
|
|
|
|
|
|
- :doc:`plans`
|
|
|
|
|
|
- :doc:`products`
|
|
|
|
|
|
|