Follow this journey to move from a verified company to a product that a Content Seller can discover, agree to sell, and fulfill under clear commercial controls.
Who needs this#
A Content Owner, such as a studio or rights-holding company, new to the console.
TL;DR#
Work in this order: company readiness → regions and commercial models → catalog → fulfillment → partner connection → partner Agreements → commercial Share → Allocation → Price → finance. Each step prepares the next one.
Before you start#
Read What is Avrix? and How a sale happens first. The second guide explains the four commercial readiness checks: Agreement → Share → Allocation → Price.
Your route to readiness#
After company setup, catalog, fulfillment, and partnership work can progress in parallel. Readiness comes only when all three meet for the intended SKU and Content Seller.
Three tracks run in parallel once the company is ready:
The readiness gate joins the tracks:
The sections below explain what completes each stream. The final check remains partner- and SKU-specific; progress in one stream does not replace missing work in another.
1. Make the company partner-ready#
Complete the items in Company setup: company details, verification, public profile, platform agreements, publishing regions, and payout capability when it is enabled for your company. Invite the right colleagues and assign sensible access from Your team.
Then activate each commercial model you intend to offer from Settings → Commercial Agreements. This company-level step enables models such as API Revenue Share, wholesale, or Traditional Revenue Share; it does not create an Agreement with a particular Content Seller.
2. Build the catalog foundation#
Use Your catalog to create the full hierarchy: product → edition → platform release → region release → SKU. Then use the Catalog chapter's Product workspace, Pricing, Taxonomy & AUM, and Availability & readiness guides to prepare the hierarchy for launch. A SKU is the unit that receives fulfillment, partner scope, allocation, and pricing.
3. Choose how fulfillment works#
Use Inventory to Import keys for key-based SKUs. For a keyless SKU, confirm its provider and hosted-redemption setup instead; keyless fulfillment does not use a batch of codes.
4. Establish the partnership#
Use Partners & allocations to:
- find or accept a Content Seller connection;
- complete the partner Master Collaboration Agreement (MCA) and applicable Business Model Agreement (BMA) at Network → Partners → partner → Agreements;
- confirm the BMA's commercial Share, which defines the catalog scope for that model;
- set a finite allocated quantity and, if useful, earmark keys as Dedicated stock; and
- confirm territory catalog pricing where the model requires it; and
- confirm which countries that partner may sell into — Where a sale is allowed.
Products → Key Sharing is a separate optional flow for complimentary, non-retail keys. It is not how you commercially share a catalog with a partner.
5. Prepare finance and promotions#
Read Getting paid before activity starts so your team knows which reports apply to API Revenue Share, wholesale, and Traditional Revenue Share business. Use Promotions when you are ready to coordinate an offer without changing the underlying Agreement, allocation, or fulfillment readiness.
You are ready when…#
Your company is verified, its regions and intended commercial models are active, each sellable SKU has a region and fulfillment method, and the chosen partner passes Agreement, Share, Allocation, and applicable Price checks. Key-based API Revenue Share sales also need available keys; keyless sales need provider readiness.
Common problems#
"The product exists but the partner cannot sell it." Check the SKU, not only the product. Walk Agreement, Share, Allocation, and applicable Price in order, then confirm its lifecycle and fulfillment availability.
"We activated a model, but there is no partner Agreement." Settings → Commercial Agreements activates the model for your company. Complete partner-specific MCA and BMA work from the partner's Agreements tab.