> For the complete documentation index, see [llms.txt](https://docs.nalpeiron.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nalpeiron.com/zentitle2-docs/use-cases/use-case-directory/order-fulfillment.md). # Order Fulfillment Follow a typical order fulfillment flow in Zentitle, from catalog-defined SKU operations through automated credential delivery and seat activation. ### A typical order fulfillment flow using Zentitle. {% embed url="" %} As a vendor, you would have an existing order processing and entry system in place. This could be Salesforce, NetSuite, or an e-commerce flow automated through Stripe, Chargify, or a similar platform. 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. {% hint style="success" %} Let's jump on a call and discuss how we can help, get in touch with your account manager today → [Setup a 1:1 discussion](https://www.nalpeiron.com/get-a-11-demo.html) {% endhint %} --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.nalpeiron.com/zentitle2-docs/use-cases/use-case-directory/order-fulfillment.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.