> ## Documentation Index
> Fetch the complete documentation index at: https://devdocs.xbox.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Advanced settings for packages

> Manage advanced settings on the Packages page in Partner Center, including device family availability and pre-order placeholder package sizes.

The **Packages** page of your product in Partner Center is where you can upload packages for your product. In addition to discussing the specific features available only with proper permissions, this topic will discuss the differences between general and advanced experiences.

## Device family availability

The device family availability configuration in your **Game setup** defines which devices you must upload a package for. If you've specified **Retail** for a device family, you won't be able to publish to the RETAIL sandbox without uploading a package for the device family. If you've specified **Sandboxes** for a device family, you won't be able to publish to your development sandbox without uploading a package for the device family.

## Pre-order packages

If you've enabled pre-order in your **Pricing and availability** and you're using a placeholder package, select the **Contains placeholder package(s) to enable pre-order** checkbox. You'll be prompted to specify the expected maximum file-size for the final packages. This value will be shown on your product's Microsoft Store Product Details Page (PDP) and will direct customers who pre-order the product to install it on a drive with disk space sufficient for the full package, when it becomes available.

> \[!Important] At least one week before your product's release date, be sure to publish an updated package that replaces your placeholder package with your release packages. This will enable customers' devices to start installing the full package before release. When you make this change, clear the **Contains placeholder package(s) to enable pre-order** checkbox. For more information about pre-orders, see [Pre-orders](/publishing/game-publishing/concepts/availability/preorder-overview).

## Market-specific packages

In some scenarios, you might want to publish different packages to different markets. For example, you might want to omit particular content to comply with local age rating requirements. You can do this for any type of a product that uses packages, including games, game demos, and durables with packages.

Market-specific packages are supported on Store clients only on Windows 10, version 1607 or later (including XBOX).

### Configure market-specific packages

To configure a package for a specific market group

<Steps>
  <Step title="Navigate to the **Packages** page for your product, and then select **Add mar...">
    Navigate to the **Packages** page for your product, and then select **Add market-specific packages**.
  </Step>

  <Step title="In the **Select markets** window, select the markets you want to target with ...">
    In the **Select markets** window, select the markets you want to target with your market-specific package.

    * You can only select from markets that have been configured for the product in the **Pricing and availability** page's market selection. For details about configuring this section, see [Availability - markets, pricing, release schedule](/publishing/game-publishing/concepts/availability/availability-overview).
    * You must select at least one market. You can't include markets in multiple market groups.
    * You can't remove a market-specific package after it has been published.
    * A product can have a maximum of 10 market groups.
  </Step>

  <Step title="After finalizing your selection, give it a **Market group name** (a maximum o...">
    After finalizing your selection, give it a **Market group name** (a maximum of 256 characters).
  </Step>

  <Step title="Select **Continue**.">
    Select **Continue**.
  </Step>

  <Step title="Select **Save draft** to save your configuration.">
    Select **Save draft** to save your configuration.
  </Step>
</Steps>

If the market-specific package hasn't been published, you can select **Delete** to remove it.

To edit the markets for the market-specific package, select **Edit**.

## Package availability and predownload dates

When submitting an update for a product already published to the RETAIL sandbox, you have the option of setting a custom date on which the package will become **available**. On this date:

<Steps>
  <Step title="Customers that have a previous package installed can start downloading the ne...">
    Customers that have a previous package installed can start downloading the new package.
  </Step>

  <Step title="New customers who download the product from the Store will start getting the ...">
    New customers who download the product from the Store will start getting the newest package.
  </Step>

  <Step title="Customers who own the game and who've installed the package can launch and us...">
    Customers who own the game and who've installed the package can launch and use it.
  </Step>
</Steps>

You can also specify a **predownload** date. If the predownload date is the same as the **available** date, no additional functionality is enabled. If the **predownload** date is before the **available** date, customers that have a previous package installed can start downloading the new package from the configured date and time. They won't be able to use the new package until the **available** date and time that was configured.

Before the package's **available** or **predownload** date, customers will get the latest package available applicable to their device *not* including this scheduled version. After the scheduled date, customers will get the latest version available *including* this version. This lets you stagger updates and control when they reach customers.

### Setting the package availability date

<Steps>
  <Step title="Navigate to the **Packages** page for the packages you want to configure.">
    Navigate to the **Packages** page for the packages you want to configure.
  </Step>

  <Step title="Under **Advanced options**, select **Configure custom availability date for y...">
    Under **Advanced options**, select **Configure custom availability date for your XVC/MSIXVC packages**.
  </Step>

  <Step title="Set a date and time (UTC) the packages will become available and mandatory.">
    Set a date and time (UTC) the packages will become available and mandatory.
  </Step>

  <Step title="Select **Save draft**.">
    Select **Save draft**.
  </Step>
</Steps>

When setting a date, keep the following in mind.

* Ensure that the date is in the future.
* If the package hasn't already been Certified, allow sufficient time for Certification between now and the package's availability date.
* A custom availability date can be configured for the base package and any market-specific packages.
* This feature applies only to products already published to RETAIL. For details on setting availability dates for your first submission, see [Availability - markets, pricing, release schedule](/publishing/game-publishing/concepts/availability/availability-overview).

## Mandatory update

XVC package updates are *always* mandatory. Updates to PC MSIXVC packages aren't considered mandatory by default. For more information, see [Checking for updates](/publishing/xstore-commerce/xstore-commerce-overview).

## See also

* [Packages](/publishing/game-publishing/concepts/packages-overview)
* [XVC packages](/publishing/game-publishing/concepts/packages-xvc)


## Related topics

- [Packages](/publishing/game-publishing/concepts/game-package-management.md)
- [Configuring XBOX services setup in Partner Center](/services/xbox-services/fundamentals/portal-config/live-config-xbl-setup.md)
- [Multiplayer Session advanced topics](/services/xbox-services/multiplayer/mpsd/concepts/live-mpsd-details.md)
- [Using the Profile for Advanced Leaderboards](/services/playfab/community/leaderboards/tournaments-leaderboards/using-the-profile-for-advanced-leaderboards.md)
- [How to configure a pre-order](/publishing/game-publishing/how-to/how-to-preorder.md)