Skip to content

Switching from another platform

What Stripe, Chargebee, Recurly, Maxio and Paddle call the things in your catalog here.

Every billing platform names the same handful of ideas differently. If you're arriving from one of them, this table maps their words onto ours.

The vocabulary bridge

Here Stripe Chargebee Recurly Maxio / Chargify Paddle
Plan Product + recurring Price Plan (Item) Plan Product ("Plan") Product
Add-on none (just another product) Addon Add-on / Item Component none (by convention)
Charge one-time Price Charge Item charge One-time component Price without a billing cycle
Price Price Item Price / price point Plan pricing + segments Price Point Price
Group none Product Family none Product Family none
Compatible add-ons none Applicable addons Plan add-on list Family scope none
Replace a price new price + archive old new price point none new price point none

What behaves differently here

  • A plan is one thing, its prices are variants. Like Stripe and Chargebee 2.0: the plan holds identity (name, invoice name, group), and each price sets a currency, billing period and pricing model. One plan, many prices.
  • Groups organize, families constrain. If you used Chargebee or Maxio product families: our group is the same shelf, without the walls. A plan change is never blocked by a group boundary, and an add-on is never scoped to one group. Which add-ons go with which plans is its own explicit setting on each add-on.
  • Prices never change under a customer. Once a price has been created, its amount and model are fixed. You replace it instead. Existing subscribers keep the old price (grandfathering) until you deliberately migrate them, with a preview of who's affected.
  • Every amount shows its math. Any computed amount (an invoice line, a proration, a preview) carries a calculation trace. Click "Show calculation" to see exactly how it was produced.

On import

When you import a catalog, family names from Chargebee or Maxio land in the group field, so your catalog arrives pre-organized. Because groups don't constrain anything, imported family rules relax rather than break. Check each add-on's compatible-plans list if you relied on family scoping.