Prepare the fulfillment behind each SKU so an eligible partner order can deliver a key or a hosted redemption experience.
Who needs this#
Content Owners about to import keys for the first time, or troubleshooting a key that won't deliver.
TL;DR#
- For key-based fulfillment, use Products → Inventory → Import keys and attach the batch to the correct SKU.
- For keyless fulfillment, configure the SKU's provider path; there is no key batch to import or dedicate.
- Inventory availability and allocation capacity are separate controls. You need both for a key-based API sale.
Choose the fulfillment path#
Key-based fulfillment#
A key-based SKU delivers one code from your inventory. Keys remain in your inventory until the applicable flow moves or fulfills them:
- an API Revenue Share storefront order consumes allocation capacity and delivers a key at checkout; or
- a wholesale, Traditional Revenue Share, or complimentary flow moves keys into the Content Seller's held Stock before retail sale.
Keyless fulfillment#
A keyless SKU does not deliver a plaintext code. The configured provider fulfills the order, for example through a hosted redemption link. Readiness depends on the provider setup rather than key inventory, and Dedicated stock does not apply because there are no keys to earmark.
Import keys#
- Go to Products → Inventory.
- Select Import keys.
- Choose the key-based SKU.
- Paste the keys or upload a supported file.
- Review the count and confirm the import.
Keep the source file until the imported count and duplicate handling match your expectation. Imported keys create fulfillment stock; they do not by themselves give any Content Seller permission or capacity to sell.
Inventory, allocation, and Dedicated stock#
Keep these concepts separate:
- Inventory is the pool of keys you hold for a SKU.
- Allocation is the finite capacity a partner can use under a Business Model Agreement.
- Dedicated stock optionally earmarks specific keys for one partner within an applicable allocation.
Dedicated stock can make a particular pool available to that partner first, but it does not increase the allocated quantity. Shared available keys can support allocations that do not use Dedicated stock.
Quarantined keys#
A key can be quarantined after a reported refund, chargeback, or eligible return. It is removed from sellable circulation and retained for review. Open Products → Inventory and use the quarantined-keys view when you need to inspect or export affected keys.
Finding a specific key#
If you need to track down where a specific key went — which Content Seller pulled it, whether it was delivered — use Products → Key Finder and search for it directly, rather than paging through batches.
You are ready when…#
Every key-based SKU has a verified inventory count, every keyless SKU has a ready provider path, and your team understands that partner scope and capacity are completed separately in the Agreement and allocation workflow.
Common problems#
"I imported keys, but the partner still cannot sell." Importing creates stock only. Confirm the partner BMA scope, allocated quantity, applicable price, product lifecycle, and current availability. Availability & readiness separates these checks.
"We dedicated 100 keys, so why is the partner's allocated quantity still 50?" Dedicated stock earmarks keys; it does not raise the finite allocated quantity.
"A keyless SKU shows no inventory." That is expected. Check provider readiness rather than importing keys.
Not covered here#
This page covers fulfillment stock. Commercial catalog scope, capacity, and pricing are covered in Partners & allocations.
Next steps#
- Partners & allocations — turn imported stock into something a Content Seller can sell
- Availability & readiness — check lifecycle and fulfillment together