Keep development stores out of commercial Shopify app reporting.

A store name or domain is not reliable evidence that a merchant is a test account. Marlo does not guess from either. A store remains Unknown and included until Shopify exposes a reliable signal or an authorised workspace member records a verified override.

1. 01Production and Unknown stores remain included
2. 02Development, Test, Staff, Frozen and Other non-commercial stores are excluded
3. 03The customer, subscription, transaction and lifecycle history remain available
4. 04Include excluded customers temporarily restores those records to a report comparison

The connected Partner data exposes a frozen lifecycle status, so Marlo classifies a frozen store from that source automatically. It does not expose Shopify Admin's store-plan field, so Marlo labels other stores Unknown rather than pretending they are production or development stores.

Shopify Admin's Shop.plan.partnerDevelopment is authoritative when the installed app forwards it through Marlo's authenticated ingestion endpoint. A true value maps to Development; a false value maps to Production unless authoritative test or Staff Business evidence takes precedence.

1. 01Open Customers and select the merchant
2. 02Read the effective classification, source value and explanation
3. 03Confirm the store type from an authoritative internal or Shopify source
4. 04Choose an override classification and enter how it was verified
5. 05Save the override and confirm the badge and report inclusion state
6. 06Review Settings → Activity for the classification event

Reset to source removes the override and restores the original classification. The audit event records the source value, previous override, new override, reason and actor.

1. 01Dashboard and named report metrics
2. 02MRR movement, churn, trials and retention cohorts
3. 03Customer and transaction views
4. 04CSV exports
5. 05Read-only MCP customer lists, metrics, reports and comparisons
6. 06Public MRR display values

Direct customer lookup remains available for investigation even when that customer is excluded from aggregate reporting.

1. 01Run one report with Include excluded customers off
2. 02Repeat it with the option on
3. 03Inspect the merchant-level difference
4. 04Confirm currency, app and date scope did not change
5. 05Export the customer table and retain the classification columns with your reconciliation notes