Content Owner product workspace

Use the catalog workspaces to put each decision at the right level: product identity at the top, platform and territory settings below it, and fulfillment details at SKU level.

Content Owners maintaining a product after creation, especially when the same title has several editions, platforms, or regions.

• A Product page has eight tabs in this order: Overview, Availability, Distribution, Descriptions, Taxonomy, Media, SKUs, Activity.
• Edition pages have Platforms & regions, Descriptions, Taxonomy, Media.
• Platform pages have Regions, Pricing, Taxonomy. Steam platform releases also expose the Steam App ID.
• Region pages have SKUs and Pricing, plus lifecycle, stock, pricing-coverage, and advisory Sales Readiness summaries.

Open Products → Catalog, choose a product, and use the hero to confirm that you are editing the right title. The hero carries product identity and the actions available for that record. Use the hierarchy beneath it to move into an edition, platform release, region release, or SKU.

The hierarchy is the route between workspaces. The side nodes show the tabs owned by each level; SKU-specific actions remain inside the Product or Region SKU views.

Use the highest level that owns the change. Move downward only when an edition, platform, region, or SKU genuinely needs its own value.

Overview is the structural dashboard. It shows the product's editions, platforms, regions, SKU counts, and availability summary. Use it to spot a missing branch before editing details.

Example: if Deluxe exists on Steam but not PlayStation, the Overview tells you whether the missing step is an edition-platform combination or a region beneath that platform.

Availability is the product-wide launch control. It brings region releases into matrix, edition-first, or platform-first views and lets you filter by edition, platform, region, launch phase, and trading state. It also supports staged bulk lifecycle changes and date copy/paste.

Use Availability & readiness before changing several releases at once.

Distribution summarizes which activated commercial models can reach the product and which connected Content Sellers currently have SKU access. Only models activated for your company and allowed by the product or SKU are eligible.

Use Manage distribution to select eligible SKUs for a connected Content Seller. A Manual badge means access was selected directly here; an Agreement badge means it comes from the applicable BMA catalog scope. These source badges explain why access exists.

Distribution is a configuration and coverage view, not the legal or commercial authority. It does not create an allocation or allocate capacity. The active partner MCA, applicable BMA, BMA catalog scope, allocation, and Dedicated stock remain under Partners & allocations.

Descriptions holds the product's localized store copy, including short and long descriptions, key features, and legal text. Add only languages your team can maintain accurately.

Edition pages also have a Descriptions tab for edition-specific copy. The current UI provides product- and edition-level editing and synchronization controls; it does not expose a generic description override at every level.

Taxonomy holds the canonical ratings, descriptors, genres, tags, and features used to classify the product. Edition and Platform pages can inherit or override taxonomy by category.

See Taxonomy & AUM for the inheritance model and Steam mapping.

Media manages assets attached to the Product. Edition pages have their own Media tab for edition-specific assets. Check which workspace you are in before uploading so artwork belongs to the intended level.

SKUs gives a product-wide view of the sellable units beneath its regions. Use the Region workspace when you need to add a SKU, import keys, edit a SKU, or open its pricing controls in territory context.

Activity is the product change record. Use it to understand what changed and who performed the recorded action. It is an audit view, not another configuration surface.

Open an edition from the Product hierarchy.

Platforms & regions shows where that edition is released and how many regions and SKUs sit beneath each platform. Add the missing platform or region here when the edition's structure is incomplete.

• Descriptions holds edition-specific localized copy.
• Taxonomy inherits from Product by default and can be changed category by category.
• Media owns edition-specific assets.

Open a platform release from an Edition.

Regions lists the region releases for this edition and platform. Add only regions the company supports under Settings → Regions.

Pricing sets the platform default tier, automatic tier-update choice, and scheduled tier changes, then shows which regions inherit or override that default. Nintendo platform releases use region-level manual per-currency pricing instead of tier inheritance.

See Pricing before changing defaults that several regions inherit.

Taxonomy inherits from Edition by category unless you choose a platform-specific value. For Steam, the workspace also exposes the Steam App ID used by Steam-related catalog workflows. Do not assume every platform exposes a generic external-reference editor.

Open a region release from a Platform page.

SKUs shows key type, available and allocated stock counts, status, and SKU actions. Add the sellable units that apply to this exact platform and territory.

Pricing controls region inheritance, a different tier, tier plus country overrides, or fully manual country pricing. Individual SKUs can then override the effective region price where needed.

The Region header also shows lifecycle badges, SKU and key counts, pricing coverage, and Sales Readiness. Treat Sales Readiness as a checklist summary, not a guarantee that a partner can transact.

For a new Deluxe edition on Steam in Europe:

1. Use Overview to confirm the Edition → Platform → Region structure.
2. Complete Descriptions, Taxonomy, and Media at Product or Edition level.
3. Open the Platform and Region Pricing tabs to set the territory grid.
4. Use SKUs to add the sellable unit and prepare its key or keyless fulfillment path.
5. Use Availability to move the release to Available + Open when the launch is ready.
6. Use Distribution to confirm eligible models and Content Seller SKU access.
7. Return to Overview for a final structure and coverage check, then use Activity to verify the recorded changes.

Your team can answer “which level owns this change?” before editing: Product for shared identity, Edition for edition-specific content, Platform for platform defaults and mappings, Region for territory setup, and SKU for the final sellable and fulfillable unit.

"I changed a parent, but one child still differs." The child may have an override. Check taxonomy category inheritance, region pricing mode, and SKU pricing before changing the parent again.

"Distribution says the model is available, but the partner cannot sell." Check the partner MCA/BMA, BMA scope, allocation, lifecycle, regional pricing, and fulfillment readiness. Distribution coverage is not transaction authority.

"The artwork or copy appears at the wrong level." Return to the Product or Edition workspace that owns it. Do not assume all child workspaces expose the same editing controls.

• Pricing
• Taxonomy & AUM
• Availability & readiness
• Partners & allocations