u/Dazzling-Fishing593

When I moved Zilch Standard from VCL to FMX, it was a substantial rewrite - SQLite, a fluid resizable interface, light and dark themes, and a path toward cross-platform distribution.

I raised the price to $69.95 because my investment had gone up, Delphi cost more, FastReport cost more, FastSpring cost more, and the product was substantially better.

Then I arbitrarily added another $10 for the Microsoft Store.

That didn't go particularly well. 😉

The mistake wasn't believing the software had value. The mistake was calculating that value almost entirely from my side of the desk.

I wrote about what happened, the pricing research I eventually did, and the distinction I finally learned between B2B and B2C software pricing.

Maybe another Delphi developer can learn this one before spending 35 years figuring it out.

https://capecodgunny.blogspot.com/2026/08/35-years-delphi-development-pricing.html

I have a software product written with Delphi that I've been selling for 35 years. I recently submitted my software to the Microsoft store. Even though I have a 35 year history, I'm a new seller and my product is new to their store. My first submission was rejected because "the price was too high". The specifically cited 10.8.7 Financial Transactions in the store policies . https://learn.microsoft.com/en-us/windows/apps/publish/store-policies

I have lowered the price and resubmitted. 🤞

Have any of you gone through the Microsoft store submission process?
What was your experience?
Did you get rejected for price?

Details:
Several people have asked what price Microsoft considered too high. Debt Blaster was submitted at $79.99. Microsoft rejected it under policy 10.8.7, saying the price was unreasonably high compared with similar products, but they did not provide an acceptable range.

After thinking it through, I decided $69.99 was a better regular price for Debt Blaster anyway. I updated FastSpring and the website, then resubmitted to Microsoft at $69.99. It is now back in certification.

I am sharing the specifics because other Delphi developers may run into the same issue with paid desktop software.