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.
Export keys#
Export keys when you need them outside Avrix, for example to hand them to a distributor. Open a batch and select Export, or select Export inventory above the batch list to export from every active batch. Archived batches are only exported when you open them directly.
In the Export keys popup, choose:
- Keys: which status to export, such as available, blocked, or quarantined keys.
- How many: leave it empty to export every matching key. One export holds at most 50,000 keys; Avrix refuses a larger export rather than cutting the file short.
- After the download, for available keys:
- Take out of stock (the default): the keys get the status Exported and stop being sold. Use this whenever the keys will be used outside Avrix.
- Keep in stock: the keys stay on sale. A key sold after the download could then be used twice, so use this only for a backup or an audit copy.
- File type: Text (one key per line) or CSV (a Key column; blocked and quarantined exports add the batch and, for quarantined keys, the dispute status).
Before you export, the popup shows how many keys match and how many will be taken out of stock.
Keys promised to Content Sellers stay in stock. Taking keys out of stock never uses Dedicated stock, and never takes the shared stock that Content Sellers' allocations still need. Those keys stay on sale, and the popup and the confirmation tell you how many stayed behind.
Only members who can change keys can take them out of stock. Members who can only export keys get a copy, and the keys stay on sale.
Blocked, expired, revoked, and quarantined keys can't be sold, so exporting them never changes their status. On the blocked and quarantined views, the export follows the filters and search you have applied, or only the keys you select.
The Exports tab#
Products → Inventory → Exports lists every export: when it ran, whether the keys were taken out of stock, where it came from (a download, a scheduled job, or a batch removal), how many keys it held, and how many have been returned. Every export records exactly which keys were in the file, so you can always answer which export a key left in.
From the row menu you can:
- Download again: get the same keys as the original file. Keys deleted since then are left out, and the confirmation says how many.
- Return to stock: put the keys of a Taken out of stock export back on sale. Only keys that are still exported come back; keys that were deleted or changed since are skipped. Anyone who has the file could still use the returned keys, so only do this when the file was never used.
- Cancel export: for an export that stopped before the file was delivered (In progress). Keys it took out of stock go back on sale.
When keys are taken out of stock, returned, or removed, the available stock your Content Sellers see updates to match.
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.
"I exported 100 keys, but only 80 were taken out of stock." The other 20 are promised to Content Sellers through Dedicated stock or their allocations, so they stayed on sale. Lower an allocation or remove Dedicated stock first if you need those keys.
"I exported keys by mistake." Open the Exports tab and select Return to stock on that export, as long as nobody has used the file.
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