Microsoft Store App: selling externally, multiple editions ~ multiple products

Question

Hello,

I have 2 questions. I'd like to get my cross-platform desktop app crowd-funded in the first stage.

This to me means discounts, and I was thinking that I would realize that via codes that I'd effectively provide outside the Store.

By the delivery of these sales will have supposedly started via the Store as well (free trial + pro license, free for non-professional use fashion - this is to be implemented in the future and to be rolled out via an update).

I don't think MS requires to be an exclusive distributor/partner. Thought it's best to check anyway, since sales/delivery would take place over multiple channels in the above scenario, so the first question is:

1. Is it legitimate to build in such unlocking mechanism into the product that allows for external purchases, e.g. via my website? Especially if purchasing is being made possible - beside the unlocking codes - via Store add-ons, in parallel?
   Then, if not, I might consider working around that by splitting product lines (one definitely sold via the MS Store using add-ons, a second allowing free personal licenses and free professional versions for early supporters, also in the Store). I'd also 'fork' a third version that I privately use for testing.
2. Is it okay to have multiple versions of the same product perhaps only different in purchase mechanisms? If not, can I at least have one branch for testing?
   (A classic scenario is ProductA-lite, ProductA-pro, but I'd also have a ProductA-test, privately shared.)
   As a last resort, I might just create a build for my site (or another partner), operate purchases there in that way, and keep distributing at more rigid, completely customer-agnostic prices via the Store. I believe that then is fine, but please correct me if I'm wrong.

Thank you for the reply!

Regards

Janos

Answer 1

Hello,

Welcome to Microsoft Q&A!

For the first question, it is mentioned in the Microsoft Store Policies 10.8.1 that You must use the Microsoft Store in-product purchase API to sell digital items or services that are consumed or used within your product. Your product may enable users to consume previously purchased digital content or services, but must not direct users to a purchase mechanism other than the Microsoft Store in-product purchase API.

If you want to upload your app to the store, then you should follow the Store Policies.

For the second question, I have to say no as well. Generally, there is only one version of an app in the store. You will need to create another app in the store and upload another package if you want to have different versions of your app.

For example, if you want to have both ProductA-lite and ProductA-pro in the store, you will need to:

1. Create an app called ProductA-lite, upload a package for it, pass the certification.
2. Create an app called ProductA-pro, upload a package for it, pass the certification.

If you want to have an additional version for testing purposes, then I'd suggest you use the Package flights function of the Store. This function could let you distribute specific packages to a limited group of testers. Please refer to Package flights for more information.

Thank you.

---

If the response is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Answer 2

Hi Roy,

Is there a way to use these licenses on Linux by any chance?

Say I just start with a one-off payment yielding a perpetual license, which allows the user to operate the product on Windows, would I be able to use the Store API based validation on Linux (beside)?

In other words the aim is to make a license obtained for Win10 more platform "neutral"? I'd need some identification/association for this.

So far I'd be the happiest if I wouldn't have to operate pretty much anything (such as a webshop) but rather could concentrate on development - this could help. However, one possible (within this current plan, likely, yet fallback) approach is to let Linux versions be free to use.

Thank you,

Janos