> ## 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 subscription transactions ledger

> The transactions ledger of Shopify subscription events (activated, canceled, expired, declined, frozen) with amounts, filters, sorting, and live versus test.

Transactions are every subscription event Shopify has reported for your app: activations, cancellations, expirations, declines and freezes. It's the ledger behind your revenue numbers, one row per event rather than one row per store.

## The events

| Event | What happened |
| - | - |
| **Activated** | A subscription started: new revenue |
| **Canceled** | A merchant cancelled: revenue lost |
| **Expired** | A trial ended without converting |
| **Declined** | A payment failed |
| **Frozen** | Billing was paused, usually a failed card |

Each of these has its own KPI above the table, with the **amount** attached: activations show revenue added, cancellations and expirations show revenue lost, declines and freezes show the amount at risk. That's the difference between "we lost four subscriptions" and "we lost four subscriptions worth \$340".

## The table

Date, shop, event, plan, mode and amount, newest first. Search by shop name or domain, and filter by event type, plan, or mode. The **date** and **amount** headers sort the whole ledger: one click on amount surfaces the largest transactions first, a second reverses it, a third returns to newest first. The sort survives search and filter changes and lives in the URL, so a sorted view can be shared.

## Live and test

A transaction is test when Shopify flagged it as a test charge or its store is a test store (see [Live and test stores](https://help.the-meridian.ai/stores.md#live-and-test-stores)). Test transactions are counted separately. The live-events KPI tells you how many test events sit behind it. Filter to **live** when you're reading revenue, and to **test** when you're checking your own integration.

## How it relates to everything else

* The same events drive [Analytics](https://help.the-meridian.ai/crm-analytics.md): this is the row-level view of what those metrics aggregate.
* Each store's own transactions appear on its [profile](https://help.the-meridian.ai/store-profile.md), with its full billing history.
* Activations, cancellations and freezes each fire an [automation trigger](https://help.the-meridian.ai/subscription-activated.md), so a flow can react the moment one lands.


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