> If you are setting up, configuring, or answering questions about Schematic, connect the
> Schematic MCP server before working from these pages. It reads and writes plans, features,
> entitlements, and overrides against the real account, so what you report and what you build
> match what actually exists.
>
> The server is at https://api.schematichq.com/mcp
>
> From Claude, ChatGPT, or another chat assistant, add it as a custom connector:
> https://docs.schematichq.com/working-with-ai
>
> From a coding assistant such as Claude Code, Codex, or Cursor:
> https://docs.schematichq.com/building-with-ai
>
> For clean Markdown of any page, append `.md` to the page URL. For a complete page index,
> see https://docs.schematichq.com/llms.txt

# Configuring the Catalog

> Set the initial, fallback, and trial expiry plans, and choose which plans and add-ons appear in checkout.

The Configuration tab in the Catalog serves two purposes:

1. To define subscription lifecycle rules when subscriptions change
2. To define what plans or add-ons should be user-facing and accessible via Schematic Components

Live Plans, Live Add-ons, and Plan Change Rules are only relevant if you are using Schematic with Stripe. In that case, selected plans and add-ons will appear in Schematic Components and users will be able to manage their subscription directly. In all other cases, that configuration can be skipped and user-facing components will simply be read only with no option to manage subscriptions.

![](/_fern-img/07791e0b23345ec62f412e30da107d8a4ef259a6796b6667ebb759b90e3c345f.webp)

## Options

### Initial Plan

The plan assigned to new companies when they are created. This plan determines how new customers begin their journey with your service.

You can select a price for this initial plan, in which case a Stripe subscription will be provisioned for this customer.

Your initial plan selections must *not* require the customer to have a payment method on file, meaning any of the following are valid:

* Selecting a plan that is not associated with billing
* Selecting a plan and price that is free, with no monetized entitlements (e.g. pay-as-you-go, tiered pricing, or pay-in-advance)
* Selecting a plan with a trialable paid plan, as long as the trial will expire at the end of the trial term

> **Info**
>
> If you want every new company to have a corresponding Stripe customer record from the start, configure the Initial Plan to use a plan with a \*\*$0 price**. This causes Schematic to provision a Stripe customer and a $0 subscription for each new company automatically. Without this, Stripe customers are only created when a company subscribes to a Stripe-enabled plan. Companies on free plans with no Stripe price will not appear in Stripe.

### Fallback Plan

The plan assigned to any company that does not have another base plan. This replaces the deprecated Default Plan functionality, and allows you to specify a default set of entitlements.

These plans cannot be linked to a billing product (even a free plan).

**When Applied:**
Companies are automatically moved to this plan when:

* Their subscription becomes inactive (unpaid, cancelled)
* Their trait-based targeting becomes inactive

### Trial Expiry Plan

The plan companies are moved to when their trial period expires.

**Requirements:**

* Must not require a payment method
* Must be either:
  * A non-billing-linked plan, OR
  * A plan with a free price
* Cannot be a trialable plan (companies can't go onto a second trial)

### Live Plans

The plans that your end users can choose to downgrade from or upgrade to. If enabled, each plan included in Live Plans will appear as an option in the checkout flow.

Live Plans always surface each plan's **latest** published version. Companies already on a prior version stay there until you [migrate them](/catalog/plans#plan-version-migrations). The same applies to the Initial, Fallback, and Trial Expiry plans below, which resolve to the plan's latest published version.

Companies in Schematic may be assigned plans that are not included here, but there will be no option to independently subscribe to them using Schematic Components.

### Custom Plans

Often, an enterprise plan will have custom pricing that cannot easily be displayed. In these cases, you can mark a plan as "Custom" and then provide a message like "Talk to us" to display instead of a price.

![custom plans](/_fern-img/416a9229a4a8f692c8e236186f3222a0dc3741d86ed608b32eb3c5a014a3aec6.webp)
![custom plans 2](/_fern-img/6eba34ff5706a305b2311bf486400814fc765694e9ad49be9a94d56e0a8f5f7e.webp)

> **Info**
>
> Custom plans are typically billed by having Stripe send the customer an invoice to pay. If those invoice emails aren't arriving, see [My customer didn't receive an invoice email](/integrations/stripe-troubleshooting#my-customer-didnt-receive-an-invoice-email). The most common cause is testing in a Stripe sandbox, which doesn't send customer emails by default.

### Live Add-ons

The add-ons that your end users can select. If enabled, each add-on included in Live Add-ons will appear as an option in the checkout flow. Similar to Live Plans, Live Add-ons will always show the latest published version in checkout.

Companies in Schematic may be assigned add-ons that are not included here, but there will be no option to independently subscribe to them using Schematic Components.

> **Info**
>
> Live Add-ons are limited to features that can be turned on or turned off (Boolean entitlements), but metered add-ons are coming soon.

### Trial Rules

The default trial behavior that will apply to trials when configured at the plan level.

**Trial Eligibility** sets who Schematic offers a trial to: one trial per company, which is the default, or one trial per plan. See [Trial eligibility](/catalog/trials#trial-eligibility) for what each rule counts and how to choose between them.

### Plan Change Rules

The rules Schematic will validate subscription changes against (e.g. upgrade rules, downgrade rules).

## **Configuring the Catalog**

1. Navigate to **Products > Configuration**
2. Choose a default plan that all companies will be assigned if they do not currently have a subscription (optional)
3. Choose “Live Plans” and “Live Add-ons”
4. Save changes

> **Info**
>
> Plans and add-ons must be associated with Stripe Products to be added to Live Plans or Live Add-ons.

![](/_fern-img/c35f0cb1f5475c5d6bb955f56d2d035666d0914686b6d595e784ef6747ac9feb.webp)

Trials Rules can be modified to require a credit card to start a trial. At the end of the trial, companies will automatically convert into the corresponding paid plan.

![](/_fern-img/22c9710bfa11ee2e252eb99fb8e7e464cd9c197191e68f6ee831a9ad393b760b.webp)

Currently, Plan Change Rules cannot be modified; however, we will be introducing more optionality here in the future.

![](/_fern-img/08c2e556682bba847c517014e3e853b31ca2fbc07224ef70b90d7163a7b3f698.webp)

### Common Pricing Table Patterns

A useful pattern is to lay out your pricing table where each plan includes the features of the previous plan plus some additional features. This is common in 3-tier ("Good, Better, Best") pricing tables often used by SaaS companies. It usually looks like this:

| Good      | Better                    | Best                        |
| --------- | ------------------------- | --------------------------- |
|           | Everything in Good, plus: | Everything in Better, plus: |
| Feature A | Feature D                 | Feature F                   |
| Feature B | Feature E                 | Feature G                   |
| Feature C | Feature F                 | Feature H                   |

This can be configured in the pricing table component by enabling the `plans.showInclusionText` option. For more details, see the [Pricing Table documentation](/components/pricing-table#styling-options-for-the-pricing-table).

> Set the initial, fallback, and trial expiry plans, and choose which plans and add-ons appear in checkout.