Apple does, but the product's website does not. As the above poster was pointing out: if the product is worth paying for the Op should make that clear.
If a product is available in the Mac App Store only, it gets tricky because you can provide the US price, but all other prices are generated by Apple in relation to the US price for other regions. This can cause confusion. Been there, done that. It's a tricky situation even for the developer.
Sure, the product's website doesn't display the price, and I agree that it should, but I was replying to this:
> it's not displayed on the App Store description either.
Developers don't need to (and, imo, shouldn't) put pricing in the App Store description, because that's what the auto-generated "In-App Purchases" list is there for.
Agreed, you'd have to localize the description to support all currencies and then update whenever the price tiers or tax rates change. For the website: I just added the pricing in USD.