Unit-Based Pricing

Unit-based pricing is for recurring products where the customer declares a quantity up front and pays for that quantity each billing period. It works well for devices, workspaces, locations, projects, or any other billable unit that does not need a person or seat assignment. Unlike usage-based billing, the quantity is selected before payment and does not come from usage events. Unlike seat-based pricing, units have no invitations, members, or benefit grants of their own.

Unit-based prices are supported on subscription products only. OurPay rejects a unit-based price on a one-time product.

Pricing models

Each currency can have one unit-based price and, optionally, a fixed recurring base price. A unit-based price cannot be combined with a seat-based or pay-what-you-want price.

Model	How the amount is calculated
Fixed per unit	Every unit uses the same rate. Internally this is one unbounded volume tier.
Volume	The tier selected by the total quantity supplies the rate for every unit.
Graduated	Each range is priced at its own rate, then the tier totals are added together.

For tiers of 1–10 units at

10 and 11+ units at

8, a quantity of 14 costs:

Volume: 14 × $8 =$ 112
Graduated: 10 × $10 + 4 ×$ 8 = $132

Rates sent to the API are whole integers in the currency’s smallest unit. For USD, 1000 means $10.00. The final tier may have a null bound for an unlimited maximum. When the final tier has a numeric bound, that value is the maximum quantity customers can buy.

Create a unit-based product

In the dashboard, create a Subscription product and select Units as the pricing type. Then:

Enter singular and plural labels, such as device and devices.
Choose fixed, volume, or graduated pricing.
Enter the unit rate for each tier.
Optionally set a minimum quantity. The default is one.

If Units is not shown, unit-based pricing has not been enabled for the organization by the deployment operator. You can also create the product with the TypeScript SDK:

import { createOurPay } from "@ourpay-dev/sdk/2026-10";

const ourpay = createOurPay({
  accessToken: process.env.OURPAY_ACCESS_TOKEN!,
});

const product = await ourpay.products.create({
  name: "Managed devices",
  recurring_interval: "month",
  prices: [
    {
      amount_type: "unit_based",
      price_currency: "usd",
      minimum_units: 5,
      unit_label: {
        en: { "=1": "device", other: "devices" },
      },
      tiers: {
        type: "graduated",
        tiers: [
          { bound: 10, unit_amount: "1000" },
          { bound: null, unit_amount: "800" },
        ],
      },
    },
  ],
});

See Create Product for every product field.

Choose the quantity at checkout

By default, checkout starts at the product’s minimum and lets the customer choose an allowed quantity. You can constrain or lock that value when creating a Checkout Session:

const checkout = await ourpay.checkouts.create({
  products: [product.id],
  units: 25,
  min_units: 10,
  max_units: 100,
  success_url: "https://example.com/success?checkout_id={CHECKOUT_ID}",
});

console.log(checkout.url);

units preselects the quantity.
min_units and max_units narrow the range for that session, but cannot exceed the product price’s own bounds.
A Checkout Link can save a fixed units value. Sessions created from that link are locked to the saved quantity.

The selected quantity and localized unit label appear in checkout, the resulting subscription, orders, and invoices.

Change subscription units

An organization can change the declared quantity through the subscription API. OurPay validates the new value against the price bounds and applies the organization’s default proration behavior unless one is supplied explicitly.

await ourpay.subscriptions.update("subscription-id", {
  units: 40,
  proration_behavior: "invoice",
});

With invoice, an increase creates an immediate prorated charge and a decrease creates the corresponding prorated credit. With prorate, the adjustment is recorded for the next invoice. The next renewal uses the new full-period quantity. Unit changes are organization-controlled. The customer portal displays the current quantity but does not currently let customers edit it themselves.

Switching an existing unit-based subscription to a product without unit-based pricing is not supported. Migrate the customer to a compatible unit-based product or create a new subscription.

Events and reconciliation

Listen for subscription.updated to detect quantity changes and order.created / order.paid to reconcile prorations and renewals. Billing entries retain the increase or decrease that produced each invoice amount, so integrations should use the resulting order rather than recomputing a charge from the current quantity.

Bootup

Features

Integrate

Merchant of Record (MoR)

Unit-Based Pricing

Pricing models

Create a unit-based product

Choose the quantity at checkout

Change subscription units

Events and reconciliation

​Pricing models

​Create a unit-based product

​Choose the quantity at checkout

​Change subscription units

​Events and reconciliation

Pricing models

Create a unit-based product

Choose the quantity at checkout

Change subscription units

Events and reconciliation