Aviate catalog guide/Getting Started Doc#641
Aviate catalog guide/Getting Started Doc#641reshmabidikar wants to merge 8 commits intokillbill:v3from
Conversation
|
|
||
| The example company used throughout this guide is *CloudSprout*, a fictional SaaS business operating in the UK and France. | ||
|
|
||
| --- |
Check warning
Code scanning / QDJVMC
Horizontal rule inspection Warning
| * Use *Aviate* to *set things up*. | ||
| * Use *Kaui* to *run billing operations*. | ||
|
|
||
| --- |
Check warning
Code scanning / QDJVMC
Horizontal rule inspection Warning
| </div> | ||
| ++++ | ||
|
|
||
| --- |
Check warning
Code scanning / QDJVMC
Horizontal rule inspection Warning
|
|
||
| This step only defines products and plans. No customers are created yet. | ||
|
|
||
| --- |
Check warning
Code scanning / QDJVMC
Horizontal rule inspection Warning
| </div> | ||
| ++++ | ||
|
|
||
| --- |
Check warning
Code scanning / QDJVMC
Horizontal rule inspection Warning
| </div> | ||
| ++++ | ||
|
|
||
| --- |
Check warning
Code scanning / QDJVMC
Horizontal rule inspection Warning
| . Select the appropriate currency (EUR or GBP). | ||
| . Save the account. | ||
|
|
||
| --- |
Check warning
Code scanning / QDJVMC
Horizontal rule inspection Warning
| </div> | ||
| ++++ | ||
|
|
||
| --- |
Check warning
Code scanning / QDJVMC
Horizontal rule inspection Warning
| </div> | ||
| ++++ | ||
|
|
||
| --- |
Check warning
Code scanning / QDJVMC
Horizontal rule inspection Warning
|
|
||
| You now have a fully working fictive SaaS company ready for demos or experimentation. | ||
|
|
||
| --- |
Check warning
Code scanning / QDJVMC
Horizontal rule inspection Warning
|
|
||
| == Introduction | ||
|
|
||
| The http://aviate.killbill.io[Aviate Catalog UI] allows you to create individual catalog entries such as products, plans, and pricelists. |
| == Introduction | ||
|
|
||
| The http://aviate.killbill.io[Aviate Catalog UI] allows you to create individual catalog entries such as products, plans, and pricelists. | ||
| This means you don’t need to manage entire catalog versions. |
There was a problem hiding this comment.
Suggestion:
'This means you don’t need to manage entire catalog versions.' -> This provides much finer granularity than the Kill Bill open-source model, which requires creating a new catalog version for any change. As a result, this approach is more dynamic and scales significantly better when managing a large number of catalog entries.
| <div> | ||
| <script async src="https://js.storylane.io/js/v2/storylane.js"></script> | ||
| <div class="sl-embed" style="position:relative;padding-bottom:calc(49.85% + 25px);width:100%;height:0;transform:scale(1)"> | ||
| <iframe loading="lazy" class="sl-demo" src="https://killbill.storylane.io/demo/elbar7il3dvs?embed=popup" name="sl-embed" allow="fullscreen" allowfullscreen style="position:absolute;top:0;left:0;width:100%!important;height:100%!important;border:1px solid rgba(63,95,172,0.35);box-shadow: 0px 0px 18px rgba(26, 19, 72, 0.15);border-radius:10px;box-sizing:border-box;"></iframe> |
There was a problem hiding this comment.
Regarding storylane:
• I think it would be best to not use Netflix as a product
• Also, could we make it a video instead of having users to click through each steps?
| <div> | ||
| <script async src="https://js.storylane.io/js/v2/storylane.js"></script> | ||
| <div class="sl-embed" style="position:relative;padding-bottom:calc(49.85% + 25px);width:100%;height:0;transform:scale(1)"> | ||
| <iframe loading="lazy" class="sl-demo" src="https://killbill.storylane.io/demo/h0mwfwocymqr?embed=popup" name="sl-embed" allow="fullscreen" allowfullscreen style="position:absolute;top:0;left:0;width:100%!important;height:100%!important;border:1px solid rgba(63,95,172,0.35);box-shadow: 0px 0px 18px rgba(26, 19, 72, 0.15);border-radius:10px;box-sizing:border-box;"></iframe> |
There was a problem hiding this comment.
Same remark on the storylane. I think a video would be better, it's a lot of clicks.
Also, call to action redirects to https://killbill.io/ \cc @pierre to be discussed.
| == Edit Plan | ||
|
|
||
| You can update *plan prices* after creation. | ||
| Other attributes (like phase duration) cannot be changed. |
There was a problem hiding this comment.
We should explain that in this case, the model is to create a new plan - and possibly retire the old one if not used anymore.
There was a problem hiding this comment.
Also, explain that this will create a new version of the plan and existing subscription will use the old plan. You could even point to the subscription manual https://docs.killbill.io/latest/userguide_subscription#_catalog_versions
| == Archive Plan | ||
|
|
||
| You can archive an existing plan. Archiving prevents creating new subscriptions corresponding to the plan. | ||
| Existing subscriptions remain active. |
There was a problem hiding this comment.
The plan remains active for existing subscriptions.
| == Delete Plan | ||
|
|
||
| You can delete an existing plan permanently. Deleting permanently removes a plan from the database. | ||
| Use this only for plans created erroneously that do not have active subscriptions. |
There was a problem hiding this comment.
Add a warning that it could break the system if there are active subscriptions.
|
|
||
| . Select the plan | ||
| . Choose *Duplicate* | ||
| . Make changes to the plan as desired |
There was a problem hiding this comment.
Explain this is purely for convenience and everything can be edited changed - as opposed to the edit functionality that only allows to update prices.
| Usage plans allow billing based on consumption: | ||
|
|
||
| . Define a *billing meter* (how usage is tracked). | ||
| . Configure *blocks/tiers*. |
There was a problem hiding this comment.
Point to the doc that defines billing meter and the kill bill doc that talks about usage: https://docs.killbill.io/latest/userguide_subscription#components-catalog-usage
Uh oh!
There was an error while loading. Please reload this page.