laraplans | SaaS style recurring plans for Laravel | Ecommerce library

That's the magic of Laravel.

You get the user model by calling Auth::user() so there you already have the relevant Model that you're looking for. That of the authenticated user.

Now inside the Model-Definition you likely have a method subscription which returns the Related Model. (You probably added some logic for the 'Pro' parameter).

Laravel here is developed with convention-over-configuration in mind and knows which rows in the table actually to look for. So what you need is a 'id' in each table, and due to the relationship a 'user_id' in the table holding the subscriptions. There is a way to define that differently in case. Here is the doc: https://laravel.com/docs/5.4/eloquent-relationships

So you got the plan from the relevant user, I don't see anything bad here.

===

You use $user->subscription but do an ->subscriptions() instead (notice the plural 's'). Use a loop (or ->first()) since you get plans and not one plan

Right now you always pass 'Pro' in but the authenticated user might now be subscribed to the Pro-Plan and hence returns null. Subscriptions returns the hasMany relation. From there /not tried/ you can loop over the result and get the names of the plan or whatever you need. Notice: It's a hasMany, although the user might just have subscribed to one subscription. So you need to loop or get the first result.