Content Owner availability & readiness

Move a release through its launch plan with confidence, then verify every commercial and fulfillment layer separately before expecting a Content Seller to transact.

Content Owners scheduling launches, pausing sales, preparing several regions at once, or diagnosing why a structured catalog item is not yet sellable.

• The Product Availability tab controls launch phase, trading state, and launch dates across region releases.
• Launch phases are Draft, Announced, Pre-order, Available.
• Trading states are Open, Paused, Discontinued.
• Sales Readiness is an advisory completeness summary, not transaction authority.
• Standard transaction readiness currently requires Available + Open. Do not treat a Pre-order label or window as a promise of a general pre-order checkout flow.
• Structure, visibility, partner scope, price, inventory or provider readiness, and allocation capacity are separate checks.

Open Products → Catalog → product → Availability.

Choose the view that matches the job:

• Matrix for scanning lifecycle state across releases.
• Edition first for coordinating each edition across platforms and regions.
• Platform first for coordinating storefront launches across editions and regions.

Filter by edition, platform, region, launch phase, or trading state. For repeated schedules, copy dates from one release and paste them into selected releases. Bulk lifecycle changes are staged first; review them and use Save all to persist.

The Set all live button opens the Set everything live dialog. Confirming moves eligible releases to Available and Open. Archived and Discontinued releases are skipped, and releases missing launch requirements remain blocked for review.

Use Draft while structure, content, dates, and commercial setup are incomplete. Draft releases are not intended for Content Seller catalog visibility or transactions.

Announced allows launch information to become discoverable where the partner catalog scope permits it, without making the release transaction-ready.

Pre-order represents the release's planned pre-order lifecycle and dates. It can make the launch discoverable, but the current standard transaction path still requires Available + Open. Do not promise a general pre-order purchase flow from this phase alone.

Available is the required launch phase for standard transactions. It still needs Open trading and every commercial, pricing, capacity, and fulfillment check.

• Open permits trading when the launch phase and other readiness layers allow it.
• Paused temporarily prevents standard selling without declaring the release finished.
• Discontinued removes the release from normal selling and partner visibility.

Use Paused for a temporary stop. Use Discontinued only when the release should no longer be offered.

Launch dates can move the effective lifecycle forward automatically. The minimum phase pins the earliest state the schedule may use, so the release does not move back below a deliberate manual decision.

Review announce, pre-order, and release dates as one sequence. A phase cannot advance when its required dates or other launch checks are incomplete. Once a date belongs to a completed phase, Availability may no longer allow that date to be pasted over.

Archived items are excluded from normal catalog and bulk Availability work. Archiving a Product, Edition, Platform release, or Region release can cascade to children beneath it. Allocated keys on an affected SKU can block the child or parent archive.

Use only the archive and restore actions exposed for the specific item and list view. A restore may include descendants, but the available action depends on the archived record and current hierarchy. Review the preview and dependency messages rather than assuming every hierarchy can be restored from any screen or in one step.

The SKU exists beneath the intended Product → Edition → Platform release → Region release. This proves the sellable unit has a place, not that it can sell.

The item is not archived or Discontinued and has moved beyond Draft. Announced and Pre-order can support discovery, while Available is required for standard transactions.

The partner has an active connection, the applicable MCA and BMA, and catalog scope that includes the SKU. Visibility can exist before transaction readiness.

The applicable BMA and commercial Share authorize the SKU, the allocation is active, and the lifecycle is Available + Open. Product Distribution can summarize reach, but it does not replace partner Agreement authority.

For key-based fulfillment, the SKU needs usable key inventory. For keyless fulfillment, the configured provider path must be ready. A key count cannot prove that a keyless order will activate, and a provider configuration cannot supply a key-based SKU.

The Content Seller needs remaining capacity under the active allocation. Dedicated stock may earmark concrete keys to that allocation, but it does not raise the allocated quantity.

The sale country needs an effective territory catalog price where the model requires it. Wholesale and Traditional Revenue Share commercial amounts remain in the BMA or allocation terms.

The Region workspace shows Sales Readiness as a percentage and checklist of catalog completeness, including product information, platform, pricing, SKU, key inventory, and platform ID signals.

Use it to find missing setup quickly. Do not use 100% as a promise that a particular Content Seller can buy. It does not replace the partner Agreement, BMA scope, allocation capacity, current lifecycle, model-specific price authority, or keyless provider check.

Suppose a Deluxe Steam SKU is visible to a Content Seller in Germany, but checkout fails. Follow one branch at a time:

Commercial gates — each one must pass before the next is checked:

Fulfilment path — once the price is ready, the delivery mechanism is the last check:

For Agreement + Share, verify the active MCA, applicable BMA, and SKU scope. For Price, use territory catalog pricing when the model requires it and partner commercial terms otherwise. The first failed branch identifies the layer to fix; catalog visibility alone proves none of the later checks.

The intended SKU has complete structure, Available + Open lifecycle, active partner Agreement and Share, remaining allocation capacity, the applicable regional price, and usable key inventory or a ready keyless provider.

"The product is visible but checkout is blocked." Visibility and sellability differ. Confirm Available + Open, BMA scope, active allocation, applicable country pricing, and fulfillment readiness.

"Sales Readiness says 100%, but the Content Seller cannot transact." Treat the score as advisory. Check the partner-specific Agreement, Share, Allocation, and Price path in Partners & allocations.

"The release is in Pre-order, but an order is rejected." The standard transaction path requires Available. Pre-order lifecycle and dates do not by themselves enable a general pre-order purchase flow.

"Set all live skipped a release." Open the blocked release and review the missing launch requirements. Archived and Discontinued releases are intentionally excluded.

"There are keys, but no capacity." Inventory and allocation answer different questions. Increase or release capacity deliberately; Dedicated stock cannot exceed the allocated quantity.

• Product workspace
• Pricing
• Inventory
• Partners & allocations