Content Seller inventory & selling

Choose the fulfilment path that matches your Agreement, confirm what is ready to sell, and keep customer adjustments separate from key-return requests.

Content Sellers making their first sale, or reconciling what they've sold against what they were given.

• Inventory → Partner catalog shows the products in your commercial Share.
• Inventory → Allocations shows capacity. For API Revenue Share checkout, the storefront uses that capacity when a customer buys; keys do not move into Stock first.
• Inventory → Stock contains wholesale and Traditional Revenue Share retail keys already in your company's possession.
• Inventory → Complimentary manages approved non-revenue grants and pulls. Pulled keys are then held in Stock with a Complimentary classification, never as retail sellable stock.
• Inventory → Refunds records buyer refund and chargeback adjustments reported by your storefront integration.
• Inventory → Returns is a separate request workflow for eligible API and Traditional Revenue Share keys, when enabled for your company.

Customer checkout (API Revenue Share) — fulfilled on demand at the moment of sale:

Held Stock and Complimentary — keys must already be in your possession before they are sold or used:

API Revenue Share checkout fulfils on demand. A key-based order needs both allocation capacity and an available key from Dedicated stock or shared inventory; keyless fulfilment depends on provider readiness. Wholesale and Traditional Revenue Share keys must already be in retail held Stock before sale. Inventory → Complimentary manages its own grants and pulls; pulled keys appear in held Stock with their Complimentary classification and remain restricted to approved non-retail use.

For API Revenue Share checkout, confirm:

1. Agreement: the partner MCA and API Revenue Share BMA are active.
2. Share: the SKU is in the API Revenue Share BMA's catalog scope and appears in Inventory → Partner catalog.
3. Allocation: usable API Revenue Share capacity appears in Inventory → Allocations.
4. Price: territory catalog pricing is valid for the buyer context.
5. Lifecycle and fulfilment: the product is live, and keys or the keyless provider path are available.

For wholesale or Traditional Revenue Share selling, confirm the matching BMA and its commercial terms, then confirm the retail keys are already in Inventory → Stock before sale.

The Seller API is the standard fulfilment path for storefront checkout:

1. Your storefront checks whether the requested SKU can be fulfilled for the customer.
2. Your storefront takes payment through its own payment provider.
3. Your storefront creates the order, which uses API Revenue Share allocation capacity and returns the entitlement for delivery.

For key-based API Revenue Share sales, the key remains with the Content Owner until checkout. It does not move into Inventory → Stock first. Inventory → Allocations is the relevant console view for capacity; available owner inventory is also required at fulfilment time.

For keyless API Revenue Share sales, no plaintext key changes hands. When keyless fulfilment is enabled for your company and the Content Owner's provider path is ready, the customer receives a hosted redemption experience. Inventory → Keyless orders then shows issued fulfilments and the available management actions. If that screen is absent, do not assume keyless is available for the partnership.

Your technical team should use Automate with the API as the handoff to the developer documentation.

Wholesale and Traditional Revenue Share keys move into your possession before retail sale:

1. Open Inventory → Stock and confirm the expected wholesale or Traditional Revenue Share keys are available to pull.
2. Pull the eligible keys into your held Stock according to the Agreement.
3. Sell those keys from the stock your company already holds. Avrix does not fulfil the same key again at your customer's checkout.

When enabled for your company, Inventory → Complimentary is the dedicated flow for approved review, press, promotional, beta, or developer use. Manage the grant and pull from that screen. After pulling, the keys are held in Stock with their Complimentary classification so custody remains visible. They stay approved for non-retail use only, must never be presented as retail sellable stock, and must not be sold.

Use Inventory → Exports when you have permission to export eligible held keys. An export is a custody operation, not proof that a SKU is commercially ready for API Revenue Share checkout.

Use this path when your buyer has been refunded or a chargeback affects a storefront order:

1. Refund the buyer or handle the chargeback through your own payment provider.
2. Have your integration report the adjustment to Avrix.
3. Review the resulting record under Inventory → Refunds and reconcile any credit through the next applicable statement or report.

Reporting an adjustment keeps the partner commercial record aligned. Avrix does not issue the retail refund for you. This is one adjustment path; it does not normally lead to a separate Return request.

Inventory → Returns is an alternative partner workflow, available only when enabled for your company. Use it to request that eligible API Revenue Share or Traditional Revenue Share keys be returned to the Content Owner — for example an invalid, already-redeemed, wrong-product, region-locked, or otherwise eligible key.

A return request may require evidence and Content Owner review. Wholesale, Buy-In Wholesale, and complimentary keys are not supported by the current Returns workflow. Eligibility also depends on the key, reason, and return window.

Choose the workflow that matches the outcome: report a buyer refund or chargeback under Refunds, or file an eligible key-return request under Returns. Do not treat them as two normal steps in one process.

For API Revenue Share checkout, the API Revenue Share BMA is active, the SKU is in its Share, API Revenue Share allocation and territory Price are available, the product is live, fulfilment is available, and your storefront can preview and create an order. For wholesale or Traditional Revenue Share selling, the applicable retail keys are already visible in Inventory → Stock and your team knows the BMA rules. Any Complimentary keys held in Stock remain visibly classified for non-retail use and are excluded from retail selling.

Example: An API SKU with capacity 100 remains in Allocations as customers buy; each checkout uses capacity and fulfils on demand. A wholesale batch of 100 moves into Stock first, and your storefront then sells from that held batch.

"My API Revenue Share allocation is available, but Stock is empty." That is expected. API Revenue Share checkout uses allocation on demand; API Revenue Share keys do not move into held Stock first.

"I expected wholesale or Traditional Revenue Share keys, but Stock is empty." Open Inventory → Stock and confirm that eligible keys are available to pull under the applicable BMA before retail sale.

"I refunded my customer. Should I also file a Return?" Not as a normal next step. Report the buyer adjustment through your integration. Use Returns instead when you are filing an eligible API or Traditional Revenue Share key-return request for Content Owner review.

"Preview failed for a country I expected to sell in." Check your selling footprint and that partner's locks before assuming stock is the cause. Where a sale is allowed names the three usual reasons: you have not declared the country, the Agreement does not grant it, or the Content Owner locked it.

• Where a sale is allowed — why a country can fail when stock looks fine
• Money & reports — how sales show up financially
• Automate with the API — connect storefront checkout to fulfilment