Sell digital products with confidence

Digital products should be delivered as smoothly as physical orders: the buyer pays, receives exactly what they purchased, and can use it without waiting for manual work. Kiero OMS brings that workflow into one place — whether you sell a browser extension, desktop software, a mobile app, a course, a downloadable file or access to a digital service.

Two ready-to-use delivery paths

1. Generated license key

Use this path when your product needs activation or entitlement checks. Kiero creates a unique key after the order is confirmed as paid, stores it securely, and links it to the product, plan, price and order.

Your application verifies the key online through the public API and can activate or deactivate a specific installation. The response includes the product, plan, immutable profile version, expiry date, device limit and product-defined features. This means a monthly and annual price can use different license rules without creating duplicate product cards.

Key profiles support four implemented generators: base32, groups, base62 and uuid_like. Changes to a validity period, generator or device limit are made as a new profile version, so already-issued licenses remain unchanged.

2. Secure download

Use this path for ZIP archives, installers, templates, manuals, media or any other private file. Upload the file from the product card; Kiero stores it in a private R2 bucket and never exposes the storage URL.

After payment, the buyer receives a protected download link. The link has an expiry time and a maximum number of downloads. Each use is counted atomically, and the final file URL is short-lived. A revoked grant, expired token or exhausted quota simply stops working.

Where can you sell?

Stripe is the most direct route: Kiero imports Stripe Products and Prices, lets you connect each price to a product and license version, and processes the paid order through the same OMS fulfillment queue.

Kiero Store gives you a complete branded storefront. Publish the selected OMS catalog, configure checkout and payments in the Store, and send the paid order back to Kiero OMS. The Store handles presentation and checkout; OMS remains the source of truth for the product, price, entitlement and operational history.

Other connected channels can also feed the common paid-order pipeline. The important requirement is a correct mapping to the local product variant and a confirmed paid state. For a manual cash or bank-transfer sale, create the order in OMS, mark it paid through the standard payment transition, and use a catalog item with its variant linked to the digital product.

A simple setup recipe

1. Create or import the product in Kiero OMS.
2. Open Digital product in the product card and choose the product category. The category is descriptive; delivery is controlled by the fulfillment method.
3. Choose Generated key, Secure download or None.
4. For a license, create an active profile version and connect each Stripe Price to the required version.
5. For a file, upload at least one active file and set the link lifetime and download limit.
6. Set the digital configuration to Active and save it.
7. Add an email automation if the buyer should receive the license or download link automatically.
8. Run one test payment and verify the complete order, email and API/download flow before publishing.

Clear contracts for developers

The developer receives a stable API contract, not a secret or a Stripe checkout identifier. The verification response identifies the paid product and plan and returns only the configured features. Download links are delivered through email placeholders such as [download_url], [download_expires_at] and [downloads_remaining].

The result is a clean division of responsibility: your product decides how to use its license features, while Kiero OMS handles payment confirmation, secure issuance, audit history and revocation. Future fulfillment modes are kept in the data model, but are not enabled until their complete execution workflow is implemented.