Subscriptions module

[MikeAlhayek]

Subscription Module

We need to develop a robust subscription module to enable sites to handle various subscription types. The module should offer the following features:

Key Features:

1. Subscription to Content Items:

   • Allow users to subscribe to individual content items. For instance, you can create a content type called Member and enable users to purchase a subscription to a Member item.

2. Subscription to Sites:

   • Provide a mechanism for subscribing to a site. For example, you can create a content type named SitePlan, which users can subscribe to. Additionally, the SitePlan should automatically generate a tenant upon subscription.

3. Multiple Payment Providers:

   • Implement support for multiple payment providers to offer flexibility in payment processing.

4. Stripe Integration:

   • Integrate with Stripe to support seamless online payments.

5. Pay-Later Option:

   • Add a "pay-later" payment provider for handling offline payment processing.

6. Admin UI for Subscription Management:

   • Develop an intuitive admin interface for managing subscriptions, including viewing and modifying subscription details.

7. Admin Dashboard Widgets:

   • Create widgets for the admin dashboard to display key subscription metrics, such as:
     • Total number of subscribers
     • Monthly revenue

8. User Subscription Management:

   • Enable subscribers to manage their own subscriptions, including:
     • Changing subscription levels
     • Canceling subscriptions
     • Updating payment methods
     • Viewing payment history and printing receipts

[giannik]

looks promising @MikeAlhayek .
Do you plan on making a demo in one of the orchardcore meetings ?

[MikeAlhayek]

@giannik that is the plan. Just need to find time to finish it first :)

[davidpuplava]

Hi @MikeAlhayek - I've been working on a fork of the ma/subscribtions branch and I'm particularly interested in one-time payments for digital products.

Does it make sense to refactor the SubscriptionFlowStep stuff into a different library (maybe Payments itself) that can be used by both Subscriptions and Products modules?

I ask because I'd like to have the same checkout/payment experience for buying a product, and it would be great to have the user registration step there for a buying customer to optionally create an account.

My reasoning is because purchasing a subscription and a product are essentially the same thing except the payment terms are different.

Another possible solution is to put the step-by-step flow stuff into the Products projects and treat a subscription as a special ProductType similar to Good and Service.

[MikeAlhayek]

Hey @davidpuplava , sorry I feel like I abandoned this module due to other work I have been working on.

Using this module, you should be able to set the stereotype of any content type to Subscription and this content item will be available for subscription. So if you have a content type called Product, giving it Subscription should give you the experience you are looking for. Did you try that?

[davidpuplava]

giving it Subscription should give you the experience you are looking for

Thanks @MikeAlhayek - I'll give it a try. No worries on abandoning the module, the AI and SignalR stuff looks great.

[MikeAlhayek]

@davidpuplava its looking better and better. Planning on another demo in Tuesday if you are interested in attending.

We'll try to work on the subscription module next. Hopefully you'll be able to complete it before then :)

[davidpuplava]

Awesome, I'll see what I can do!