[Aleksey]

Dear testers!

Today we have many people asking about subscription management in LemonStand. We are considering to start working on this module soon. But we need your help in order to find out your requirements and wishes. As everything in LemonStand the module implementation will be as simple as possible, and as beautiful as possible.

Please post your ideas about the module features. Describe specific tasks, which you, or your customers would like to be solved on the store. What do you think about billing plans? How flexible should they be? Should they be product-specific or store-wide? What do you think about credit card charging? Should it be automatic or manual? Please post us any your ideas. We are listening!

Aleksey

[SoccerGuy3]

Your timing is good. I am starting on a site very soon that is going to need this very feature! Here are the specs I have been discussing with my client:

* Shopping cart for physical items (clothing, individual magazines, etc)
* Shopping cart + subscription management (for magazine subscriptions, with recurring billing or subscriber management features)
* Shopping cart + electronic subscription management (for electronic content, members only area, etc)

The subscriber management I would envision would have the ability to generate reports and exports of subscriber info, rebilling, tracking of anniversary dates (for subscriptions, not marriage!), warning emails that subscription is about to run out (click here to renew!).

The members only stuff would be pretty straight forward. Something where a password was issued by the system maybe that was tied to a fixed time period. That password would give access to certain areas of the site... hmmm... maybe this isn't a cart function. Gotta think about that.

Holler if you need more detail.

[Aleksey]

Hi, SoccerGuy3!

Thank you! How the billing should work for magazine subscriptions, for example? How the billing date should be defined - each month, starting from the order date? For example, if I subscribed today, April 30th, the next billing date for me would be May 30th?

How the rebilling should work?

Aleksey

[SoccerGuy3]

Hey Aleksey, sorry I haven't responded, didn't realize you had responded. To answer the question, most subscriptions are annual. Meaning if I subscribe on July 1, the next billing is due on June 30 to continue the subscription.

[vibrantpixel]

A few of my clients would like is a subscription module like:
1) Software Subscription
- Billing Options: Monthly and/or Annually
- A way to contact the store to see if they have a current registration and what options are enabled.
- Options: They would like to have options for number of Users and other additional add-on’s. (i.e. Monthly Software Subscription with 5 Users and 2 additional modules)
- Client has the ability to change/cancel their subscriptions from the store.

2) Membership Subscription
- Billing Options: Monthly and/or Annually
- Manage multiple subscriptions for multiple sites/memberships.
- A simple way for clients to be able to login and be redirected to a protected blog and/or forum.
- Client has the ability to change their subscriptions from the store.

[Aleksey]

Hi, vibrantpixel!

Thank you the update. We appreciate it a lot. We are going to start working on the subscriptions module soon after the release.

Aleksey

[vibrantpixel]

Great!! We are so excited for the release.

[vibrantpixel]

How is this coming along? Any progress on this module?

[Aleksey]

Quote

How is this coming along? Any progress on this module?

Hi!

We were not starting any large-scale tasks before the release. Today we released and after completing some minor tasks we will begin working on the Subscriptions.

Thanks!

[vibrantpixel]

Any updates with this module? I have a few clients asking for this module.

[Aleksey]

Quote

Any updates with this module? I have a few clients asking for this module.

Hi! Sorry, guys, still no updates. The feature is sitting on the top of our to-do list, but we cannot begin working on the implementation, because of multiple distracting smaller tasks, including internal business needs. Although the release has passed, we still extending the website and My Account area in order to prepare ourselves to upcoming marketing actions. When we finish this work, we will have more time for the large-scale tasks.

Thanks

[bohara]

I am just evaluating lemonstand. So far I am in love with the exception of the template editing (but it looks like there is a solution available).

I know that this is an old thread, but I have a need to sell subscriptions for physical goods. These would happen monthly (could easily be quarterly, or yearly). in my case I am selling consumable liquids.

The use case is as follows:
----------------------------------

1. I need the user to be able to select from multiple products could be like a grouped product if that allows them to enter separate quantities of different quantities. it would be great if the could select the frequency (monthly, weekly, etc)

2. Billing would be credit card only. Ideally it would be charged automatically, and notice would be emailed if the was an issue such as CC expiration.

I would also be acceptable if an order was automatically created, and an email was sent requesting payment before shipment.

3. It would be great if this functioned as a separate product not combined with the original individual products.

I think my use case would also work in for things like coffee, wine, and vitamin subscriptions.

I would gladly pay extra for a module that allowed this functionality.

-----------------------------------

I must say you guys have a fantastic product here. I just gave up on magento, and have evaluated, cs-cart, oscommerce, wordpress (shopp plugin), interspire, big commerce, and a few others.

What you have here seems to be impossibly good, compared to what is currently available. You even have documentation!

Keep up the good work

[spot13]

I'm also looking for this feature. The recurring billing would not have to be automated for me, we would require customers to return to the site, login and renew a subscription. Is this by any chance in the development pipe?

[Aleksey]

Hi, guys!

We will implement automatic payments after publishing the subscriptions module. Which payment gateways you use? Each gateway has its own API, and not all gateway support recurring payments and storing customer CC data on the gateway side. As we cannot store any CC information in LemonStand gateway, your payment gateway should support this feature.

Thank you

[skinnydope]

Is there an updated delivery time on the subscriptions model? And what gateways will you support at release. I am very interested in this functionality and will choose the gateway that has the easiest implementation with your system. thanks.

[Aleksey]

Quote

Is there an updated delivery time on the subscriptions model? And what gateways will you support at release. I am very interested in this functionality and will choose the gateway that has the easiest implementation with your system. thanks.

Hi!

We are working on the App Store, which is needed for selling our new premium modules. The ETA is still undefined and I do not want to speculate. Regarding the payment gateways - most likely we will start with the Authorize.Net and Braintree (http://www.braintree...tsolutions.com/).

Thank you

[skinnydope]

Any updates on the App store and the subscriptions module?

[Aleksey]

 skinnydope, on 02 March 2011 - 07:09 AM, said:

Any updates on the App store and the subscriptions module?

Hi! Marketplace (we renamed AppStore to Marketplace) is just around the corner. All business processes are already developed and now we're working on the front-end user interface. Watch for the announces in the blog and Twitter.

Thanks

[chintankotadia]

Hello Aleksey,

When will be subscription module released ?
Thank you.

[Danny]

 chintankotadia, on 03 March 2011 - 12:20 AM, said:

Hello Aleksey,

When will be subscription module released ?
Thank you.

The subscriptions module will be released soon after the Marketplace goes live. It is dependent on the Marketplace.
The blog post I linked to gives an estimated timeline for this.