Export (0) Print
Expand All

Provide price and market details for your desktop app

Set a price and specify market details for your desktop app, as part of getting it listed in the Windows Store.

Price tier

The price tier you choose for your app must accurately reflect the price of your app on your own acquisition page. A Windows Store app listing must not be misleading to users.

Windows users have given feedback that some app price listings have not been clear, or that the Windows Store listing is misleading when compared to the developer’s website. At times such issues have resulted in poor reviews for the app listed in the Windows Store. In particular, paid apps cannot claim to be free in a Windows Store listing—the info in the Windows Store product description page must match that on the acquisition site.

Note that desktop apps in the Windows Store can be listed only as paid or free; there is no option during app submission to list an app as having a trial version. However, you can indicate in your listing description that a free trial is available for your app.

A paid app in the Windows Store may:

  • Assume or require purchase of another component in order to work.

  • Be a limited-time, trial version that loses functionality after a period of time.

(These are examples, not a comprehensive list.)

A free app in the Windows Store (again, for example) has these characteristics:

  • The version of the app listed in the Windows Store is free in perpetuity.

  • The app has "functionality," but may require in-app purchases for things like specific new levels or capability upgrades.

The Windows Store does not handle commerce for desktop apps. This means that the price you choose is not shown on the app tile or on the app’s product description page in the Windows Store. The price tier you choose will be used only for sorting and filtering in the Windows Store. Your app price should be correct so that the Windows Store can filter and sort your app accurately based on price.

The way price tiers are created in the Windows Store does not enable you to list your app with different prices for different markets. We recommend that you pick a price that represents the median price for your app in its main markets.

Price tier field in Selling details section

Markets

The markets you choose affect the markets where Windows users see your desktop app. Choose your markets carefully. If you do not select a market, Windows users in that market will not see your app in the Windows Store. If you have a Windows 8 and a Windows 8.1 version of your app associated with one listing in the Windows Store, the market choices you make apply to both versions as part of the same listing.

Here's how this works. The user language and region preferences in Windows 8 will determine which market the Windows Store detects for a user. There are also some settings in the Windows Store that can be changed by the user at any time. The Rest of World market selection covers all other markets outside of the defined set in the Windows Store. There is no way to pick and choose a subset of markets from among the Rest of World markets at this time. Be sure to check that the list in the Windows Store matches the markets available on your own acquisition page.

At any time after your app is published in the Windows Store, you can choose to remove your app from the Windows Store, or to add or remove a market for your app in the Windows Store. To remove your app, simply clear the market selections for your app. Once this change is complete and submitted, you will still be able to see your app in the Store dashboard, but your app will not be visible to users. To list your app, select the appropriate markets again and resubmit.

Languages

Markets and languages are separate concepts in the Windows Store: you choose the languages for your app separately from the markets. For each language you choose, you must fill out a language-specific description page for your app. On this language-specific page, you can add links to your acquisition page so that users can acquire your app directly. For example, if you choose English and German, you must complete two description pages (one for each language).

You are required to complete these pages before you can submit your app for Windows Store certification. Even though you add your markets and languages separately during submission, it’s a good idea to fill out at least one language-specific description page for each market you choose.

Languages section of the Selling details page

Release date

This is the date that your app will be available to users in the Windows Store. Regardless of which date you enter here, your app will be reviewed for Windows Store certification as soon you complete your listing data entry and submit your app certification. This means that if your app-acquisition experience is not yet live (that is, that your own website is not yet available) when your app is reviewed, your app will fail certification. If this happens, you will receive an email describing the failure. You can resubmit your app for certification when your site is available or hold your original submission until your site is available. If you would like to provide password access for Windows Store certification reviewers, you can do so in the Notes to testers field, the last step in the submission process.

Release date section of the Selling details page

Categories and subcategories

You can place your app in a category and subcategory in the Windows Store. You can choose only one category, and if there are subcategories available for your chosen category, you must pick one. To help you plan how to list your app, refer to the current list of categories and subcategories for the Windows Store.

App category and subcategories section of the Selling details page

Protocols and file extensions

If you would like to list the supported protocols and file extensions for your app, you can add these here. Be sure to separate items in your list with a semicolon. The info you enter here is used by Windows to display suggested apps in the Windows Store if, for example, a user attempts to open an unknown file type.

Protocols and file extensions section of the Selling details page

Related topics

Provide age rating info
Walkthrough: Desktop app submission
Certification requirements for Windows desktop apps

 

 

Build date: 11/16/2013

Community Additions

ADD
Show:
© 2014 Microsoft