How a sale happens

Before a Content Seller can sell a Content Owner's product, several things have to line up. If you have ever asked "why can't I sell this?" — start with the four commercial readiness checks below, then confirm the product lifecycle and fulfillment availability are live.

Content Owners deciding what to make available, and Content Sellers wondering why a product is not showing up as sellable.

• Sellability starts with four commercial readiness checks, in order: Agreement → Share → Allocation → Price.
• Those four are necessary but not sufficient. The product must also be in a sellable lifecycle state, and fulfillment availability must be there when the sale happens. Passing them still does not mean every country — Where a sale is allowed is the country check.
• Agreement means the partner Master Collaboration Agreement (MCA) plus the applicable Business Model Agreement (BMA). Share is the catalog scope set by that BMA. Allocation is sellable capacity under that Agreement — consumed at API Revenue Share checkout, or when wholesale and Traditional Revenue Share keys are pulled into held Stock. Optional Dedicated stock earmarks concrete keys within an applicable partner allocation across commercial models. Price for API Revenue Share sales is territory catalog pricing; wholesale and Traditional Revenue Share pricing follow the applicable Agreement and allocation terms.
• Fulfillment follows the business model: API Revenue Share at checkout (including keyless hosted redemption), or held Stock where keys move to the seller before retail sale.
• Money moves in three related steps: the buyer pays the Content Seller at retail, the Content Seller settles with the Content Owner under the applicable model, and Avrix commission is handled separately on the Content Owner side.

Every partnership starts with two kinds of Agreement, both signed per partner:

• The Master Collaboration Agreement (MCA) is the overall partnership framework — the baseline terms for working together.
• A Business Model Agreement (BMA) covers how you trade under a specific model (for example API Revenue Share, wholesale, Traditional Revenue Share, or Buy-In Wholesale), including which SKUs are in scope and the commercial rules for that model.

You need an active MCA and the BMA that matches how you intend to sell. The four commercial readiness checks below assume both are in place for that partnership.

1. Agreement. The Content Owner and Content Seller have signed the MCA and the BMA that applies to how they are trading. Nothing sellable happens until both are active for that partnership.
2. Share. The BMA defines which SKUs are in scope — the catalog the Content Seller is allowed to see and sell under that Agreement. An active Agreement alone does not put products in front of the Content Seller; the BMA catalog scope does.
3. Allocation. The Content Owner allocates sellable capacity under the partnership. For API Revenue Share sales, that capacity is used at checkout when the storefront fulfills the order. For wholesale and Traditional Revenue Share, capacity is used when keys are pulled into the seller's held Stock — before any retail sale. Optionally, Dedicated stock earmarks specific keys for that partner within the applicable allocation; it works across commercial models and does not increase the allocation itself. BMA scope without allocation means the Content Seller can see the product but cannot sell it.
4. Price. What counts as a valid price depends on the business model:
   • API Revenue Share sales: territory catalog pricing on the SKU — a valid price for the buyer's country or region must be set before preview or fulfillment.
   • Wholesale and Traditional Revenue Share: pricing follows the applicable Agreement and allocation terms — not the same territory catalog-pricing gate used for API Revenue Share sellability.

A product can look fine in the catalog and still fail one of these checks silently. If a Content Seller cannot sell something they expect to, walk this list top to bottom before assuming something is broken.

Passing Agreement, Share, Allocation, and Price still does not mean the buyer’s country is allowed. Where a sale is allowed explains the grant, the selling footprint, the title region, and the locks that only narrow.

Passing all four commercial readiness checks still does not guarantee a sale.

• Product lifecycle. The SKU must be in a live, sellable lifecycle state — for example available and open for trading, not archived or held back for pre-order before its release window. A pre-order SKU may be visible but not yet sellable.
• Fulfillment availability. For API Revenue Share key-based sales, remaining allocation capacity and available keys — from Dedicated stock or the shared pool — must be there at checkout. For API Revenue Share keyless sales, fulfillment depends on provider readiness, not key inventory. For held Stock, keys must already be in the seller's possession before retail sale. A SKU can pass every check and still fail if capacity, keys, or provider readiness are not there when needed.

How a buyer receives the product depends on the business model:

• API Revenue Share at checkout. The storefront requests fulfillment when a customer buys. For key-based products, keys stay with the Content Owner until that moment; checkout needs both remaining allocation capacity and available keys (Dedicated or shared). The seller's Allocations show capacity, not keys in Stock. For keyless hosted redemption, the buyer receives a redemption link — fulfillment follows provider readiness, not key inventory, and no key moves into the seller's possession.
• Held Stock. For wholesale, Traditional Revenue Share, or complimentary flows, keys move into the seller's Stock before retail sale. The seller sells from what they already hold; Avrix does not transfer those keys again at checkout.

Your role-specific inventory guide explains which path applies to each partnership.

All four commercial readiness checks pass for the SKU and buyer context, the product lifecycle is live, and fulfillment availability is there when you need it — allocation capacity plus available keys for API Revenue Share key-based sales, provider readiness for API Revenue Share keyless sales, or keys already in Stock before retail sale. On the Content Owner side, that means an active MCA and BMA, BMA catalog scope applied, capacity allocated (with Dedicated stock if you use it), and the correct pricing for the model. On the Content Seller side, confirm the same checks from your partner view and choose the right fulfillment path before you list or fulfill.

Three related flows — they do not mix:

1. Retail sale. The buyer pays the Content Seller through the Content Seller's own storefront and payment provider. Avrix is not part of this and never holds this money.
2. Partner settlement. Separately, the Content Seller settles with the Content Owner under the applicable model — for example paying a wholesale invoice for keys sold, or submitting Traditional Revenue Share reports and settling the agreed share. Not every model uses a per-key wholesale rate.
3. Platform commission. Avrix's commission is handled on the Content Owner side — it is not a separate charge the Content Seller pays directly to Avrix on top of partner settlement.

Reports, invoices, and running balances in the console's finance features track partner settlement on the seller side and receivables on the owner side, on a schedule set by the commercial Agreement — not necessarily on each individual sale. When Wallet is enabled, Embedded Wallets & Airwallex explains how those invoice funds actually move.

"The product is in my catalog but I can't sell it." Walk the four commercial readiness checks in order, then confirm lifecycle and fulfillment availability — most often it is allocation (no capacity allocated yet), price (missing territory catalog pricing for API Revenue Share, or incomplete Agreement terms for other models), exhausted API Revenue Share capacity, missing keys for key-based API Revenue Share sales, or empty Stock for held-stock models.

"The SKU is priced and allocated, but France was refused." The country check failed. See Where a sale is allowed — the country may be outside the title region, the Agreement grant, or the Content Seller’s selling footprint, or a lock may have removed it.

"We signed the Agreement — why can't they sell it yet?" Signing the MCA and BMA is only the first check. The Content Seller also needs BMA catalog scope, allocated capacity, the correct pricing for the model, a live product lifecycle, and either checkout capacity plus keys (for API Revenue Share key-based sales), provider readiness (for API Revenue Share keyless sales), or keys already in Stock.

"I shared the product — why can't they sell it yet?" BMA catalog scope only makes the SKU visible under that Agreement. The Content Seller also needs allocated capacity, pricing, lifecycle, and fulfillment availability.

"We dedicated stock — why is there still an allocation limit?" Dedicated stock earmarks keys within the applicable partner allocation. It helps a partner draw from a specific pool but does not increase the allocation itself.

"Who do I ask if I think a check is wrong?" Content Owners manage Agreement, share, and allocation from their side of Network and Catalog. Content Sellers can see their own allocations and pricing but cannot allocate themselves capacity — that request goes to the Content Owner.

• Where a sale is allowed — which countries a sale may happen in
• Content Owner: Partners & allocations — how to agree terms, apply BMA scope, and allocate capacity
• Content Seller: Find content to sell — how to request a connection and check what is actually sellable
• Embedded Wallets & Airwallex — how invoice funds, commission, and withdrawals move
• Your team — set up your company before any of this