Hello Patrice:
You can absolutely do this, but it will require a tiny bit of development to make it happen. First, you'd use the reward points feature and repurpose it for this use case.
https://support.upendoven...118766-Reward-Points You'd want to have a product that is called whatever these credits are called, and the quantity would be the number of points they're ordering. You'd also have reward points enabled and update the settings, localization, and views to correctly display the point system name and branding.
Whenever a customer purchases the points product, the quantity and/or the dollar amount would end up directly relating to the number of points the customer has access to use during checkout.
There will also be a few other things that you'd have to do. For example, you'd want to think through whether the customer goes through the standard checkout experience when purchasing products with credits (reward points) or not, and what additional work with it require for your team either way. You'd also likely have a custom user experience that's different in browsing and purchasing that's different between the credit products and the reward points product.
Finally, you'd also want to implement a user experience to show and/or notify customers of when their points need to be used before they expire. You can use a combination of a scheduled job and viewset updates to accomplish this. The database schema already includes the transaction date, so you can use that to determine the expiration date as well. The scheduled job would then not only change the user experience, but also expire points.
Will Strohl, Upendo Ventures
Hotcakes Cloud |
Get Support |
Code Support Official Cloud & Support provider for Hotcakes