Laravel Subscribable is a flexible plans and subscription management system for Laravel, with the required tools to run your SAAS like services efficiently. It's simple architecture, accompanied by powerful underlying to afford solid platform for your business.
We invest a lot of resources into creating best in class open source packages. You can support us by buying one of our paid products.
We highly appreciate you sending us a postcard from your hometown, mentioning which of our package(s) you are using. You'll find our address on our contact page. We publish all received postcards on our virtual postcard wall.
The idea is inspired by rinvex/laravel-subscriptions
You can install the package via composer:
composer require samehdoush/subscriptions
php artisan subscriptions:install
You can publish and run the migrations with:
php artisan vendor:publish --tag="subscriptions-migrations"
php artisan migrate
You can publish the config file with:
php artisan vendor:publish --tag="subscriptions-config"
This is the contents of the published config file:
return [
];
Optionally, you can publish the views using
php artisan vendor:publish --tag="subscriptions-views"
$subscriptions = new Samehdoush\Subscriptions();
echo $subscriptions->echoPhrase('Hello, Samehdoush!');
** Subscriptions** has been specially made for Eloquent and simplicity has been taken very serious as in any other Laravel related aspect. To add Subscription functionality to your User model just use the \Samehdoush\Subscriptions\Traits\HasPlanSubscriptions
trait like this:
namespace App\Models;
use Samehdoush\Subscriptions\Traits\HasPlanSubscriptions;
use Illuminate\Foundation\Auth\User as Authenticatable;
class User extends Authenticatable
{
use HasPlanSubscriptions;
}
That's it, we only have to use that trait in our User model! Now your users may subscribe to plans.
Note: you can use
HasPlanSubscriptions
trait on any subscriber model, it doesn't have to be the user model, in fact any model will do.
$plan = \Samehdoush\Subscriptions\Models\Plan::create([
'name' => 'Pro',
'description' => 'Pro plan',
'price' => 9.99,
'signup_fee' => 1.99,
'invoice_period' => 1,
'invoice_interval' => 'month',
'trial_period' => 15,
'trial_interval' => 'day',
'sort_order' => 1,
'currency' => 'USD',
]);
// Create multiple plan features at once
$plan->features()->saveMany([
new PlanFeature(['name' => 'listings', 'value' => 50, 'sort_order' => 1]),
new PlanFeature(['name' => 'pictures_per_listing', 'value' => 10, 'sort_order' => 5]),
new PlanFeature(['name' => 'listing_duration_days', 'value' => 30, 'sort_order' => 10, 'resettable_period' => 1, 'resettable_interval' => 'month']),
new PlanFeature(['name' => 'listing_title_bold', 'value' => 'Y', 'sort_order' => 15])
]);
You can query the plan for further details, using the intuitive API as follows:
$plan = \Samehdoush\Subscriptions\Models\Plan::find(1);
// Get all plan features
$plan->features;
// Get all plan subscriptions
$plan->planSubscriptions;
// Check if the plan is free
$plan->isFree();
// Check if the plan has trial period
$plan->hasTrial();
// Check if the plan has grace period
$plan->hasGrace();
Both $plan->features
and $plan->planSubscriptions
are collections, driven from relationships, and thus you can query these relations as any normal Eloquent relationship. E.g. $plan->features()->where('name', 'listing_title_bold')->first()
.
Say you want to show the value of the feature pictures_per_listing from above. You can do so in many ways:
// Use the plan instance to get feature's value
$amountOfPictures = $plan->getFeatureBySlug('pictures_per_listing')->value;
// Query the feature itself directly
$amountOfPictures = \Samehdoush\Subscriptions\Models\PlanFeature::where('slug', 'pictures_per_listing')->first()->value;
// Get feature value through the subscription instance
$amountOfPictures = \Samehdoush\Subscriptions\Models\PlanSubscription::find(1)->getFeatureValue('pictures_per_listing');
You can subscribe a user to a plan by using the newSubscription()
function available in the HasPlanSubscriptions
trait. First, retrieve an instance of your subscriber model, which typically will be your user model and an instance of the plan your user is subscribing to. Once you have retrieved the model instance, you may use the newSubscription
method to create the model's subscription.
$user = User::find(1);
$plan = \Samehdoush\Subscriptions\Models\Plan::find(1);
$user->newPlanSubscription('main', $plan);
$user->newPlanSubscriptionWithOutTrail('main', $plan); // without trial
The first argument passed to newSubscription
method should be the title of the subscription. If your application offer a single subscription, you might call this main
or primary
, while the second argument is the plan instance your user is subscribing to, and there's an optional third parameter to specify custom start date as an instance of Carbon\Carbon
(by default if not provided, it will start now).
You can change subscription plan easily as follows:
$plan = \Samehdoush\Subscriptions\Models\Plan::find(2);
$subscription = \Samehdoush\Subscriptions\Models\PlanSubscription::find(1);
// Change subscription plan
$subscription->changePlan($plan);
If both plans (current and new plan) have the same billing frequency (e.g., invoice_period
and invoice_interval
) the subscription will retain the same billing dates. If the plans don't have the same billing frequency, the subscription will have the new plan billing frequency, starting on the day of the change and the subscription usage data will be cleared. Also if the new plan has a trial period and it's a new subscription, the trial period will be applied.
Plan features are great for fine-tuning subscriptions, you can top-up certain feature for X times of usage, so users may then use it only for that amount. Features also have the ability to be resettable and then it's usage could be expired too. See the following examples:
// Find plan feature
$feature = \Samehdoush\Subscriptions\Models\PlanFeature::where('name', 'listing_duration_days')->first();
// Get feature reset date
$feature->getResetDate(new \Carbon\Carbon());
There's multiple ways to determine the usage and ability of a particular feature in the user subscription, the most common one is canUseFeature
:
The canUseFeature
method returns true
or false
depending on multiple factors:
- Feature is enabled.
- Feature value isn't
0
/false
/NULL
. - Or feature has remaining uses available.
$user->planSubscription('main')->canUseFeature('listings');
Other feature methods on the user subscription instance are:
getFeatureUsage
: returns how many times the user has used a particular feature.getFeatureRemainings
: returns available uses for a particular feature.getFeatureRemainingsOrText
: returns available uses for a particular feature but if -1 return text unlimited.getFeatureValue
: returns the feature value.
All methods share the same signature: e.g.
$user->planSubscription('main')->getFeatureUsage('listings');
.
In order to effectively use the ability methods you will need to keep track of every usage of each feature (or at least those that require it). You may use the recordFeatureUsage
method available through the user subscription()
method:
$user->planSubscription('main')->recordFeatureUsage('listings');
The recordFeatureUsage
method accept 3 parameters: the first one is the feature's name, the second one is the quantity of uses to add (default is 1
), and the third one indicates if the addition should be incremental (default behavior), when disabled the usage will be override by the quantity provided. E.g.:
// Increment by 2
$user->planSubscription('main')->recordFeatureUsage('listings', 2);
// Override with 9
$user->planSubscription('main')->recordFeatureUsage('listings', 9, false);
Reducing the feature usage is almost the same as incrementing it. Here we only substract a given quantity (default is 1
) to the actual usage:
$user->planSubscription('main')->reduceFeatureUsage('listings', 2);
$user->planSubscription('main')->usage()->delete();
For a subscription to be considered active one of the following must be true
:
- Subscription has an active trial.
- Subscription
ends_at
is in the future.
$user->subscribedTo($planId);
Alternatively you can use the following methods available in the subscription model:
$user->planSubscription('main')->active();
$user->planSubscription('main')->canceled();
$user->planSubscription('main')->ended();
$user->planSubscription('main')->onTrial();
Canceled subscriptions with an active trial or
ends_at
in the future are considered active.
To renew a subscription you may use the renew
method available in the subscription model. This will set a new ends_at
date based on the selected plan and will clear the usage data of the subscription.
$user->planSubscription('main')->renew();
Canceled subscriptions with an ended period can't be renewed.
To cancel a subscription, simply use the cancel
method on the user's subscription:
$user->planSubscription('main')->cancel();
By default the subscription will remain active until the end of the period, you may pass true
to end the subscription immediately:
$user->planSubscription('main')->cancel(true);
// Get subscriptions by plan
$subscriptions = \Samehdoush\Subscriptions\Models\PlanSubscription::byPlanId($plan_id)->get();
// Get bookings of the given user
$user = \App\Models\User::find(1);
$bookingsOfSubscriber = \Samehdoush\Subscriptions\Models\PlanSubscription::ofSubscriber($user)->get();
// Get subscriptions with trial ending in 3 days
$subscriptions = \Samehdoush\Subscriptions\Models\PlanSubscription::findEndingTrial(3)->get();
// Get subscriptions with ended trial
$subscriptions = \Samehdoush\Subscriptions\Models\PlanSubscription::findEndedTrial()->get();
// Get subscriptions with period ending in 3 days
$subscriptions = \Samehdoush\Subscriptions\Models\PlanSubscription::findEndingPeriod(3)->get();
// Get subscriptions with ended period
$subscriptions = \Samehdoush\Subscriptions\Models\PlanSubscription::findEndedPeriod()->get();
** Subscriptions** uses 4 models:
Samehdoush\Subscriptions\Models\Plan;
Samehdoush\Subscriptions\Models\PlanFeature;
Samehdoush\Subscriptions\Models\PlanSubscription;
Samehdoush\Subscriptions\Models\PlanSubscriptionUsage;
composer test
Please see CHANGELOG for more information on what has changed recently.
Please see CONTRIBUTING for details.
Please review our security policy on how to report security vulnerabilities.
The MIT License (MIT). Please see License File for more information.