Content Owner taxonomy & AUM

Describe each title once in a consistent catalog vocabulary, then let editions and platforms inherit that foundation unless they genuinely differ.

Content Owners improving discovery, age-rating clarity, cross-platform consistency, or Steam-synced product data.

• Taxonomy covers ratings and descriptors, genres, tags, and features.
• Avrix Universal Mapping (AUM) provides the canonical vocabulary used across platform-specific labels.
• Inheritance flows Product → Edition → Platform release.
• Each taxonomy category can inherit or use its own values.
• Steam sync can map Steam Store genres and categories into AUM; Avrix administrators maintain the platform-to-AUM mapping, while Content Owners review and select the canonical result.

Open Products → Catalog → product → Taxonomy.

Choose the applicable rating for each supported rating system, then add the descriptors associated with that rating. Ratings communicate the age classification; descriptors explain the content behind it.

Use only ratings that apply to the product and verify territory requirements with your publishing team.

Genres are broad catalog categories such as action, strategy, or role-playing. Keep the selection focused enough to describe the product clearly.

Tags add more specific themes, modes, or characteristics. They help distinguish titles that share a genre.

Features describe supported capabilities, such as achievements or cloud functionality, when those capabilities are represented in the Avrix vocabulary.

Platforms often use different names for similar ideas. AUM is the canonical layer that connects those platform terms to one Avrix genre, tag, or feature vocabulary.

For example, a platform category describing Steam achievements can map to the canonical achievement feature. The catalog can then use that canonical result instead of carrying a different label for each platform.

AUM does not invent a match. Avrix administrators maintain the platform vocabularies and their mappings. Content Owners select and review the canonical values available in the Product, Edition, and Platform Taxonomy tabs.

Mapped platform labels enter the shared AUM vocabulary before Content Owners apply them. Ratings and descriptors join the Product taxonomy separately, then each category can inherit or differ farther down the catalog.

The decisions are category-specific. An Edition can override ratings while inheriting genres, and a Platform can override features while keeping the Edition's other values.

Taxonomy flows down the catalog hierarchy:

1. Product establishes the shared foundation.
2. Edition inherits from Product by default.
3. Platform release inherits from Edition by default.

Inheritance is category-specific. An Edition can inherit genres and tags while overriding ratings. A Platform release can inherit the Edition's genres but use platform-specific features.

When Inherit is enabled for a category, that level uses its parent's values and the category cannot be edited there. Turn inheritance off only when the child genuinely differs.

Suppose Northstar is an action-adventure game:

• Product taxonomy defines the core genre, exploration tags, and the relevant PEGI and ESRB ratings with descriptors.
• Deluxe Edition inherits genres, tags, and ratings because the playable content has the same classification.
• The Steam platform release inherits those categories but overrides Features to include the Steam capabilities that actually apply.
• A console platform release keeps the shared taxonomy and selects only the features supported on that platform.

This preserves one clear identity without claiming that every platform term or capability maps automatically.

Open Products → Steam-sync when you want to import supported public Steam Store data. When taxonomy sync is selected, Avrix resolves supported Steam genres and category descriptions through the configured Steam-to-AUM mappings.

After sync:

1. Open the Product Taxonomy tab.
2. Confirm that genres, tags, and features describe the title accurately.
3. Check Edition and Platform inheritance.
4. Add or correct ratings and descriptors as needed.

Steam sync assists catalog entry. It does not replace editorial review, age-rating authority, platform setup, pricing, or commercial readiness.

The Product has a clear canonical classification, every Edition and Platform category either intentionally inherits or intentionally differs, and ratings and descriptors match the content being offered.

"I cannot edit a category on an Edition or Platform." It is inheriting from its parent. Turn off Inherit for that category only if a child-specific value is required.

"Steam sync did not add an expected term." The Steam label may not have a configured AUM mapping. Choose the correct canonical value if available; mapping maintenance belongs to Avrix administrators.

"A platform shows a feature the product does not support there." Override the Features category at Platform level. Keep the other categories inherited if they remain correct.

"Ratings are present but descriptors are missing." Edit the rating entry and select the applicable descriptors for that rating system.

• Product workspace
• Availability & readiness
• Catalog overview