In-app product properties
This topic applies to the earlier Windows Phone Dev Center dashboard and not the new unified Dev Center dashboard. Since we are still in the process of migrating all developer accounts, the info here may not apply if your account has already been migrated to the new dashboard. For more info, see Using the unified Dev Center dashboard.
Note: You can use in-app products only in apps for Windows Phone 8 and later versions.
An in-app product is a supplementary item for your app that can be purchased by users. This product can be a fun new add-on feature, a new game level, or anything else you think will keep users engaged. Not only are in-app products a great way to make money, but they invite users to experience a new layer of interactivity and immersion with your app. Here’s the first step for submitting in-app products into Windows Phone Dev Center.
It’s possible that your app will be in certification even if your in-app product has made it through the process. We recommend that you design your app to handle this situation.
First, give your in-app product an alias, a name to identify it on Dev Center. Like the app alias, your in-app product alias needs to be unique and can be up to 100 characters.
If your in-app product is added to an app that was previously associated with a Windows app, or if you plan to associate the app with a Windows app in the future, in-app products that share the same alias in the Windows Store and Windows Phone Store must also share the same type, Consumable or Durable, for example.
Enter the Product identifier you’ve created in your app. This identifier needs to be unique to the app. It’s important to note that once you submit your in-app product, the Product identifier can’t be changed.
After you've given your in-app product an alias, select the Product Type you’d like it to be.
Consumable A product that’s bought, used (consumed), and bought again, like 1000 pieces gold in a game.
Durable A product that’s bought and owned by the buyer forever, like a game level. Durable products aren’t consumed.
Once you've submitted your in-app product, you won’t be able to change the Product Type, so make sure to give it some thought before you submit.
If you selected the Durable type, you need to specify the lifetime of the product. The Product lifetime represents how long a customer can use an in-app purchase, after which time the customer must purchase the product again. You can change this value in the future, and any new value will take effect for new customers. The product lifetime for existing customers will remain unchanged. There is no product lifetime for consumables.
If you select a Product lifetime value other than Forever, the product will only be available to users who are running Windows Phone 8.1 or newer.
Next, you must select a Content type for your product. This field defaults to Electronic software download, which is the most common. If the content of your product is something different, such as a music download or e-book, select the content type in the Content type list.
Last, select the Default language that you’d like us to the app supports more languages than you give in the description.
Select the Base price for your in-app product in the drop-down. You can list the same in-app product at different price points per region just as you can for apps. Beta users won’t be charged for your in-app product when they test against your beta app. Also, changing your app’s price after submitting it for certification won’t affect your in-app product submission. To learn more about pricing customization, see Define pricing and market selection.
You can’t submit paid in-app products if your account is registered in countries or regions that do not support payout.
Once you’re finished with the Details and Pricing in Step 1, you can save your changes and move on to Step 2, In-app product description. If you’d like to customize your in-app product beyond what you’ve already done, click the More Options drop-down.
When it comes to development, no two apps are exactly alike. The same principle applies to in-app products. In More Options, you can make a few simple but important changes to the properties for your in-app product.
Publish your app manually
By default, your app will be published as soon as it’s certified. If you’d like to publish it manually instead (for example, you’d like to time the release of your in-app product), select Manually publish.
Create dynamic views
In Dev Center, you can create dynamic views for your in-app purchase content. Provide up to ten Keywords for each in-app product you submit. Your app can then query for products that match these words. This feature lets you build screens that can load products without you having to bake in the Product-IDs. After you submit your in-app product, you can change keywords at any time without affecting the certification process.
Use tags to drive context
With Tags, you can drive the context of your in-app product. Let’s say you have a game, and you’re selling a bag of gold coins as an in-app product. Using the Tags field, the app can query for this bag of gold. Using the Tags feature, you can adjust the value at any time (in this case, the number of coins in your bag). Don’t worry about changing tags after you submit your in-app product. It won’t affect the certification process.
Customize your description
If you’d like to describe your in-app product in multiple languages on the Store, select the countries/regions under Windows Phone Store languages. Note that you’ll need to write the description for each language you select in the respective language.
Once you've finished creating or updating in-app product properties and you're satisfied with your changes, click Save. If your Save is successful, you'll be sent back to the submission hub page. You're ready to proceed to Step 2, In-app product description.