> ## Knowledge Base Index
> Fetch the complete knowledge base index at: https://supr-bundles-and-subscriptions.crisp.help/sitemap.xml
> Use this file to discover available pages before exploring further.
> Pure-Markdown content can be obtained by appending a '.md' suffix to the content URLs listed in the sitemap (without the trailing slash).

# Requesting a new feature

Missing something in Supr Bundles & Subscriptions? Tell us on the **Feature requests** page in the app. It is a shared board where every store can suggest features, vote for the ideas they want most, and follow each request as our development team reviews and builds it.

| 🔍 To access this page, go to [**Supr Bundles & Subscriptions > Feature requests**](https://admin.shopify.com/apps/super-subscriptions/app/feature-requests) in the app menu.

### Table of contents

* [How the board works](#3-how-the-board-works)
* [Submit a feature request](#3-submit-a-feature-request)
* [Vote and comment on requests](#3-vote-and-comment-on-requests)
* [Writing a good request](#3-writing-a-good-request)
* [Common questions](#3-common-questions)

### How the board works

Requests are grouped in columns that show where each one stands:

* **Open**: new, waiting to be reviewed.
* **Accepted**: we plan to build it.
* **In progress**: we are working on it.
* **Completed**: it is live in the app.
* **Rejected**: we decided not to build it.

Our development team reviews new requests and moves them across the board. The more votes a request has, the easier it is for us to see what matters most to merchants.

Everyone who uses the app sees the same board. Store names are not shown: your own requests carry a **Submitted by you** badge, other merchants' comments appear as **Anonymous**, and replies from our team carry a **Developer** badge.

### Submit a feature request

1. Go to **Feature requests** and click **Create request**.
2. Choose **Feature request** (something new you'd like the app to do) or **Bug report** (something that's not working as expected).
3. Describe it in **Description** and click **Save**.

Each store can submit up to 3 requests. The button shows how many you have left, for example **Create request (2 of 3 left)**. Before creating a new one, check whether someone has already asked for the same thing and vote for it instead.

|| For anything urgent, such as a bug that stops customers from subscribing or checking out, contact support in the live chat rather than only posting it on the board.

### Vote and comment on requests

* Click the **thumbs up** button on a request to vote for it. Click it again to take your vote back.
* Click the **comments** button (or the request itself) to read the comments and add your own with **Add a comment**. Comments are a good place to explain your use case or add details to your own request.

### Writing a good request

* **Say what you want to achieve**, not only the button you imagine. "Customers should be able to switch to a subscription in the cart" tells us more than "add a checkbox".
* **Give an example** from your store: the product, the offer, what your customers ask for.
* **Keep private details out.** Every store can read the board, so never include customer names, emails, order numbers or anything else personal.

### Common questions

* **How do I request a feature?**
  Open **Feature requests** in the app menu, click **Create request**, choose **Feature request**, describe it and click **Save**.
* **How do I track a request I made?**
  Find it on the **Feature requests** board by its **Submitted by you** badge. The column it is in shows its status.
* **Can I edit or delete my request?**
  Not after saving, but you can add details in its comments. Contact support if something needs removing.
* **The Create request button says "Limit reached". What now?**
  Your store has used its requests. Vote for or comment on existing requests, or tell us in the live chat.
* **When will my request be built?**
  We cannot promise dates. Requests with more votes are easier for us to prioritise, and you can see progress when a request moves to **Accepted**, **In progress** or **Completed**.
* **The app doesn't do something I need. Is there a workaround?**
  Often there is. Ask in the live chat or search this helpdesk, and add a feature request so we know you need it.