Content Owner catalog overview

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

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

• 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.

• 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.

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.

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.

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.

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.

Import a whole Steam catalogue. On the same page, Import from Steam finds the apps behind a Steam publisher or developer page URL, a publisher or developer name, a pasted list of App IDs, or your connected Steamworks key. Each selected app becomes a product with a Steam release, the App ID set and a Steam sync queued; apps already in your catalogue are marked and skipped, DLC and soundtracks are linked to their base game, and demos, videos and tools start unselected. Imported products start private and in draft.

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 catalogue 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 catalogue currency is reported instead of written. Turn on Refresh Steam prices daily to keep them current; prices you entered by hand are never overwritten by the daily refresh.

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.

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.

"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.

• Product workspace — learn every catalog workspace and tab
• Pricing — control territory and SKU catalog prices
• Taxonomy & AUM — keep classification consistent
• Availability & readiness — prepare releases for visibility and sale
• Inventory — add fulfillment behind key-based SKUs