Clint Kaul
My feedback
35 results found
-
33 votesClint Kaul
supported this idea
·
-
53 votesClint Kaul
supported this idea
·
-
9 votes
An error occurred while saving the comment -
42 votesClint Kaul
supported this idea
·
-
182 votesClint Kaul
supported this idea
·
-
143 votes
An error occurred while saving the comment Clint Kaul
commented
Hello Oleg,
I've got various questions about your "Work in Progress" posting. The first two have to do with the first paragraph.
1. At the end you say "Moreover, ... the new level might be effective only for a few days". That seems to contradict the 2nd sentence "... currently designed ... set renewal date according to new level renewal policy". Most levels will have a renewal policy of 1 year? 1 quarter? not a few days.
2. The first sentence "... how WA handles level changes close to renewal date". Yet the graphic shows a level change 4 months before the renewal date. I suspect most organizations have a "Pending-renewal" window of 14 days (the default when creating a new level)? But maybe you are trying to expand/generalize the concept from just the "Pending-renewal" window to any time a level change occurs.The reason I voted on this topic has to do with invoices and "pending-renewal". I initially had levels configured to send out an invoice and renewal reminder 14 days before the renewal date (the default when creating a new level). What I found is once the invoice is generated the member cannot change their membership level. Maybe they want to change from 1-year to 3-year but with an invoice they are forced into another 1-year membership. They have to wait until after the grace period has voided the invoice, then they can change levels and renew. I got around this by NOT sending out an invoice and simply relying on the renewal reminder emails.
Getting to your new proposal. The key for me would be "Remaining portion of old membership level payment will be applied to new level". That saves us from having to issue refunds for partially used old membership levels. Let's say our bronze level is $24/year and silver is $36/year. Using your graphic I would argue that his Sept 1, 2020 to Jan 1, 2021 dues would be (($36*(1/3) [new level pro-rated]) - (($24*(1/3) [old level pro-rated])) = $4. Correct with your proposal? Now if they are down-grading from silver to bronze they would have a credit of $4. Not sure how WA handles that.
For my organization we are based on "join date" - not a fixed renewal date. So for this case, using your graphic, I wouldn't worry about pro-rating the new level. Just reset the renewal date from Jan 1, 2021 to Sept 1, 2021. Although the fee for the level change would be pro-rated based on the "remaining portion of old membership level". So using our example (($36 [new member level]) - ($24*(1/3) [old level pro-rated])) = $28.
Clint Kaul
supported this idea
·
-
33 votesClint Kaul
supported this idea
·
-
68 votesClint Kaul
supported this idea
·
-
124 votes
Many thanks for your comments and feedback in this thread - it was super helpful for us in analysis and design of the feature.
I'm happy to announce that we're working on adding donations to compensate payment processing fees. This feature will be released later this year.Some design decisions I wanted to speak out explicitly:
1. We decided to proceed with optional donations to compensate credit card processing fees as opposed to surcharges/convenience fee.
Main reasons for this is that there are too many regulations around mandatory charges to compensate fees: it's illegal in some countries/states, there are caps on how much you could charge, etc. To avoid all of this legal complications we decided to suggest members to opt-in to compensate processing fees, as opposed to make them obligatory.
All these transactions will be recorded as donations in WA and can be later used for tax deduction.2. You…
Clint Kaul
supported this idea
·
-
5 votes
An error occurred while saving the comment Clint Kaul
commented
Our situation has a family/child relationship in the "bundle". So a parent is the bundle admin and others in the family are bundle members. When the family does an activity it would be nice if they could update their profile with this new information within the Android app. Currently, only the bundle admin (parent) can Edit their own profile and update a count. It would be nice if they could also edit the profiles of each of their bundle/family members and update those counts within the app. Currently, they would have to click on the "website" link in the app and use a browser to make these changes.
Clint Kaul
supported this idea
·
-
44 votesClint Kaul
supported this idea
·
-
105 votesClint Kaul
supported this idea
·
-
12 votesClint Kaul
supported this idea
·
-
7 votesClint Kaul
supported this idea
·
-
221 votesClint Kaul
supported this idea
·
-
11 votesClint Kaul
supported this idea
·
-
2 votesClint Kaul
shared this idea
·
-
8 votesClint Kaul
supported this idea
·
-
137 votesClint Kaul
supported this idea
·
-
83 votesClint Kaul
supported this idea
·
Oleg, can you provide details on how to do this with the "Country" provided by the Online Store? I was able to do this with a Contact "common field" I created for Country, but that's completely unrelated to the version shown by the Online Store.