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.
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 groupNavigate to the **Packages** page for your product, and then select **Add mar...
In the **Select markets** window, select the markets you want to target with ...
- 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.
- 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.
After finalizing your selection, give it a **Market group name** (a maximum o...
Select **Continue**.
Select **Save draft** to save your configuration.
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:Customers that have a previous package installed can start downloading the ne...
New customers who download the product from the Store will start getting the ...
Customers who own the game and who've installed the package can launch and us...
Setting the package availability date
Navigate to the **Packages** page for the packages you want to configure.
Under **Advanced options**, select **Configure custom availability date for y...
Set a date and time (UTC) the packages will become available and mandatory.
Select **Save draft**.
- 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.
