#Handling Custom-Priced Enterprise Subscriptions in Dodo Payments

1 messages · Page 1 of 1 (latest)

fringe moon
#

I’m working on implementing enterprise subscriptions using Dodo Payments and ran into a design challenge.

Problem:- For enterprise customers, pricing is custom per customer (e.g. ₹50K, ₹2L, ₹5L/month), along with custom limits/features.

However in Dodo:

  • Subscription pricing is fixed per product
  • We can’t pass a dynamic amount when creating a subscription

Given this, what’s the best way to handle enterprise subscriptions where pricing varies per customer?

wintry boughBOT
# fringe moon I’m working on implementing enterprise subscriptions using Dodo Payments and ran...

You’re right — subscription amounts aren’t dynamic in Dodo. Common patterns:

Option 1: Create a custom Price per customer (recommended)

  • Create a Product: enterprise-plan
  • For each customer, create a new Price with their agreed amount (₹50K, ₹2L, etc.)
  • Attach that price to the subscription
  • Map limits/features on your backend using customer ID

Option 2: Use add-ons / top-ups

  • Base subscription (fixed)
  • Add one-time or recurring add-ons to reach custom pricing
  • Messier to manage at scale

Option 3: Invoice-based billing (if highly custom)

  • Skip subscriptions
  • Generate recurring invoices manually via API
  • Best if pricing or terms change frequently

Typical setup

  • 1 product → many prices (one per enterprise deal)
  • Store contract metadata in your DB (limits, seats, etc.)

If you expect frequent price changes per customer, go with invoices. Otherwise, per-customer price is the cleanest.