Paul Ghazar

My feedback

  1. 108 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    62 comments  ·  Wishlist » Members  ·  Flag idea as inappropriate…  ·  Admin →
    Paul Ghazar supported this idea  · 
  2. 60 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    35 comments  ·  Wishlist » Events  ·  Flag idea as inappropriate…  ·  Admin →
    Paul Ghazar supported this idea  · 
  3. 133 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    71 comments  ·  Wishlist » Members  ·  Flag idea as inappropriate…  ·  Admin →

    We have started analysis for this issue, and it seems that key problem is how Wild Apricot handles level changes close to renewal date. The system is currently designed to collect the full new level amount and set renewal date according to new level renewal policy. All prepaid amounts for old levels are disposed. Moreover, since no prorating occurs, the new level might be effective only for a few days.

    As a first step, we suggest to redesign how level change is working and add prorating there:

    - Level would be changed immediately, as now - Remaining portion of old membership level payment will be applied to new level - For new levels with specific renewal date (e.g. annual levels with renewals Jan 1st) apply the pro-rating settings for new applications: - Allow member to pay only a pro-rated amount of the new level fee (e.g. six months before renewal…
    An error occurred while saving the comment
    Paul Ghazar commented  · 

    I agree. This issue causes lots of confusion and additional administrative work on our volunteers to maintain/respond to member emails and manually have to update every time someone changes their membership level after receiving a reminder, but before the renewal date.

Feedback and Knowledge Base