Feature Request for Shopify App Pricing: Tag donations in usage charges

Hello!

I am the co-founder of GoodAPI. We help brands streamline their climate and social impact programs. We use Billing API usage based pricing to charge for trees and plastics and have to rely on Stripe to collect donations. Terrible UX :slight_smile:

My BIGGEST feature request for the new Shopify Billing is to allow us to tag certain usage charges as “donations” so that they can get treated separately i.e. They don’t get charged under the 15% partner revenue share and can be passed through directly to our non-profit partners. That way we won’t need to create this hodge podge of Billing API for subscriptions and Stripe Billing for donations. Pretty please!

Mock Example
Instead of sending a $0.50 usage fee under Billing API, i would love to send
$0.48 donation, $0.02 fee

And treat the $0.02 as our revenue that should be subject to the partner revenue sharing and any other shopify fees. While the $0.48 is passed through directly so we can send it to our non-profit partners.

Happy to work with the team on this. We will migrate Yesterday if this was possible!

Hi @Mirvise, I had a look for you, and can confirm there’s no way today to tag usage charges as donations or exempt part of a charge from partner revenue share, on either the Billing API or Shopify App Pricing. Usage meters support fixed, graduated, and volume structures only and revenue share is calculated on gross app revenue, not the portion you retain, so the full $0.50 would count rather than just your $0.02 fee.

That means the split you’re running now (Billing API subscriptions plus Stripe for donations) is unfortunately the only real workaround, and I agree it’s not a great merchant experience. For the usage-based side of the model, App Pricing meters fed by the App Events API are the path going forward since the Billing API is now legacy, but that doesn’t change the donation treatment.

Your $0.48/$0.02 example is clear and I’ve shared this thread with the team internally as product feedback. Can’t promise anything on timing, but the detail on how you’d want it modeled is very useful context. Thanks for posting it here!