Recommended way to save features of subscription plan?

[atinder]

Additional table or column. what do you recommend?

[excid3]

@atinder I've been just using a separate table. We've been considering adding it to the gem as well.

You can also just hardcode a hash as a constant since the plans aren't likely to change often.

[archonic]

I'd like to add my 👍 for a convention on storing products and plans. It would be nice to have enough data locally to display a form which can switch between products and plans.

[deanpcmad]

I can work on adding this as it was an annoyance for me that it wasn't already included.

Would we want 2 models, such as Product and Price? As such a Product (e.g. "My SaaS Plan"), can have many prices (e.g. "$5 monthly" or "$50 yearly")

[excid3]

Unless you're selling multiple products, there's not a need for a Product model.

[deanpcmad]

True. Maybe just a Plan model then?

[excid3]

As far as Pay's concerned, probably.

I would probably call it Pay::Price since we'll want to support one-time purchases and not just subscriptions.

Something like this:

Pay::Price

• name:string
• description:string
• amount:integer (cents)
• currency:string ("usd")
• metered:boolean
• unit_label:string
• charge_per_unit:boolean
• trial_period_days:integer
• hidden:boolean

It probably needs a JSON column for handling Stripe, Braintree, Paddle, etc, IDs, Stripe Tax, and any other details.

Alternatively, you could add processor and processor_id and duplicate this for each payment processor.