Prices can now live in a central product catalog and be shared across plans. Previously, a price could only be scoped to a single plan, so a price used across several tiers had to be copied into each plan separately. Now you define a list price once and reference it from every plan that uses it, so you can see which products you sell, at what prices, and which of your customers are on rates that differ from your standard pricing.

• Define once, reference everywhere: list prices live in the product catalog and can be referenced by multiple plans.
• Dimensional prices: dimensional prices can be defined once and shared across plans, alongside other common price types.
• Full API support: every price management and sharing operation in the dashboard is also available through the API.
• Activity feed: every pricing and packaging change records who made it, when, and why.

Shared products and prices are the default for new Orb accounts, which now set up catalog-first: ingest events, create metrics, build your product catalog, package prices into plans, then create subscriptions. Negotiated rates layer on top of list prices as overrides.

Learn more about the product catalog in our docs.

When you migrate subscriptions to a new plan version, you can now set the effective date to the start of the current invoice period or the start of the next invoice period. Each subscription switches on its own invoice boundary, so the new pricing covers a full billing period instead of starting partway through one.

The effective date step in the migration flow has also been redesigned, with options grouped by what they align to:

• Align to invoice period: start of current invoice period, start of next invoice period
• Align to subscription term: start of current term, start of next term
• Custom timing: on a specific date, or immediately

Learn more about migration effective dates in our docs.

You can now choose which subscriptions a plan version migration applies to by uploading a list of subscription IDs. Use it to migrate a prioritized subset first, run start-of-cycle migrations for specific customers of yours, or carve out edge cases from a bulk run.

Previously, you had to pick subscriptions one at a time in the table or rely on filters.

• On a plan's Subscriptions tab, click Select subscriptions by CSV.
• Upload a CSV with one subscription ID per row in the first column (an optional Subscription ID header is supported), or a TXT file with one ID per line.
• Each upload can include up to 250 subscriptions.

Learn more about plan version migrations in our docs.

You can now start as many plan version migrations as you need at once. Previously, running more than three migrations concurrently could cause them to fail. Now any migrations beyond that limit are queued automatically and start as soon as capacity frees up, so bulk plan changes no longer need to be spaced out by hand.

To follow progress, open the new Migrations tab under Plans > Migrations. It lists each migration with its plan, target version, created date, subscriptions migrated, and status:

• Queued
• Scheduling
• Completed
• Action needed

Learn more about plan version migrations in our docs.

When adding a pre-purchase allocation to a plan or subscriptions, Orb now supports a custom expiration option for each allocation credit block. This option allows you to set a specific number of days or months after which the block should expire. This option can be configured in both our UI and API.

To learn more about allocations, please visit our docs.

Orb now allows you to anchor your billing cycles to a custom date. Previously, you were able to specify the day of the month on which billing cycles were anchored. Now, you're able to specify a full date. 

For example, a quarterly subscription anchored on March 16, 2024 with a start date of October 10, 2023 and an end date of March 16, 2024 would have the following billing periods: October 10, 2023 - December 16, 2023, December 16, 2023 - March 16, 2024.

Orb now supports specifying a custom billing cadence or one-time service period. Previously, prices could only recur monthly, quarterly, semi-annually, or annually. Now you're able to specify a custom duration in days or months. You can also now specify a custom service period duration for one-time prices, which determines the duration of the line item.

The new billable metric "Debugging" tab enables you to test your metric before publishing. It shows you the result of evaluating the metric for a customer over a time range without needing to create a subscription. To create a new metric, we recommend the following workflow:

1. Define the metric and save it as a draft (with "Save & exit").
2. Verify the metric returns the expected results on a few customers using the "Debugging" tab in the billable metric detail page.
3. Change the metric if necessary and repeat verification.
4. Publish the metric.

We've added a "maximum spend" concept to our pricing models! This allows you to configure plans with a spend-cap at the price or the plan level from the plan or subscription creation flows.

We've also added support for limiting spend on an individual invoice at the line item or invoice level through the existing invoice edits flow.

Plans in Orb can now be configured with prices in a combination of custom credits and real-world currencies. The custom credits concept backs Orb's prepurchase ledger.

When configuring a plan, each price can be in either credits or the plan's invoicing currency. If the user subscribed to a mixed credits/currency plan and has pre-purchased credits, prices in credits will draw down from the pre-purchase balance, and any overage will be invoiced at the end of the billing period at the configured 'price per unit' rate for credits.

Learn more about working with prepaid balance in Orb's docs.