Content Owner catalog pricing

Set one sensible platform default, vary it only where a territory or SKU needs different treatment, and keep the price a Content Seller presents separate from the commercial amount agreed between companies.

Content Owners preparing territory prices, correcting a missing country value, or investigating why a SKU differs from its platform default.

• Avrix resolves catalog pricing from the most specific level: SKU override → region release → platform release default.
• Platform tiers can update automatically and can have a scheduled tier change.
• A region can inherit, use a different tier, combine a tier with country overrides, or use fully manual country prices.
• Nintendo releases use manual per-currency pricing at Region level; tier inheritance is unavailable.
• Territory catalog or suggested retail price (SRP) pricing is not the same as the Agreement or allocation price between a Content Owner and Content Seller.

When Avrix needs the catalog price for a SKU in a country, it checks:

1. SKU override — the most specific value, when that SKU has its own pricing.
2. Region release — the territory rule and country grid beneath the platform release.
3. Platform release default — the tier inherited by regions that do not override it.

Catalog price resolution and partner commercial pricing are separate authorities. The first branch resolves a territory-facing catalog value where required; the second reads the amount or settlement model agreed between companies.

One branch never rewrites the other. A complete country grid cannot repair missing partner terms, and changing a partner amount does not create a missing territory price.

Example: a Steam platform release uses a 59.99 USD tier. Its Europe region inherits that tier, but Germany has a country override of 54.99 EUR. A Deluxe SKU in that region has its own 64.99 EUR override. The Deluxe SKU value wins for that SKU; the Germany region override still applies to other SKUs without their own value.

Open Products → Catalog → product → edition → platform → Pricing.

Choose the platform price tier that should apply to inheriting regions. You can also:

• enable automatic updates so future changes to that tier flow through;
• schedule a different tier to take effect later; or
• cancel a scheduled change before it takes effect.

The region summary shows which region releases inherit the platform tier and which use custom pricing. Review the overriding regions before changing a default used across several territories.

Open a region from the Platform Regions tab, then select Pricing.

Use the tier selected at Platform level. This keeps regions aligned and minimizes maintenance.

Choose another standard tier for this region while keeping tier-controlled country values.

Start from a tier, then change individual country values. Use this for a small number of territory exceptions.

Set every country price in the region by hand. Use this only when the standard tiers do not represent the intended grid.

Switching away from manual pricing can remove existing manual values. Review the confirmation and export the current grid first when you need a record.

The Region Pricing tab shows the countries included in that platform region and the effective values for them. Depending on the mode and platform, you can edit a country directly, select countries for a bulk price suggestion, and use the available CSV, export, and saved-template tools to handle larger grids. Review suggested values before applying them.

Use the grid to answer three questions:

• Is the country part of this platform region?
• Does it have an effective amount and currency?
• Is the value inherited, tier-based, or manually overridden?

Some console storefronts use a fixed country list. In those cases, edit the listed values rather than adding or removing countries.

Nintendo platform releases do not use platform tier inheritance. Set manual per-currency amounts at Region level for the fixed country list shown by Avrix.

This means an empty Nintendo Platform Pricing view is not a request to choose a platform tier. Open each relevant Region Pricing tab and complete its listed currencies.

Open the Region SKUs tab and use the pricing action for the specific SKU. A SKU-level value takes precedence over its region and platform defaults.

Keep common values at Platform or Region level. Use SKU pricing for a distinct package or edition whose catalog price genuinely differs within the same territory.

The same SKU pricing dialog can also lock countries on that title, or refuse a location mismatch. That card is not a price. Leave it empty unless this title must be tighter than the deal. Where a sale is allowed explains when the region and the Agreement are the default instead.

Catalog pricing describes the territory-facing price or suggested retail price used for catalog and applicable API sale checks. It answers: what price applies to this SKU in this country?

The partner Agreement and allocation describe the commercial terms between the Content Owner and Content Seller. They answer: what amount or settlement model applies between these companies?

• For applicable API Revenue Share models, territory catalog pricing is part of sale readiness.
• For wholesale or Traditional Revenue Share arrangements, the BMA and allocation terms carry the commercial price or settlement basis.

Changing an SRP does not rewrite a partner Agreement. Changing an Agreement or allocation price does not fill a missing country in the catalog grid.

Every territory you intend to support has an effective catalog price for each applicable SKU, intentional overrides are documented at the lowest necessary level, and partner commercial pricing has been confirmed separately.

"A country has no price." Confirm the country belongs to the Region, then follow the chain upward: SKU override, Region mode and grid, Platform tier. For Nintendo, go directly to the Region's manual currency list.

"Changing the platform tier did not change one region." That region is using a custom mode. Open its Pricing tab and decide whether to keep the override or return to inheritance.

"A single SKU is still different." Open its pricing action from the Region SKUs tab. A SKU override wins over both parent levels.

"The partner's commercial amount is wrong even though the country grid is correct." Review the partner BMA and allocation in Partners & allocations. Do not solve a commercial-term issue by changing SRP.

• Product workspace
• Availability & readiness
• Partners & allocations
• Where a sale is allowed — country permission is not a price