-
-
Notifications
You must be signed in to change notification settings - Fork 582
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
[MIG] pos_return_voucher: Migration to 16.0 #1140
base: 16.0
Are you sure you want to change the base?
[MIG] pos_return_voucher: Migration to 16.0 #1140
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
My main concern is the same I expressed to @zamberjo and in this version is more relevant than in the one this module was proposed: this should fill the gap (if there's any) between the existing pos_loyalty
functionality (coupons, ewallets) and this module functionality.
If I thought that it would also be very convenient to hook up with the entire pos_loyalty system, when it came to collecting payments at POS it would already be solved without the need for anything else. But I have a question, can these rewards be created anonymously, without having to relate them to a client? |
Coupons at least can be. With eWallets I don't have that much experience |
@zamberjo and @chienandalu I'll tell you what I see in the module, the paython part is functional but where I'm stuck is when paying with a payment method "Vale" that has the "return_voucher" field activated in Javacript, it returns the value of "undfinded" and is not taking the value from the database correctly. In the PaymentScreen.js file the value of Let's see if you can help me to continue advancing in the migration of the module. Thanks |
@chienandalu The problem with discount and loyalty modules is they don't cover the scenario where the customer doesn't receive a refund upon returning a product. Instead, a credit balance is retained for future purchases. |
We could adapt the logic to the And allow to be able to visualize there the vouchers applied from the POS. @manuelcalerosolis , would you take care of the adaptation? If you don't see it clear we could take care of it as soon as we have less workload, I don't know how urgently you need the module. @chienandalu , do you see this solution viable? |
@zamberjo what you propose may be an improvement and make the module a little lighter, but I think it should first work as it does in v 14.0. If you can see the JavaScript issue, I'll start trying to use the |
Once the functionality of this new module has been verified in v 14.0 (https://github.com/OCA/pos/pull/996/files), and with the need to launch it in a version v 16.0 I start this PR.
Communicated with the author of the module @zamberjo, he invited me to begin the migration to v 16.0 to complete it among all those interested in this PR.
I think that the part that needs refactoring the most is Javascript, and I invite all those interested to help the migration of this module, which will be so interesting to have in OCA.