Zentitle2 - setting up products, plans and offerings

Learn how to do the basic setup steps for your products

Watch more videos about how to license your software and increase revenues

1000s of software companies have used Zentitle to launch new software products faster and control their entitlements easily, many going from startup to IPO on our cloud software license management solutions

Software Licensing Customer LogosSoftware Licensing Customers

Zentitle - the Enterprise-Class Software Monetization Platform

18 Years+

Track Record

$1B+

Revenues Protected

300M+

Transactions / Month

99.9%+

Uptime SLA for 10 Years+

Zentitle supports 100M's users 24x7x365 for the world's leading SaaS, Software and IoT companies

Your long-term partner for software business growth

Zentitle meets the standards for scale, security and operational excellence demanded by enterprise-class software companies

From startup to $1Bn in ARR partnering with Nalpeiron

Partner for 8 years

From startup to VC funding to IPO for millions of users, all on Zentitle

Partner for 14 years

zentitle customer logoszentitle customer logos

What's in this video

In this video, we're gonna walk you through setting up some products and some business plans, creating some offerings, and then generating a couple of entitlements from those offerings.

So let's go.

So very often, our customers will have this kind of situation where they perhaps have good, better, best additions of a given product and Some features are included in some additions and not in others. And in this particular example, we're offering them either in subscription or perpetual licensed models with or without maintenance.

So how would we set that up within Zentitle2? Well, you can see we have a number of different attributes. So we've got sort of a standard set of features, and then we want to be able to enable this advanced simulation feature.

So the pro edition needs to have that feature switched on. And then for the enterprise edition, everything that is in standard and also include advanced simulations and batch mode and another feature so that the software can run on a virtual machine. And, of course, these are just examples.

So to set that up, you would go into Zentitle2.

Go to the products tab and create a new product.

So here, our product name is Elevate, Elevate Standard Pro Enterprise.

So we'll go and enter elevate.

And save that. So we've now created that product.

And I can set some defaults for that particular product. So licenses built from that product definition will inherit you know, this initial lease period, which is force a refresh once a day, the offline lease period, which is used for offline activations, and the concept of grace period and linger period. If you want more information on those concepts, check out the Zentitle2 documentation.

So now I've got that product. I want to add some specific features.

Now I've inherited a couple of global features that I've set up separately. So under my global settings, I've got a couple of fields like maintenance end date, and customer location that will be inherited by every single product I create. So here, you're seeing that in the elevate features.

But now I want to add some specific features for this product. So The first one that we wanted to add was this, advanced simulation.

And so we need to be able to, within the license, be able to switch that feature on or off for a given customer. So we'll initially set the value to false.

And so now I have that advanced simulation feature. So these features are straight bullion on off features that you can then enable or disable for a given customer's license.

Now we also want to add a feature for this batch mode.

So we're gonna create another feature called batch mode that will also default to false.

So now we've got our batch mode feature. And then there was another feature that we need to define, which is, virtual machine Okay.

So this is a flag to the application.

This fictional Elevate software application that would enable that application to run appropriately within a virtualized environments. So, of course, these are just examples.

So now I've got my three bullion features on the elevate product definition. Got some attributes that we've inherited from the global settings. That's the g for global.

And we can also add some advanced features things like element pools, consumption tokens, floating features.

And so I won't go into that right now. But consult the documentation if you wanna understand how those features work.

Alright. So now I have my basic features.

I can set up my additions.

So additions are how you name sort of the standard patterns for good, better, best. So in this case, standard professional and enterprise.

So I'm gonna create a standard edition.

And I'm gonna create a professional edition.

And I'll create my enterprise edition.

So now I have my three editions.

And so these will now be set to hold the values of whether those features should be enabled or disabled for users of that particular edition.

So for the standard edition, none of the additional features are switched on. So they'll just get the base functionality. So I'll leave all of these as they are disabled.

And so when I generate a license for this elevate standard edition, these will all default to off.

Now when I look at my pro edition, I'm going to set that advanced simulation flag to be true because we're enabling advanced simulations, whatever that is within that professional edition, but that's the only change. Right? Cause that is the only additional feature for the pro tier. And then for the enterprise, it's the advanced simulations, batch mode, and that virtual machine okay flag. So I'm gonna go back here and look at my profession or, enterprise edition, and here I'm going to switch all of these on.

Alright. So now I have my three additions, and my good, better, best? And now I can start looking at the business model side of things. So what kind of license model do I want to be able to sell these licenses against? So here we've got set up a number of different sort of canned business plans, but you can set, those up yourself. So here, for example, is a six month subscription that is simply a license type of subscription, it gets activated upon the first use, and then it's a duration of six months.

So here, I wanna be able to sell in either perpetual license model, which is, of course, license type perpetual, and the license starts when, again, upon first activation.

So I've got my perpetual license model, and I've got my one year subscription model. So those are the two business models that I want to be able to use.

Now once I've done that, I can define offerings. So an offering is a combination of a products edition and a business plan and a seat count. So let's create some to represent, say, these six different permutations.

So we've got three in the subscription based model, and then another three in the perpetual license model. So to do that, I'm going to create an offering And so it is for that elevate product.

And so I'll say elevate standard.

One year subscription.

One seat.

And, of course, the name can be whatever you choose. So here, by convention, I'll put in a SKU, and, of course, this might come from some other system, SAP Oracle, force or what have you. So I'll say, zero zero one dash, one year. Is my SKU. And so that is the standard edition with the one year subscription.

And a C count of one, and it's going to be a node lock individual license.

So I will save that out then as a new offering.

And now, of course, I can create, another one, similarly for elevate.

Elevate, standard, perpetual, license one sequel.

And again, zero zero one dash herb.

So that is the standard edition again against a perpetual license model with a C count of one and also a note lock license.

So now I've got a couple of different offerings.

So now when I want to be able to fulfill a license against one of these offerings. So when a customer wants to buy one of these licenses, I can click into that offering and create that entitlement. And, of course, all of this can be done programmatically as well. So I've got my elevate product. I've got my perpetual license.

I'm going to create a brand new customer So we'll create ACME widget Corp.

And so that entitlement will now be associated with ACME widget Corp, and maybe I'm gonna fill in some sort of reference ID from Salesforce or what have you. And again, that could be done programmatically.

Alright. So now I have my individual entitlement and you'll see that it will also automatically generate an activation code. So these activation codes, you can have many as you wish, they're all synonyms for one another. And so if you're doing a license that gets activated by a license key in activation code, you can provide that. And so this could be sent out as part of an automated email in the entitlement, is created and and sent out to the customer.

And if you want to, you can change the activation code associated with this entitlement. You can add another one we're just gonna add one more activation code. So now either of these two activation codes can be used, to activate a seat against this entitlement, and, of course, you can delete, old ones as well. So you can add as many as you like.

And that's really all there is to setting up plans, products, additions, offerings, and entitlements.

Hope that helps you get started quickly, and let us know if you have any questions.