Question regarding subscription and contract modules

[flotho]

Hi everyone,

I can see that subcription module is now part of the OCA repo. I'm wondering if there is any ducplicate usage wuth contract module ? What are the use case that will lead us to choose subscription instead of contract ?

Regards

[rousseldenis]

That's indeed a good question as functionally, it is quite equivalent...

@carlos-domatix @simahawk @francesco-ooops

[francesco-ooops]

I have only followed development and haven't done a full functional analysis myself, but for what I understand contract modules somehow have reached a complexity level where it was difficult to easily attend customer's requests (you can find many comments on the tone of https://github.com/OCA/contract/pull/971#issuecomment-1652404292)

Just consider this repo has approx the same number of issues of huge repos like sale or purchase-workflow...

[chrisandrewmann]

I agree that subscription_oca seems much more "lightweight" and has less of a chain of dependencies to maintain. It's also capable of more common use cases such as generating a sales order or invoice, as well as subscribable products. I think what would make the real icing on the cake would be to add automatic payments option and also a simple area in the user portal to reflect their subscriptions allowing customers to cancel them.

[flotho]

AFAICR, subscription seems to be the future of OCA/Contract repo

[flotho]

for the record : https://github.com/OCA/contract/pull/1029

[github-actions[bot]]

There hasn't been any activity on this issue in the past 6 months, so it has been marked as stale and it will be closed automatically if no further activity occurs in the next 30 days. If you want this issue to never become stale, please ask a PSC member to apply the "no stale" label.

[flotho]

actually here is the reasons : https://github.com/OCA/contract/issues/1108