Hello Community! 🙂
There appears to be a couple of oversights present in both the public app marketplace's application form, located in the 'Pricing' section as well as the listing copy in the same section for published apps.
App application form
1) Pay-as-you-go pricing is limited to whole cents only. Many API products are priced per API call, and many have fractional cent pricing, e.g. $0.009, you can circumvent this frontend field limitation by stating for example that $0.90 is per 100 API calls, but for accuracy sakes when a HubSpot customer compares this to the app partners own pricing page it should match. This creates a discrepancy between the HubSpot app listing pricing and the app partners web page pricing. Please enable a few extra decimal places in the pricing fields.
2) 'Contact us' as a pricing tier once selected requires mandatory selections of 'Starts from' and 'Frequency'. If 'Contact us' is selected then it is a stand alone statement, the app partner should not be forced to enter a price from or a frequency (which just so happens to only offer 'One time', 'Monthly' & 'Yearly'... counter intuitive to the pay-as-you-go options.). Please disable mandatory selection of 'Starts from' and 'Frequency' when selecting Contact us as a pricing tier.
App published listing copy
1) When the app is published, the copy should not reference subscription pricing models when the app's pricing is pay-as-you-go. There is a huge difference between the two pricing models and this confuses HubSpot users when we offer the more popular pay-as-you-go but the listing copy mentions subscriptions.
Two locations, in the main pricing section -
and on the upper right side snippet -
The listing application clearly gives you the option to differentiate between the two pricing models, but this is not reflected in the actual listings copy -
Please replace 'subscription' highlighted in screen shots with 'pricing' or reflect the apps selected pricing model option as per above.
2) The app listings copy would flow a lot better if words weren't breaking over lines -
Try using non breaking spaces or nowrap.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.