ComputeStacks uses billing plans as a rule set for determining the real time price for a given resource. We also use this for generating the price matrix on order forms.
You can create as many billing plans as you want, but only one may the default. This is useful for creating custom or special pricing for a different set of users.
SECTIONS
<aside> 👉 If no price rule exists for a given scenario (e.g. currency + region + quantity), ComputeStacks will default to a price of 0.00.
</aside>
When creating a billing plan, you will have an option to set the term used.
It’s important to note that even with monthly pricing, ComputeStacks will still treat that as post-bill. So, when a user orders a monthly package, they will get a usage item in the database for that through the end of the month, however, we are expecting that your billing system will not generate an invoice until the following month. This is an important distinction to ensure upgrades, downgrades, and cancellations are handled appropriately.
<aside> ⚠️ Pricing for overage storage (backup, temporary, volume) will always be per-hour.
</aside>
Once you have your billing plan, you may assign it to a particular user group.
A product is a separate object from Billing Plans, which allow you to define it once, and use it in multiple plans.
Products are the base for packages, so you must define this first prior to creating a package.
External ID
This is available in WebHooks and API Calls. This is generally used by billing integrations to identify this product.