Skip to content
This repository has been archived by the owner on May 26, 2023. It is now read-only.

How to define the same plans with different payment periods? #90

Closed
boryn opened this issue Aug 18, 2021 · 2 comments · Fixed by #119
Closed

How to define the same plans with different payment periods? #90

boryn opened this issue Aug 18, 2021 · 2 comments · Fixed by #119
Assignees
Labels
enhancement New feature or request
Milestone

Comments

@boryn
Copy link
Contributor

boryn commented Aug 18, 2021

Hi @bpuig! Actually what is your way to define the same plan but with different payment periods? I mean we want to have "Basic" plan paid monthly or yearly. I'd go with tags basic-monthly and basic-yearly defining appropriately the price and invoice_interval fields. But with this approach I come into a problem of grabbing and presenting the all payment options for the "Basic" tag. It's quite cumbersome to filter the tag field by LIKE 'basic-%'.

PS. All these "Basic" plans use the same feature set. With my approach I need to duplicate the definitions at plan_features.

@bpuig bpuig added the enhancement New feature or request label Sep 5, 2021
@bpuig
Copy link
Owner

bpuig commented Sep 5, 2021

This would be a new part of the package, because plan per se it's the same, just that you pay 12 months in advance. In v5, this would be (just by memory, don't trust me) something like renew(12) and pay whatever quantity.

The solution is a new "plan prices" part where you can input plan, number of periods and price. It's a good idea, but maybe for v6.

Edit: This is also related to #90 . So maybe we can do both in v6

@bpuig bpuig added this to the v6.0.0 milestone Sep 5, 2021
@boryn
Copy link
Contributor Author

boryn commented Sep 10, 2021

Yes, we can renew whatever number of periods having accepted whatever amount of money, but the exact definition of plans with their prices is often used to display pricing tables in the front-end. And they are often got fetched through API and that's why it's important to have all the pricings in the plans table.

At this moment I use this basic-monthly / basic-yearly or even basic-monthly-usd / basic-yearly-usd / basic-monthly-eur / basic-yearly-eur approach, but it's not optimal and thought you have some better solution for now.

@bpuig bpuig self-assigned this Jan 23, 2022
@bpuig bpuig linked a pull request Feb 19, 2022 that will close this issue
2 tasks
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
enhancement New feature or request
Projects
Status: Done
Development

Successfully merging a pull request may close this issue.

2 participants