Add-ons (also sometimes referred to as in-app products) are supplementary items for your app that can be purchased by customers. An add-on can be a fun new add-on feature, a new game level, or anything else you think will keep users engaged. Not only are add-ons a great way to make money, but they help to drive customer interaction and engagement.
Add-ons are published through the Windows Dev Center dashboard. You'll also need to enable the add-ons in your app's code.
The first step in the add-on submission process is to create the add-on in the dashboard by defining its product type and product ID. After that, you can create a submission so that your add-on can be purchased via the Microsoft Store. You can submit an add-on at the same time you submit your app, or you can work on it independently. And you can make updates to add-ons after the app is in the Store without having to resubmit the app again.
This section of the documentation describes how to submit add-ons in the Dev Center dashboard. Alternatively, you can use the Microsoft Store submission API to automate add-on submissions.
Checklist for submitting an add-on
Here's a list of the info that you provide when creating your add-on submission. The items that you are required to provide are noted below. Some of these are optional, or have default values already provided that you can change as desired.
Create a new add-on page
|Product lifetime||Required if the product type is Durable. Not applicable to other product types.|
|Quantity||Required if the product type is Store-managed consumable. Not applicable to other product types.|
|Subscription period||Required if the product type is Subscription. Not applicable to other product types.|
|Free trial||Required if the product type is Subscription. Not applicable to other product types.|
|Keywords||Optional (up to 10 keywords, 30 character limit each)|
|Custom developer data||Optional (3000 character limit)|
Pricing and availability page
|Markets||Default: All possible markets|
|Visibility||Default: Available for purchase. May be displayed in your app's listing|
|Schedule||Default: Release as soon as possible|
|Publish date||Default: Publish as soon as possible|
One Store listing required. We recommend providing Store listings for every language your app supports.
|Title||Required (100 character limit)|
|Description||Optional (200 character limit)|
|Icon||Optional (.png, 300x300 pixels)|
When you've finished entering this info, click Submit to the Store. In most cases, the certification process takes about an hour. After that, your add-on will be published to the Store and ready for customers to purchase.
The add-on must also be implemented in your app's code. For more info, see In-app purchases and trials.
Updating an add-on after publication
You can make changes to a published add-on at any time. add-on changes are submitted and published independently of your app, so you generally don't need to update the entire app in order to make changes to an add-on such as updating its price or description.
If your app is available to customers on Windows 8.x, you will need to create and publish a new app submission in order to make the add-on updates visible to those customers. Similarly, if you add new add-ons to an app targeting Windows 8.x after the app has been published, you'll need to update your app's code to reference those add-ons, then resubmit the app. Otherwise, the new add-ons won't be visible to customers on Windows 8.x.
To submit updates, go to the add-on's page in your dashboard and click Update. This will create a new submission for the add-on using the info from your previous submission as a starting point. Change the info you'd like, and then click Submit to the Store.
If you'd like to remove an add-on you've previously offered, you can do this by creating a new submission and changing the Distribution and visibility option to Hidden in the Store with the Stop acquisition option. Be sure to update your app's code as needed to also remove references to the add-on (especially if your app supports Windows 8.1 earlier; this visibility setting won't apply to those customers).