Order Fulfillment
Last updated
Was this helpful?
Last updated
Was this helpful?
As a vendor, you would have an existing order processing and entry system. This could be Salesforce, NetSuite, or an e-commerce flow automated through Stripe, Chargify, etc. Ultimately, there's a way to take an order—whether subscription, perpetual, etc.—from a product catalog.
Within the catalog, you can define what operations should be performed to fulfill an entitlement for a given offering or SKU. For example, you may have SKUs that generate brand-new entitlements for initial subscriptions. You may also have SKUs that modify existing entitlements—a classic example being a renewal that extends a subscription's expiration date by a year in the Zentitle cloud.
Similarly, you might have SKUs for adding seats or upgrading from one edition to another. This flexible catalog mechanism lets you define specific operations for fulfilling orders against entitlements in the Zentitle cloud.
Once an entitlement is created, you can automatically send out credentials. If you have a "ship to" field in the order, you can use that to specify an email address and generate an automated email with activation credentials. This could use a license key or identity-based approach. The end user then enters these credentials into the SaaS or on-premises application. Once entered, your application uses our SDKs to call the Zentitle Cloud licensing API, activating a seat against that license.
This streamlined path from order entry to fulfillment, credential delivery, and seat activation provides an end-to-end experience that takes just minutes for each customer.
Let's jump on a call and discuss how we can help, get in touch with your account manager today →