Jump to content


Replying to Traditional Magazine Membership Model?


Post Options

  or Cancel


Topic Summary

Elise Alley

Posted 11 March 2014 - 03:50 PM

Hey Rob,

I definitely can and will add these as feature requests.  I don't have a timeline, however, for if/when they will be added.

Let us know if you have any additional questions.

Thanks,

Elise

Posted 10 March 2014 - 05:53 PM

Thanks for the response, Elise. That's helpful.

I might not have been clear about one thing: part of the goal behind my request is to allow the subscription to automatically renew. Traditional print magazine subscriptions do require a manual payment for each renewal, but I'm thinking more in line with digital ones—which typically operate with auto-renewing subscriptions (e.g. ConsumerReports.org).

View PostElise Alley, on 10 March 2014 - 04:34 PM, said:

What you'd need to do is make, for instance, a March 2014 Membership product using Recurring Payments so that the membership expires after a month.  Then, whoever purchases it, will have access to the posts for that month.  Then, in April 2014, they'd have to buy the new Membership product for April to have access to the posts for that month.  

With my clarification above, the problem with this scenario is that it doesn't automatically renew the way digital magazine subscriptions do. It requires the user to manually go back every time a new issue comes out and buy the next issue.

So it seems there's three basic features/functions that Exchange does not currently have that would work together to produce what I'm looking for:
  • Automatic renewal memberships that, when cancelled, would be able to leave purchased content behind for the user.
  • Membership that can display content based on when the membership was activated (e.g. if someone buys the membership in March, March will display...but if the same membership is purchased in April, only April will display).
  • Memberships that can roll out [permanant] access to other content on specific days (I think I saw this as a feature-request related to "content drip" functionality in the appropriate Exchange feature requests Trello board).
If my understanding is correct...would it be possible to have those features added to the feature requests?

Thanks so much!

Rob

Elise Alley

Posted 10 March 2014 - 04:34 PM

Hey Rob,

You could make something like this work in Exchange with the Membership and Recurring Payments add-ons.  

What you'd need to do is make, for instance, a March 2014 Membership product using Recurring Payments so that the membership expires after a month.  Then, whoever purchases it, will have access to the posts for that month.  Then, in April 2014, they'd have to buy the new Membership product for April to have access to the posts for that month.  

If, however, you make a product that it automatically recurring or have them purchase the same product each month instead of them purchasing a new product every month, they will have access to anything that's ever been added to that product unless you remove it from that product (so your back-issues).  

Let us know if you have any additional questions.

Thanks,

Elise

Posted 10 March 2014 - 09:32 AM

Hi,

I was wondering if iThemes Exchange (with any appropriate add-ons) supported a fairly traditional magazine membership model. I looked through the documentation, but it doesn't look like Exchange supports this use case...just wanted to check and make sure I wasn't missing something.

Here's the use case:
In sort of a traditional magazine model, a user subscribes to a publication and gets access to a new issue (in this case, a collection of Wordpress posts) every subscription period (e.g. a month). The subscription doesn't give them access to all back-issues (from before they subscribed), just the current issue and all future issues until they cancel. If they cancel, they retain access to all the issues they received during their subscription period. If they renew, the process begins again—they receive all issues that come out while they are subscribed.

From what I can tell in Exchange terminology this almost treats each issue like a separate product grouped under an overarching membership. So when the person signs up for a membership, they are actually "buying" a new issue each month.

Any ideas if this is doable (somehow) in the current Exchange version?

Thanks,
Rob

Review the complete topic (launches new window)