Community Support Forums

I see that custom capabilities are meant to be one-time charges. However, trying to do custom capabilities with membership levels creates a lot of extra membership levels.

i.e. Bronze, Silver, Gold, with +custom1 and +custom2 would require 12 membership levels.. which if you then lay out in a table of features becomes pretty large. (Base Package, Base Package + custom1, Base Package + custom2, Base Package + Custom1 + Custom2).

Thinking along the lines of the GoDaddy model, where you sign-up for the base product, then there's all kinds of upselling done prior to the close.

We're using s2Member Pro.

Yeah, I see what you mean, Ryan.

I'd suggest looking at the membership levels to make sure you really need them. Levels give incremental access, where a level gives access to content at that level or lower. If you don't require this characteristic, maybe you can handle everything with ccaps.

Now, that may still require a large table if laid out the way you described. You could, instead, have two tables: one for the base package, then another table for the extras which can apply to either package.

I hope that helps.