|
1 | 1 | =================== |
2 | | -Renew subscriptions |
| 2 | +Renewing subscriptions |
3 | 3 | =================== |
4 | 4 |
|
5 | | -The foundation of any subscription business model is recurring payments. This is when customers |
6 | | -reliably pay a regular amount at specific intervals, in exchange for access to a subscription |
7 | | -product or service. |
| 5 | +Subscription renewal is the process customers follow when they willingly choose to continue a |
| 6 | +subscription product or service. Subscribers go through the renewal process at different intervals |
| 7 | +-- weekly, monthly, annually, etc. -- depending on the duration of the agreed-upon contract. Most |
| 8 | +companies that offer subscriptions prefer to automate the renewal process for customers. However, |
| 9 | +manual subscription renewals are still used in some cases. |
8 | 10 |
|
9 | | -Subscription renewal is the process customers follow when they willingly choose to continue |
10 | | -participating in, and paying for, a subscription product or service. |
11 | | - |
12 | | -Subscribers experience the renewal process at different intervals -- weekly, monthly, annually, etc. |
13 | | --- depending on the duration of the agreed-upon contract. |
14 | | - |
15 | | -Most companies that offer subscriptions prefer to automate the renewal process for customers. |
16 | | -However, manual subscription renewals are still used in some cases. |
17 | | - |
18 | | -With the Odoo **Subscriptions** application, a company can manage all of its subscriptions in one |
19 | | -place. Renewals can be processed automatically, or manually, include additional products or upsells |
20 | | -per renewal order, and be filtered in batch views to quickly locate customers who need to renew |
| 11 | +With the Odoo :guilabel:`Subscriptions` application, a company can manage all of its subscriptions |
| 12 | +in one place. Renewals can be processed automatically or manually, include additional products or |
| 13 | +upsells per renewal order, and be filtered in batch views to locate customers who need to renew |
21 | 14 | their subscriptions. |
22 | 15 |
|
23 | | -Subscription renewals |
| 16 | +Required elements for subscription renewals |
24 | 17 | ===================== |
25 | 18 |
|
26 | | -In order to renew a subscription, a quotation with a subscription product **must** be confirmed, |
27 | | -with a configured *Recurring Plan* selected. |
28 | | - |
29 | | -To open a subscription quotation, navigate to :menuselection:`Subscriptions app --> Subscriptions |
30 | | ---> Quotations`, and select the desired quotation from the list. Or, create a new one by clicking |
31 | | -:guilabel:`New` to open a new quotation form. |
| 19 | +In order to renew a subscription, a quotation with a subscription product *must* be confirmed and |
| 20 | +a configured *recurring plan* must be selected. Payment from the customer for the initial |
| 21 | +subscription *must* be invoiced and registered in order to successfully open a renewal quotation. |
32 | 22 |
|
33 | | -.. note:: |
34 | | - - Only a singular product is required. |
35 | | - - A subscription service counts as a product, as it is considered a recurring product. |
36 | | - |
37 | | -Subscription quotations **must** be confirmed, and payment from the customer for the |
38 | | -initial subscription **must** be invoiced and registered in order to successfully open a *Renewal |
39 | | -Quotation*. |
40 | | - |
41 | | -.. seealso:: |
42 | | - For more information on the above process of confirming quotations and invoicing payments, |
43 | | - see: |
44 | | - - :doc:`../sales/sales_quotations/create_quotations` |
45 | | - - :doc:`../sales/sales_quotations/get_paid_to_validate` |
46 | | - |
47 | | -Once the payment from the subscription quotation is confirmed, the quotation turns into a sales |
48 | | -order. An :guilabel:`In Progress` tag is applied to the sales order form, and a series of buttons |
49 | | -also appear at the top of the sales order, including a :guilabel:`Renew` button. |
| 23 | +To ensure these required elements are all present, begin by opening an exisiting subscription |
| 24 | +quotation. Navigate to :menuselection:`Subscriptions app --> Subscriptions--> Quotations` and |
| 25 | +select the desired quotation from the list. Properly configured subscriptions show as being in the |
| 26 | +:guilabel:`Sales Order` stage, have an :guilabel:`In Progress` tag, and have the :guilabel:`Renew` |
| 27 | +button in the row of buttons directly above the order form. |
50 | 28 |
|
51 | 29 | .. image:: renewals/renew-button.png |
52 | 30 | :align: center |
53 | 31 | :alt: Renew button on subscription sales order with Odoo Subscriptions. |
54 | 32 |
|
| 33 | +The subscription renewal process |
| 34 | +===================== |
| 35 | + |
55 | 36 | When the :guilabel:`Renew` button is clicked, Odoo instantly presents a new renewal quotation, |
56 | 37 | complete with a :guilabel:`Renewal Quotation` tag. |
57 | 38 |
|
58 | 39 | .. image:: renewals/renewal-quotation.png |
59 | 40 | :align: center |
60 | 41 | :alt: Renewal quotation in the Odoo Subscriptions application. |
61 | 42 |
|
62 | | -From here, a standard sales flow can occur to confirm the quotation. This typically begins |
63 | | -by clicking :guilabel:`Send by Email`, which sends a copy of the quotation to the customer, by |
64 | | -email, for them to confirm, and eventually, pay for. |
| 43 | +From here, follow the standard sales flow to confirm the quotation, invoice the order, and receive |
| 44 | +payment. |
65 | 45 |
|
66 | | -.. note:: |
67 | | - In the chatter of the :guilabel:`Renewal Quotation`, it is mentioned that this subscription is |
68 | | - the renewal of the subscription from the original sales order. |
| 46 | +.. tip:: |
| 47 | + Important reference information like the start date and next invoice date are automatically added |
| 48 | + to the renewal quotation's chatter. |
69 | 49 |
|
70 | | -Once the :guilabel:`Renewal Quotation` is confirmed, it becomes a sales order, and a |
| 50 | +Once the renewal quotation is confirmed, it becomes a sale order and a :icon:`fa-usd` |
71 | 51 | :guilabel:`Sales History` smart button appears at the top of the page. |
72 | 52 |
|
73 | 53 | .. image:: renewals/sales-history-smart-button.png |
74 | 54 | :align: center |
75 | 55 | :alt: Sales History smart button in the Odoo Subscriptions application. |
76 | 56 |
|
77 | | -When that :guilabel:`Sales History` smart button is clicked, Odoo reveals a separate page, |
| 57 | +When the :icon:`fa-usd` :guilabel:`Sales History` smart button is clicked, Odoo loads a new page, |
78 | 58 | showcasing the different sales orders attached to this subscription, along with their individual |
79 | 59 | :guilabel:`Subscription Status`. |
80 | 60 |
|
81 | 61 | .. image:: renewals/sales-history-page.png |
82 | 62 | :align: center |
83 | 63 | :alt: Renewal quotation in the Odoo Subscriptions application. |
84 | 64 |
|
85 | | -Additionally, once the :guilabel:`Renewal Quotation` is confirmed, an :guilabel:`MRR` smart button |
86 | | -also appears at the top of the sales order. |
| 65 | +Additionally, once the Renewal Quotation is confirmed, an :icon:`fa-line-chart` :guilabel:`MRR` |
| 66 | +smart button also appears at the top of the sale order. This button leads to the MRR Analysis page |
| 67 | +where monthly recurring revenue related to this specific subscription may be found. |
87 | 68 |
|
88 | 69 | .. image:: renewals/mrr-smart-button.png |
89 | 70 | :align: center |
90 | 71 | :alt: MRR smart button in the Odoo Subscriptions application. |
91 | 72 |
|
92 | | -When clicked, Odoo reveals an :guilabel:`MRR Analysis` page, detailing the monthly recurring revenue |
93 | | -related to this specific subscription. |
94 | | - |
95 | 73 | .. important:: |
96 | | - On rare occasions, automatic payment can fail, which results in a *Payment Failure* tag on the |
97 | | - top-right of the sales order, if there is an error in the payment method. |
| 74 | + On rare occasions, automatic payments can fail to register properly, which results in a |
| 75 | + :guilabel:`Payment Failure` tag on the sale order and the :guilabel:`Contract in exception` |
| 76 | + checkbox being automatically ticked in the :guilabel:`Subscription` section of the sale order's |
| 77 | + :guilabel:`Other Info` tab. |
98 | 78 |
|
99 | | - This is done to prevent the system from charging the customer again the next time a scheduled |
100 | | - action is run. Because the status of the payment is unknown, Odoo requests a manual operation to |
101 | | - check if the payment has been made, before the payment can be used again. |
| 79 | + Being marked Contract in exception prevents scheduled actions from running, which keeps the |
| 80 | + system from accidentally double-charging the customer if the automatic payment actually went |
| 81 | + through. Because the status of the payment failed to register with the system, users must |
| 82 | + manually check if the payment has been made before automatic payments and other scheduled actions |
| 83 | + can resume. |
102 | 84 |
|
103 | 85 | To do this, navigate to :menuselection:`Subscriptions app --> Subscriptions --> Quotations`. |
104 | | - Click into the desired subscription, then check the *Chatter* to see if the payment was made. |
| 86 | + Click into the desired subscription, then check the Chatter to see if the payment was made. |
105 | 87 |
|
106 | | - If the payment was **not** made, first enter :doc:`debug mode <../../general/developer_mode>`. |
| 88 | + If the payment *was not* made, first enter :doc:`Developer Mode <../../general/developer_mode>`. |
107 | 89 | Then, click the :guilabel:`Other Info` tab, and untick the checkbox next to :guilabel:`Contract |
108 | | - in exception`. Reload the sales order, and the :guilabel:`Payment Failure` tag is gone. |
| 90 | + in exception`. Reload the sale order and confirm that the :guilabel:`Payment Failure` tag is |
| 91 | + gone. |
109 | 92 |
|
110 | | - If the payment **was** made, a new invoice must be made and posted manually. This automatically |
111 | | - updates the next invoice date of the subscription. Once created, enter :doc:`debug mode |
112 | | - <../../general/developer_mode>`, and navigate to the new sales order. Click the :guilabel:`Other |
113 | | - Info` tab, and untick the checkbox next to :guilabel:`Contract in exception`. |
114 | | - Reload the sales order, and the :guilabel:`Payment Failure` tag is gone. |
| 93 | + If the payment *was* made, a new invoice must be made and posted manually. This automatically |
| 94 | + updates the next invoice date of the subscription. Once the invoice is created, enter |
| 95 | + :doc:`Developer Mode <../../general/developer_mode>` and navigate to the new sale order. Click |
| 96 | + the :guilabel:`Other Info` tab, and untick the checkbox next to |
| 97 | + :guilabel:`Contract in exception`. Reload the sale order and confirm that the |
| 98 | + :guilabel:`Payment Failure` tag is gone. |
115 | 99 |
|
116 | 100 | .. figure:: renewals/contract-in-exception.png |
117 | 101 | :align: center |
118 | 102 | :alt: The "contract in exception" option selected with the "payment failure" tag shown. |
119 | 103 |
|
120 | | - The :guilabel:`contract in exception`` option selected with the :guilabel:`payment failure` |
| 104 | + The :guilabel:`Contract in exception` option selected with the :guilabel:`Payment Failure` |
121 | 105 | tag shown. |
122 | 106 |
|
123 | | - In both cases, once the :guilabel:`Contract in exception` option is no longer selected, Odoo |
124 | | - handles renewals automatically again. If the subscription remains in *payment failure*, it is |
125 | | - skipped by Odoo until the sales order is closed. |
| 107 | + In both cases, once the :guilabel:`Contract in exception` checkbox is no longer ticked, Odoo |
| 108 | + handles renewals automatically again. If the subscription remains in Payment Failure, it is |
| 109 | + ignored by Odoo until the sale order is closed. |
126 | 110 |
|
127 | 111 | .. seealso:: |
128 | 112 | - :doc:`../subscriptions` |
| 113 | + - :doc:`../sales/sales_quotations/create_quotations` |
| 114 | + - :doc:`../sales/sales_quotations/get_paid_to_validate` |
0 commit comments