Zentitle Order Fulfillment

From an order all the way to the customer using your application

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

So let's look at how you would use Zentitle within a typical order fulfillment flow.

So here, you know, you as the vendor would have some existing order processing order entry kind of approach. Could be Salesforce, could be NetSuite, could be an e commerce based flow, automated through Stripe, Chargeify, and so forth. But ultimately, there's some way of taking an order the choice of addition, you know, subscription, perpetual, etcetera, from some product catalog.

So within the catalog, you can define For a given offering or a SKU, what are the operations should that that should be performed in terms of fulfilling an entitlement for that SKU? So for example, you may have some SKUs that generate a brand new entitlement. Right? So an initial subscription of whatever form. But you may also have other SKUs that act as modifiers against existing entitlements.

Classic example would be a renewal. Right? So you want to take an existing entitlement that already exists within the Zentitle Cloud and, expand the subscription expiration date by a year. Similarly, you may want to have SKUs that represent buying add ons of seats, upgrading from one addition to another, and so forth. So this catalog mechanism is very flexible in terms of defining to fulfill an order of a specific, entity, a specific SKU What are the operations that should be performed on that entitlement or set of entitlements within this end title cloud?

Now once that entitlement has been created, course, you can, on an automated basis, send out the credentials. So if you have sort of a ship to kind of field within that order, You can use that to define say an email address, generate an automated email with the credentials that should be used to activate seats, Could be, again, that license key based model could be an identity based approach and so forth. So the end user would then take those credentials and enter that into the application. Could be a SaaS application, could be an on prem application, and so forth.

And then once that set of credentials are entered. Your application through our SDKs, make a callback into this entire cloud using our licensing API to activate a seat against that license and away you go. So this whole path from order entry to order fulfillment providing credentials and then activating seat. You know, you can have an end to end experience for a given customer literally in a couple of minutes.