Content Owner catalog overview

Build the Product → Edition → Platform release → Region release → SKU hierarchy and follow the focused catalog guides.

Build one dependable catalog foundation, then use the four focused guides in this chapter to control presentation, pricing, classification, and release readiness.

Who needs this#

Content Owners adding a new product, or trying to understand why "the product" and "the sellable thing" aren't quite the same.

TL;DR#

  • The catalog hierarchy is Product → Edition → Platform release → Region release → SKU.
  • The SKU is the unit that receives fulfillment, partner scope, allocation, lifecycle, and applicable pricing.
  • Start with Products → Catalog → Create product, then add each level deliberately.
  • Structure alone does not make a SKU sellable. Lifecycle, partner scope, allocation, pricing, and fulfillment each answer a different readiness question.

The catalog structure#

  1. Product

    the game

  2. Edition

    Standard, Deluxe…

  3. Platform release

    Steam, console…

  4. Region release

    territory coverage

  5. SKU

    the sellable unit

  • Product. The title at its broadest level.
  • Edition. A version such as Standard, Deluxe, or a bundle.
  • Platform release. An edition published for a particular platform.
  • Region release. The territory coverage beneath that platform release.
  • SKU. The specific sellable unit beneath a region release, including its key or fulfillment type.

Most commercial checks happen at SKU level. A complete product page does not by itself make every edition, platform, or region sellable.

Build the hierarchy in order#

  1. Go to Products → Catalog.
  2. Select Create product and enter the product details.
  3. Add the editions you intend to offer.
  4. Add a platform release for each edition and platform combination.
  5. Add the relevant region releases beneath each platform release.
  6. Add the SKUs that partners will receive scope and capacity for.

Example: Northstar → Deluxe Edition → Steam → Europe → NORTHSTAR-DLX-STEAM-EU. That final SKU is where the fulfillment type and the most specific catalog price can be set. Its parent region supplies territory context; its platform release can supply default pricing and taxonomy.

Use the Catalog chapter#

Learn what each Product tab controls, then follow the hierarchy into Edition, Platform, and Region workspaces. Use this when you know the catalog exists but are unsure where a change belongs.

Set platform defaults, region behavior, country prices, and SKU overrides. Use this when a territory has no price or a lower-level value differs from its parent.

Classify content consistently with ratings and descriptors, genres, tags, and features. Use this when platform vocabulary needs to become one canonical catalog description.

Control launch phase and trading state, then diagnose the separate layers between catalog structure and a successful sale. Use this when a product is visible in one place but not sellable in another.

Know when the catalog foundation is ready#

A SKU is ready to take into a partner Agreement when:

  • it sits under the correct edition, platform release, and region release;
  • its lifecycle is appropriate for the intended launch;
  • its fulfillment method is clear;
  • territory catalog pricing is present where the business model requires it; and
  • key inventory or keyless provider readiness can support fulfillment.

The partner still needs Agreement, Share, and Allocation before the SKU becomes commercially sellable. The Product Distribution tab helps you inspect reach, but Partners & allocations remains the authority for MCA/BMA scope, partner access, capacity, and Dedicated stock.

Steam sync#

For Steam products, Products → Steam-sync can import public Steam Store listing data and mapped taxonomy into the catalog. This is optional; it does not replace the region release, SKU, inventory, partner Agreement, allocation, or pricing checks required in Avrix.

Sync one release or many. The page lists every Steam release with its Steam App ID, its last sync and its status. Tick the releases you want and choose Continue. A release without a Steam App ID cannot be ticked until you add one with Add Steam ID; Edit Steam IDs on a row changes the App ID or the package ID and can verify the App ID against Steam.

Choose what to sync. Continue opens What to sync: product name, descriptions and their languages, developer and publisher, genres, tags and features, release date, regional prices, cover, screenshots, key art and store banner. Start sync reads Steam in the background, and the row's status shows the progress. Nothing is saved yet.

Review before saving. A finished sync waits under Recent syncs and in the row's status with a Review button. The review lists every change next to what you have now. Untick what you do not want, then save. A review you do not save expires after a day.

Import games from Steam. The Import from Steam button on that page opens one search bar. Type a game title or a publisher or developer name to see both the matching games and everything by that publisher; paste a Steam publisher or developer page link, a game store link or App IDs to find those apps; or use Add from my Steamworks key. Add the apps you want to the To import list, search again as often as you like, then choose Next: What to sync opens, and Import starts the import. A search for a publisher or developer shows their card in purple; open it to see everything they publish. Each app opens a review under Recent syncs with what Steam has. Saving the review adds the game to your catalog, with its Steam release and App ID, private and in draft; discarding it adds nothing. Apps already in your catalog or waiting for review cannot be added twice, and DLC is linked to its base game when that is in your catalog. The review also lists Steam's price for every Worldwide country Steam sells the game in, all ticked. Saving creates the game's Worldwide region and writes the prices you kept, in the currency Steam charges there (or your fallback price where you excluded that currency). Untick Regional prices from Steam in What to sync to import without prices. Create product also has an Import from Steam button on its first step that opens this importer.

Steam prices for every release at once. Regional pricing from Steam imports the regular (pre-discount) Steam storefront price of every Steam release with an App ID in one background run, in your catalog currency. Countries where Steam does not sell the product are skipped rather than priced at zero, and a country whose Steam currency differs from your catalog currency is reported instead of written. Prices you entered by hand are never overwritten.

When creating a product, entering the Steam App ID on the platforms step syncs the product from Steam right after creation.

When enabled for your company, Analytics → Steam sales provides Steam sales reconciliation for linked products.

You are ready when…#

Every planned SKU belongs to the intended product, edition, platform release, and region release; the team knows which workspace owns each change; and every sellable SKU has a lifecycle, fulfillment method, and applicable price.

Common problems#

"I added the product but no Content Seller can see it." Check Availability & readiness first. A Draft or archived item is not partner-visible. Then check BMA catalog scope; commercial visibility does not come from complimentary Products → Key Sharing.

"I have the right edition but the wrong platform or territory." Check both the platform release and its region release. They are separate levels.

"A country has the wrong price." Follow the resolution path in Pricing: SKU first, then region, then platform default.

"Steam terminology does not match our other platforms." Review Taxonomy & AUM to see how platform terms map to the canonical Avrix vocabulary.

Next steps#

What links here

Published guides that link to this page.

Search docs

Search documentation…