Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[RFC] website_portal_contract: Website Contract Management #45

Closed
lasley opened this issue Dec 2, 2016 · 16 comments
Closed

[RFC] website_portal_contract: Website Contract Management #45

lasley opened this issue Dec 2, 2016 · 16 comments

Comments

@lasley
Copy link
Contributor

lasley commented Dec 2, 2016

This module will provide website views for customer management of their existing contracts.

It will add a new field website_template_id to the account.analytic.contract model (and subsequently the account.analytic.account model). This field will act in the same way that the quote template works for website sales. A default template will be provided.

It will provide a new section in the website My Account, similar to the existing Your Quotes, Your Orders, etc & will be called Your Contracts.

In the Your Contracts listing, the following fields will be displayed in the table:

  • Display Name
  • Debit
  • Credit
  • Balance

Clicking a contract in the listing will take you to the website template associated with that contract.

@rafaelbn
Copy link
Member

rafaelbn commented Dec 2, 2016

It's more website_portal_contract, isn't it?

@lasley
Copy link
Contributor Author

lasley commented Dec 2, 2016

@rafaelbn - Yup that's a better name for sure

@lasley lasley changed the title [RFC] website_contract: Website Contract Management [RFC] website_portal_contract: Website Contract Management Dec 2, 2016
@dreispt
Copy link
Sponsor Member

dreispt commented Jan 6, 2017

Add to the wishlist a "Your Issues" feature, and "Open an Issue"

@pedrobaeza
Copy link
Member

Isn't that already on website_issue?

@dreispt
Copy link
Sponsor Member

dreispt commented Jan 6, 2017 via email

@vonpupp
Copy link

vonpupp commented Mar 15, 2017

Using a module such as this would it be possible to automatically charge a credit card? Such as a subscription monthly payment?

@lasley
Copy link
Contributor Author

lasley commented Mar 15, 2017

@vonpupp - That is not within scope right now, but autopay is part of my long-term plans. That will likely be in a separate module though in order to allow for usage outside of this context.

@vonpupp
Copy link

vonpupp commented Mar 15, 2017

Great @lasley. I am not aware of any module right now that allows recurrent payments. Perhaps the closest might be the memberships module. I think it would be very nice to have something similar to the Odoo enterprise feature subscriptions.

There is also an effort on the donation module to achieve recurrent payments. Wouldn't it be possible to create some sort of "fit all" recurrent payment module that integrates with contracts, memberships and donations?

@pedrobaeza
Copy link
Member

AFAIK Odoo enterprise doesn't handle either automatic recurrent payment. And this is very closely related with payment gateways (Paypal and so on) to allow this option.

@vonpupp
Copy link

vonpupp commented Mar 18, 2017

I have not tried this myself but Fabien stated that it is supported on the Enterprise version @pedrobaeza. I believe this feature would be very important and would boost Odoo adoption IMHO.

If I have some help and somebody to count on to provide some guidance I would gladly help. As I said I am a beginner with Odoo, so patience is important :)

@pedrobaeza
Copy link
Member

OK, I see, but he is saying that it works only with Ingenico and Stripe payment gateways, and in Enterprise version. There are 2 ways to do it:

  1. Automatically making the charge every period, which has to be supported by payment gateway, and that you are authorized to make it (in Spain it's very difficult to get this authorization).
  2. Sending a reminder each period with a link to make the payment.

Second is more feasible, but doesn't guarantee the payment.

@lasley
Copy link
Contributor Author

lasley commented Mar 18, 2017

v10 added a lot of server to server interaction with some of the payment gateways, so this did become a bit more feasible from the tech end of things - but there is still no unified interface, so each automation would need to be created independently as Odoo SA has done for Stripe & Ingenico.

The mental plan was to create a base_payment_auto module to provide the base interface, then a payment_authorize_auto to cover the scope of my needs. In the US we can charge whatever the hell we want, whenever we want; so I'm not worried about legalities. The downside are chargebacks, but that's a merchant consideration IMO.

I can create an RFC for this if you guys want - it's a only rough idea at this point though, and is pretty far off in our dev schedule.

@pedrobaeza
Copy link
Member

For now I don't have that need, so you can still retain it for more time to improve it if you want.

@vonpupp
Copy link

vonpupp commented Mar 19, 2017

Great proposal @lasley.

Having a request made by email automatically (i.e: monthly) would be also something feasible that would indeed be better than nothing, perhaps both of these proposals would cover all the needs of recurrent payments.

For instance in Brazil we have a quite common payment method called "boleto", which is some sort of payment order with a bar code that the customer pays directly at the bank / ATM or phone. If the donors could receive these boletos each month by email it would be awesome.

I am still trying to integrate this on v10 without the need of the localization for the sake of simplicity. The NGO I am helping need more the financial part rather than the accounting part, so the simpler the better.

@pedrobaeza
Copy link
Member

This is already implemented, isn't it?

@lasley
Copy link
Contributor Author

lasley commented Dec 2, 2017

Indeed it is, I guess we just forgot to link to and close the RFC!

https://github.com/OCA/contract/tree/10.0/website_portal_contract

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants