For AI agents: a documentation index is available at the root level at /llms.txt and /llms-full.txt. Append /llms.txt to any URL for a page-level index, or .md for the markdown version of any page.
SupportDashboard
Getting StartedAPI ReferenceRoadmapBlog
Getting StartedAPI ReferenceRoadmapBlog
  • Getting Started
    • Overview
    • What is Schematic?
    • Concepts
  • Using Schematic
    • Who Uses Schematic
  • Quickstart
    • Quickstart
    • Account Setup
    • Entitling a Feature
    • Tracking Usage
    • Components
    • Identifying Users
    • Setup the SDK
  • Using Feature Flags
    • Overview
    • Flags
    • Features
    • Tracking Feature Usage
    • Company Overrides
    • Feature Types
  • Building Your Catalog
    • Overview
    • Plans
    • Managing Company Plans
    • Configuring the Catalog
      • Initial Plan
      • Fallback Plan
      • Trial Expiry Plan
      • Live Plans
      • Custom Plans
      • Live Add Ons
      • Trial Rules
      • Plan Change Rules
    • Add Ons
    • Trials
  • AI Tooling
    • For Developers
  • Setting Up Billing
    • Overview
    • Usage Based Billing Models
    • Seat Based Billing Models
    • Credit burndown
  • Using UI Components
    • Overview
  • Developer Resources
    • Concepts
    • Key Management
    • Environments
    • Entity Relationship Diagram
  • Production Readiness
    • Availability
    • Observability & Support
    • Security
  • Integrations
    • Segment Integration
    • Clerk Integration
    • WorkOS Integration
    • Salesforce Integration
    • Hubspot Integration
  • Playbooks
    • Overview
    • Creating a metered feature
    • Backfills and usage corrections
    • Rolling out beta functionality with Flags
    • Handling customer exceptions and feature trials
    • Automatically provision customers using Stripe
    • Build a slack webhook
LogoLogo
SupportDashboard
On this page
  • Options
  • Initial Plan
  • Fallback Plan
  • Trial Expiry Plan
  • Live Plans
  • Custom Plans
  • Live Add Ons
  • Trial Rules
  • Plan Change Rules
  • Configuring the Catalog
  • Common Pricing Table Patterns
Building Your Catalog

Configuring the Catalog

Was this page helpful?
Previous

Add Ons

Next
Built with

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.

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

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 **0price∗∗.ThiscausesSchematictoprovisionaStripecustomeranda0 price**. This causes Schematic to provision a Stripe customer and a 0price∗∗.ThiscausesSchematictoprovisionaStripecustomeranda0 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.

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 custom plans 2

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.

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.

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.

Plan Change Rules

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

Configuring the Catalog

  1. Navigate to Catalog > 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
Plans and add ons must be associated with Stripe Products to be added to Live Plans or Live Add Ons.

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

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

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:

GoodBetterBest
Everything in Good, plus:Everything in Better, plus:
Feature AFeature DFeature F
Feature BFeature EFeature G
Feature CFeature FFeature H

This can be configured in the pricing table component by enabling the plans.showInclusionText option. For more details, see the Pricing Table documentation.