#2 #3 add membership_payment_date: membership start date -> payment date. Don't overlap membership periods on renewals
This commit is contained in:
parent
54965d483f
commit
d8cd83bdaf
12 changed files with 511 additions and 0 deletions
6
membership_payment_date/readme/DESCRIPTION.rst
Normal file
6
membership_payment_date/readme/DESCRIPTION.rst
Normal file
|
|
@ -0,0 +1,6 @@
|
|||
This module modifies the membership date calculation to use the effective
|
||||
payment date instead of the invoice date for membership lines.
|
||||
|
||||
It also prevents overlap on renewals: if a member renews before their current
|
||||
membership expires, the new membership starts the day after the current one
|
||||
ends.
|
||||
10
membership_payment_date/readme/USAGE.rst
Normal file
10
membership_payment_date/readme/USAGE.rst
Normal file
|
|
@ -0,0 +1,10 @@
|
|||
#. Create a membership product (fixed or variable period).
|
||||
#. Sell the product to a member via a sales order or invoice.
|
||||
#. The invoice generates a membership line with provisional dates.
|
||||
#. When the invoice is paid (e.g. bank transfer registered manually),
|
||||
the membership line dates are automatically updated:
|
||||
|
||||
* **date_from** is set to the payment date (or the day after the
|
||||
current active membership expires, in case of renewal).
|
||||
* **date_to** is recalculated based on the new date_from for
|
||||
variable-period products.
|
||||
Loading…
Add table
Add a link
Reference in a new issue