> ## Documentation Index
> Fetch the complete documentation index at: https://help.the-meridian.ai/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> These are the public docs of Meridian for Shopify apps: hosting, billing (Plan Builder and the @the-meridian/sdk package), CRM, emails and automations for Shopify app developers.
> Start with these pages: Meridian MCP (https://help.the-meridian.ai/mcp-server.md) to connect a coding agent, AI coding agents (https://help.the-meridian.ai/ai-agents.md) for the agent skill, SDK quickstart (https://help.the-meridian.ai/sdk-quickstart.md), Running your app with the CLI (https://help.the-meridian.ai/cli-dev.md), Deployment (https://help.the-meridian.ai/deployment.md), and Errors (https://help.the-meridian.ai/errors.md) to look up an error code or message.
> Fetch one page at a time as Markdown (the page URL followed by .md), using the index in https://help.the-meridian.ai/llms.txt. llms-full.txt holds every page in one file of about 900 KB, so avoid loading it whole.
> With Meridian MCP connected, search these docs with docs_search and docs_get, and read live facts (feature and event keys, plan ids, environments, deployments, logs) from the MCP tools instead of guessing them.

# Shopify app billing with Plan Builder

> Introduction to the Plan Builder: recurring and usage-based Shopify billing for your app, how it compares to Shopify's own billing options, and where to start.

Public apps need a way to monetize, and Shopify offers several approaches depending on your strategy. The Plan Builder is Meridian's: define your pricing once, and let the SDK handle everything a merchant sees and everything Shopify needs.

## Recurring charges

Define plans, include features in each, and let the merchant choose. Bill monthly or yearly, regardless of how much they use the app. Upgrades start at once, while downgrades and cancellations wait for the end of the period the merchant has paid for, and can be undone until then. See [Plan changes](https://help.the-meridian.ai/plan-changes.md).

## Usage-based charges

Bill on events instead of, or alongside, a recurring charge. Define events, track them, and invoice the merchant continuously based on usage.

## How does Shopify handle it?

| Approach | What you get | What's missing |
| - | - | - |
| **Shopify App Pricing** | Recurring and usage-based plans managed through Shopify's interface, easy to drop in | No feature gating, no account page, no automations around it |
| **Billing SDK** | React Router is Shopify's base template; if you use it, an SDK is already there to talk to the billing API | Easier than the raw API, but the surrounding capabilities are still yours to build |
| **Billing API** | Everything is possible | Everything takes time |

## What the Plan Builder is

One place to define your monetization, and one integration to expose it:

* **[Plans](https://help.the-meridian.ai/create-a-plan.md)**: the tiers you sell, with a monthly price, an optional [annual price](https://help.the-meridian.ai/billing-interval.md), and an optional [free trial](https://help.the-meridian.ai/free-trial.md).
* **[Features](https://help.the-meridian.ai/plan-features.md)**: what each plan includes, boolean or a numeric limit, gated at runtime by key.
* **[Events](https://help.the-meridian.ai/usage-events.md)**: what you meter. The catalog is app-level (under **Usage**) and shared; a plan adds the terms: included quantity, overage rate, cap.
* **[Discounts](https://help.the-meridian.ai/discounts.md)**: percentage or fixed-amount, code-based or automatic.

Your app renders the [pricing page](https://help.the-meridian.ai/plans.md) and [account page](https://help.the-meridian.ai/account.md) from that definition through the [SDK](https://help.the-meridian.ai/sdk-authentication.md), and Meridian does the Shopify Billing handshake, so you write almost no billing code, and none of the recurring-charge or usage-charge API calls.

## The path through it

1. Define your [features](https://help.the-meridian.ai/plan-features.md), and your [events](https://help.the-meridian.ai/usage-events.md) under **Usage** if you want to bill on usage.
2. [Create a plan](https://help.the-meridian.ai/create-a-plan.md) that includes them, as a draft.
3. [Activate it](https://help.the-meridian.ai/publishing-plans.md) so merchants can subscribe. This is the step with prerequisites.
4. Gate your app on the feature keys, and report usage on the event keys, through the SDK.

> [!NOTE]
>
> A plan starts as a draft. Only active versions are offered to new subscribers. Plans with live non-test subscribers have [protected terms](https://help.the-meridian.ai/create-a-plan.md#editing-a-plan-with-subscribers): favorable changes apply in place, while other changes open a **Save as version** dialog from the latest version. The new version inherits its status, and an active previous version switches to draft. Its subscribers keep their terms and see their **Current plan** with a **No longer offered** badge. See [Visibility](https://help.the-meridian.ai/plan-visibility.md).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.