Pricing Models

For single payment and subscription products we offer a lot of pricing flexibility with our various pricing models.


You have the option of charging a flat price or charge precisely based on usage.

Pricing models are applied at the variant level so you can have one product with variants using different pricing models.

Lemon Squeezy: pricing models

Flat-rate pricing models

Flat-rate pricing models charge customers up-front, and you can charge an amount of items using a quantity at checkout.

Standard pricing

Standard pricing is the default setting. It lets you charge a single fee for a product or subscription.

Changing the quantity value will simply charge customers a multiple of the regular price. For example, setting the quantity to 3 for the example below would charge the customer 3 × $9.99 = $29.97.

Lemon Squeezy: standard pricing

Package pricing

Package pricing lets you charge a fixed amount for a fixed amount of units.

For example, you can sell packages of API credits at a certain price. As usage increases past the package’s unit limit, you would charge for an additional package.

Changing the quantity value will charge customers based on how many packages need to be bought for that quantity.

For example, if you sell 100 credits for $10, setting the quantity to 120 will charge the customer for two packages (2 × $10 = $20) because their usage has gone past the 100-credit limit for the first package.

Lemon Squeezy: package pricing

Tiered pricing models

Tiered pricing models charge customers with much more flexibility and at a unit level, and can be used alongside Usage-based billing for easy usage reporting.

If you want to charge a recurring base fee on volume and graduated subscriptions alongside unit usage, you can add a flat fee to each pricing level.

Volume pricing

Volume pricing lets you charge a fixed per-unit cost based on the tier customer usage falls into.

For example, you sell software by seats and charge $5/month each up to 5 seats and $4/month per seat after that. Setting the quantity to 8 would charge the customer 8 x $4 = $32.

You can either use quantity-based billing to charge by usage (which will charge customers up-front), or enable usage-based billing for more flexible reporting (which will charge customers retrospectively).

Lemon Squeezy: volume pricing

Graduated pricing

Graduated pricing lets you charge variable unit prices across different usage tiers (instead of a single unit cost like volume pricing).

For example, you sell software by the number of orders placed in a marketplace, charging a flat fee of $5/month plus $3/order for the first 50 orders, $2/order for the next 50 orders and then $1/order for all additional orders. Setting the quantity to 180 would charge the customer $5 + (50 × $3) + (50 × $2) + (80 * $1) = $335.

You can either use quantity-based billing to charge by usage (which will charge customers up-front), or enable usage-based billing for more flexible reporting (which will charge customers retrospectively).

Lemon Squeezy: graduated pricing

Charging customers based on their usage

When selling subscriptions using any of the four pricing models, you can use quantity-based billing by updating a subscription’s quantity value with the API, which will change the amount your customers are charged at the next renewal.

Alternatively you can opt to enable usage-based billing on each product variant to charge customers based on their real-world usage in arrears.

Read how to implement usage-based billing in detail in our Developer Guide.

Setup fees

Setup fee is a one-time charge applied at the start of the subscription period. This fee is charged in addition to regular subscription fees and is typically used to cover the initial costs associated with setting up an account or service.

For example, if a subscription is $10 per month and the setup fee is $15, the initial payment will be $10 + $15 = $25, followed by the regular $10 monthly fee.

This option is available for all types of subscription products, including those that offer trials or utilize usage-based billing.


Was this page helpful?