may be we have two options
- start with a subset of what contract management is in a simplified design then add features as custom
- start with universal contract management concepts in a standardized design and then add specific custom behaviors.
I favour the second because first one reminds me Odoo too much, but this is an open discussion and I will listen everybody and probably the right thing to do is in-between the two options.
On the different contracts I deal with (either because I’m vendor or customer) I see many concepts that Tryton would be good at.
in telephony, when I agree on new pricing it becomes effective but I keep my contract and options.
in my insurance, I can declare a new driver of my car, it is an amendment, not a new contract.
A service provider proposed to suspend the service during my holidays
when a customer complains, I can offer him to extend the duration of the contract for free as a compensation
If we choose option 1, then probably we will have several contract modules to cover different cases.
If we could find a generic, basic way to implement generic case, then many kinds of contract management could be built over it.
Any opinion ?