Content Owner partners & allocations

Turn a partner connection into controlled selling readiness by completing the Agreement, Share, Allocation, and applicable Price checks in the right places.

Content Owners connecting with a new Content Seller, or allocating more capacity to an existing one.

• Use Settings → Gatekeeper to define pre-connection eligibility when you need it.
• Complete the partner MCA and applicable BMA at Network → Partners → partner → Agreements.
• The BMA's catalog scope is the commercial Share. Products → Key Sharing is only for complimentary, non-retail keys.
• Set a finite allocated quantity in Products → Allocate. Optional Dedicated stock earmarks keys within that quantity; it does not add capacity.

Settings → Gatekeeper defines the criteria and acknowledgements a prospective Content Seller must satisfy before requesting a connection. Use it to express eligibility requirements at the start of the relationship.

Gatekeeper does not pause a catalog Share or allocation after a partner Agreement is active. Partner terms and selling readiness are managed in the later steps below.

1. Open Network → Seller Network to review available Content Sellers, or handle an incoming request.
2. Complete the connection process.
3. Open the connected company from Network → Partners.

Connection status only confirms that the companies are connected. Commercial selling still requires the partner Agreements.

From Network → Partners → partner → Agreements, complete:

• the Master Collaboration Agreement (MCA), which sets the overall framework for working together; and
• the applicable Business Model Agreement (BMA), which sets the model-specific commercial terms and product or SKU scope.

The MCA and BMA must reach the required signed, active state before allocation can be saved for that model.

The partner page also shows that Content Seller's selling footprint against the territory the live Agreement grants. The overlap is where a sale can actually happen. If this partner must not use a granted country, Manage restrictions locks it for every title under that Agreement. Where a sale is allowed explains the country check and when to lock a title instead.

Settings → Distribution models activates business models for your company and records the related platform agreement. Activate a model there before offering it to a partner. Do not use that company-level page as a substitute for the partner MCA or BMA.

The active BMA defines which products or SKUs are in scope for that Content Seller under that business model. This scope is the Share check: it determines the catalog the partner may see and sell commercially.

Review or expand BMA scope from the partner's Agreements area. An MCA without an applicable BMA scope does not commercially share the SKU.

1. Go to Products → Allocate.
2. Choose the connected Content Seller and business model.
3. Select SKUs covered by the active BMA.
4. Set a finite allocated quantity for each SKU and save the allocation.

The allocated quantity is the maximum capacity available under that partner, SKU, and model. As keys are pulled, reserved, or fulfilled, the remaining amount falls. Raising the allocated quantity requires an explicit allocation update; adding more inventory alone does not raise it.

For key-based SKUs, Dedicated stock can earmark specific keys for a partner within an applicable allocation. Commercial fulfillment can prefer those keys before the shared available pool.

Dedicated stock is not extra capacity. If the allocated quantity is 50, dedicating 100 keys does not let the partner use 100; the finite allocation still governs how much can be fulfilled.

Keyless fulfillment has no physical keys to dedicate. Its readiness depends on the allocation and provider path.

For API Revenue Share sales, confirm territory catalog pricing for the buyer's country or region in the product's pricing setup under Products → Catalog. Catalog pricing explains the SKU → region → platform-default resolution order. A SKU can have an Agreement, Share, and Allocation but still fail preview or fulfillment where no valid territory price exists.

Wholesale and Traditional Revenue Share pricing follows the applicable BMA and allocation terms rather than the API Revenue Share territory catalog-pricing gate. Review the terms for the model you are using instead of assuming one pricing rule applies to every partnership.

The partner is connected, the MCA and applicable BMA are active, the intended SKUs are in BMA scope, each SKU has a finite allocation, and the model's pricing requirement is satisfied. Key-based API Revenue Share fulfillment also needs available keys; keyless fulfillment needs provider readiness.

"The Content Seller is connected but cannot see the SKU." Check the active BMA's catalog scope. Do not try to solve a commercial scope gap through complimentary Key Sharing.

"The SKU is visible but cannot be fulfilled." Check allocation remaining, product lifecycle, and fulfillment availability. For API Revenue Share sales, also check territory catalog pricing.

"We imported or dedicated more keys, but capacity did not rise." Inventory and Dedicated stock do not increase the allocated quantity. Update the allocation deliberately.

"A prospective Content Seller cannot request a connection." Review Settings → Gatekeeper for unmet pre-connection eligibility requirements.

• Where a sale is allowed — grant, footprint, and locks
• Availability & readiness — verify lifecycle, visibility, fulfillment, and capacity
• Getting paid — what happens financially once sales start
• Promotions — running joint promotions with your Content Sellers