> For the complete documentation index, see [llms.txt](https://docs.roadmap.so/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.roadmap.so/subscriptions/managing-subscriptions/filtering-the-subscriptions-list.md). # Filtering the Subscriptions list Every filter type on the Subscriptions list view, what it matches, and how to combine filters to find the contracts you want. The Subscriptions list view supports filtering by seven dimensions on top of the status tabs. Filters combine — every active filter must match for a contract to appear. This article covers each filter type and the most useful combinations. #### Where to filter Open Subscriptions → Manage Subscriptions. Under the search bar you'll see the active filters as chips (e.g., Status: Active) and an Add filter + button to add more. Click Add filter + to open the filter type picker. Choose the filter you want, set its value, and the list updates immediately. To remove a filter, click the × on its chip. Clear all removes every filter. #### Status tabs vs filters The tabs across the top (Active / Failing / Paused / Failed / Cancelled) are filters too — they're shortcuts for Status: . Picking a tab is the same as adding a Status filter; you'll see the tab selection reflected in the filter chips. Use tabs for the most-common slices, Add filter + for everything else. #### The seven filter types **Email** Match contracts by the customer's email address. Useful when you want to find every subscription a single customer has. Tip: this is exact-match (or partial-match within a domain). For free-text fuzzy search, use the search bar at the top instead. **Last Payment Status** The result of the most recent billing attempt for each contract. Common values: Successful, Failed. Use this to find contracts that are mid-dunning (Last Payment Status: Failed while Status: Active) — the same set as the Failing tab — or to confirm contracts billed cleanly in your last cycle (Last Payment Status: Successful). **Next Billing** Filter by when the contract is next due to bill. Useful for capacity planning ("who's billing in the next 7 days?") and for proactive outreach ("send a reminder to everyone billing tomorrow"). The list-view default grouping (Tomorrow / In 3 days / In 7 days / Specific date) is essentially a visual version of this filter. **Payment Method** Filter by the type of payment method on the contract — credit card, ShopPay, etc. Use this when troubleshooting payment-method-specific issues, or when running a recovery push targeted at one payment type. **Products** Filter by which products are on the contract. Useful for cohort reporting ("how many subscribers do I have on the limited-edition variant?") or for change management ("everyone subscribed to product X needs notice that we're discontinuing it"). **Country** Filter by the customer's shipping country. Use for region-specific outreach (delivery delay in a country, regulatory compliance email, country-specific promotion). **Market** Filter by Shopify Market. Useful in multi-market stores where customers in different markets see different prices, currencies, and products. Pairs well with Country for region-aware reporting. #### Useful filter combinations **"Subscribers due to bill tomorrow on a failing payment method"** Next Billing: Tomorrow + Last Payment Status: Failed — your at-risk renewal cohort. Reach out before the cycle hits. **"Failed contracts on the limited-edition product"** Status: Failed + Products: — the recovery list for a specific product line, useful when running a targeted re-engagement campaign. **"Active subscriptions in the EU using credit cards"** Status: Active + Country: (or use Market) + Payment Method: Credit card — useful for compliance-related comms (e.g., when card-handling rules change in a region). **"Everyone billing in the next 7 days"** Next Billing: In 7 days — your near-term billing forecast. Combine with Status: Active to exclude paused/cancelled. #### How filters interact with bulk actions The Actions ▾ menu reads from the filtered list. The count next to each action ("Email 6 subscribers") tells you exactly how many contracts will be affected. Always verify your filters before bulk actions — particularly Update payment method, which creates a $1 charge per contract. See Working with subscriptions in bulk. #### How filters interact with the search bar The search bar at the top searches by contract ID, customer name, or email. Search and filters combine — search narrows the filtered set further. Use search for "find one specific thing", filters for "find a cohort". #### Common scenarios **"I filtered by Status: Active but I see contracts I expected to be in dunning"** Contracts in dunning are still Active under the hood — they just also appear in the Failing tab. If you want active contracts that aren't currently failing, combine Status: Active + Last Payment Status: Successful. **"My filter combination shows zero contracts but I know there should be matches"** Check for typos in the filter value (especially country names and product titles). Filters are case-insensitive but require exact substring matches for text-based fields. **"I want a saved filter view I can come back to"** Saved views aren't currently a feature — every list-view session starts fresh. Bookmark the URL after applying filters; the URL encodes the filter state, so the bookmark will reload the same view. #### Related guides * The Manage Subscriptions admin: a tour * Working with subscriptions in bulk * Subscription statuses explained --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.roadmap.so/subscriptions/managing-subscriptions/filtering-the-subscriptions-list.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.