Skip to main content
The Stores list is every merchant store that has installed your app: the CRM view of your customer base. Nothing is imported: records are built from Meridian’s mirror of Shopify Partner events, so installs, uninstalls and plan changes appear as they happen.

The list

MRR is the same figure Analytics adds up for the whole app, at the store level: the monthly amount of the store’s current subscription plus the usage charges billed to it over the last 30 full days (today is left out until it ends), while the store has a live subscription. When Shopify refunds a usage charge, the refund comes off MRR from the day of the refund: a partial refund takes off the refunded share and a full refund the whole charge, and the days before the refund keep the charge. Refunds come from your app’s billing transactions, so they need the View financials permission and reach MRR after the daily transaction sync. An annual plan counts at a twelfth of its price, so a $499 yearly plan is $41.58 of MRR. Meridian takes how often a plan bills from Shopify: from your app’s billing transactions (with the View financials permission), from the subscription itself when your app’s subscription webhooks reach Meridian, or from the Plan Builder when the plan was subscribed through it. A subscription Shopify has said nothing about yet falls back to its name, and counts as annual when the name says so (“Annual”, “Yearly”, “per year”, “/yr” or “12 months”). One-time charges are not recurring, so they stay out of MRR and count only in lifetime revenue. A store that is frozen, cancelled or uninstalled stops contributing straight away, its recent usage included, and so does a store billing usage with no subscription. A store in its free trial shows its plan’s price here, while Analytics leaves it out of MRR until the trial ends. A test charge on a live store (a test usage charge, say) is left out of its MRR, as Analytics leaves it out. A test store shows its own test subscription, so you can see what it is on. Added up across all your live stores, the column matches the MRR on the Analytics overview with trials included. Plan is the store’s current subscription plan. An installed store with no running subscription reads Free when Meridian knows its last subscription was cancelled. If no cancellation is known, it keeps the last subscription’s name. Frozen and uninstalled stores keep the name of the last plan they subscribed to. A store that never subscribed reads Free, even if it paid usage or one-time charges. The plan filter follows the same rule. Lifetime revenue is everything the store has been billed: every subscription cycle, usage charge and one-time charge, less refunds (adjustments and credits), before Shopify’s share. Meridian reads it from your app’s billing transactions in the Partner API, which Shopify only shares when your Partner connection has the View financials permission. Until those transactions have synced once, lifetime revenue falls back to the store’s Partner charge events, which record when a subscription starts but not its renewals, so a long-running plan counts there for its first cycle only. Transactions sync once a day, so a charge billed today reaches lifetime revenue by tomorrow. Test charges are never billed, so they are left out on both sources: a test store has no lifetime revenue, and a test charge on a live store adds nothing to it. This is billed history, not the predicted LTV on the Analytics overview, which divides ARPU by churn. Amounts show in the store’s own billing currency, and nothing is converted: sorting by MRR or lifetime revenue compares the raw amounts, so 29 EUR ranks below 30 USD. Search by store name or domain, and filter by status, plan, or mode. By default the list shows your newest stores first, by install date. Click the Store, MRR, or Lifetime revenue column header to sort instead: the first click ranks stores by that column (highest MRR first is one click), the second reverses it, and the third returns to the newest-first default. Sorting applies to the whole list, not just the visible page, and survives search and filter changes. The search, filters, page and sort all live in the URL, so a view can be shared. Open any row for its profile. Going back from a profile with the browser’s Back button returns to the list as you left it.

The numbers above it

Active subscriptions, stores on trial, frozen stores, churned stores, live stores and test stores, each with its share of the total. That’s the quickest read on whether the base is growing and how much of it is real traffic rather than your own development stores. Every store carries exactly one of the first four labels. Trial means the store is installed and its active subscription is still inside its free trial, and it takes precedence over Active, so a trialist is never counted twice. Frozen means Shopify paused the store’s subscription, usually after a failed payment. It is not a trial, whatever the store’s subscription rows say. Whether a store is installed, frozen or churned follows the newest thing Meridian knows about it: its install and uninstall events from Shopify, a charge the merchant approved (only an installed app can ask for one), and the install or uninstall your app reported to Meridian, which arrives at once while the Partner events can take an hour or more. So a store that uninstalled, came back and subscribed reads Active as soon as it is back, even before Shopify’s reinstall event reaches the mirror. A plan change is never a churn: switching plans keeps the store Active, and paid plan changes count as upgrades or downgrades in Analytics.

Live and test stores

One rule decides what is test, and every surface reads it: Analytics, Stores, Transactions, Trials, segments, email variables and the Report Builder. A store is a test store when any of these holds:
  • it is a development store (Meridian asks Shopify when your app identifies the store), or you installed it with meridian dev;
  • its Plan Builder subscriptions were recorded as tests and it has nothing real: no subscription that is not a test and no real charge;
  • it has charges and every one of them is a Shopify test charge.
A charge is test when Shopify flagged it as a test charge, or when its store is a test store. The rule is per store: one test charge on a live paying store (a test usage or one-time charge, say) leaves the store Live, and only that charge is left out of its MRR and lifetime revenue. The same goes for an old test subscription on a store that later subscribed for real: the store stays Live and only the test subscription is left out. Test stores are counted separately everywhere, and Analytics, the Report Builder and the list’s mode filter can bring them back. That matters, because a handful of test subscriptions on a young app will otherwise dominate your revenue metrics. Analytics reads the rule from the history it compiles, so a store Shopify reports as a development store after its first events moves to test when Meridian next rebuilds that store’s history, which happens at its next Shopify Partner event.

It runs on the Shopify connection

Stores and Analytics read from your app’s Shopify connection. Three states worth knowing:
  • Never connected: the screens are blocked with an explanation and a link to app settings, because there’s nothing to show yet.
  • Connected, history still importing: right after you connect, Meridian imports your app’s events from the Shopify Partner API, newest first. The pages show an Importing your Shopify history card with the share already imported, measured from your app’s first event to today. Before the first events arrive the figures read zero; your most recent months appear within minutes, and older months fill in over the following hours (an app with millions of events can take a day). Until the card goes away, figures that reach far back, MRR and LTV especially, can read lower than they are. Nothing to do: the import picks up where it stopped if it is interrupted, and the card disappears when it reaches your first event.
  • Disconnected after syncing: the data you already have stays visible, marked as frozen with the date it stopped syncing. Reconnect to resume.

What to do from here

  • Group stores by rules with Segments for targeting and reporting.
  • Record your own attributes on them with Custom fields.
  • Reach them with an automation: the CRM is where its recipients come from.
“Stores”, “merchants” and “customers” all mean the same thing across Meridian: a Shopify store that uses your app.
Last modified on November 15, 2026