disabled state based on the user’s current product and plan, and handle payments.

/components directory, under a /autumn folder.
Usage
productDetails, which can be used to pass in content that can override the default contents (which are generated from your Autumn products). The example below was used to render the screenshot above.
You can choose which products should be displayed, and what items each card should have. The items array can either take an object with primaryText and secondaryText properties, or a string with the featureId, which will just take the item from Autumn’s default contents.
Scenarios
When you installpricing-table, a @/lib/autumn/pricing-table-content.tsx file is also installed. This file contains the pricing card button texts for each scenario, which you can customize how you want.
/lib/autumn/get-checkout-content.tsx
Build your own
Display a list of the products you offer by fetching your product data from Autumn’s API. This gives you a dynamic, single source of truth for your app’s pricing plans.scenario enum, that can be used to determine its relation to the user’s currenct product.
This can be used to control the button text of each pricing card you display. See our shadcn/ui pricing table texts for an example.
| Scenario | Description |
|---|---|
upgrade | The product is an upgrade to the user’s current product |
downgrade | The product is a downgrade to the user’s current product |
cancel | The product is a free product which would cancel the user’s current subscription |
renew | The product would be a renewal of a product that’s scheduled to downgrade |
scheduled | The product is already scheduled to start at a future date (eg, for downgrades) |
active | The product is already active |

