Have an idea for something Composerie should do? This guide shows you how to send a feature request, what to include so we can act on it, and how we weigh the ideas you send. It is for any merchant who wants to shape where the product goes next.
A feature request is a suggestion for new behavior or an improvement to something that already exists. It is different from a support request, which is for a problem you need fixed. If something is broken, head to contact support instead.
How to send a feature request
The fastest way to get your idea to us is the same channel as support. You can write from inside the dashboard, which attaches your store details to the message, or email us directly.
Open the help menu in the dashboard
Open your Composerie dashboard and find the help menu. Choose Contact support to start a message. Starting here attaches your store details, so we have the context without asking for it.
Describe the problem, not only the solution
Tell us the problem you are trying to solve, not only the fix you have in mind. The solution you picture is useful, but the underlying need helps us find the best answer, which is sometimes different from the one you expected.
Add how often it comes up and your current workaround
Tell us how often the situation happens and what you do today to get around it. A request that comes up every order with a clumsy workaround is easy for us to weigh. Send the message, and you get a confirmation by email.
What makes a request we can act on
The clearer the request, the easier it is for us to weigh and build. A few habits make a real difference.
Be specific. Name the screen, the field type, or the add-on control you have in mind. Composerie supports a defined set of personalization field types, such as text, image, color, font, dropdown, number, and date, and a defined set of add-on display types, such as checkbox, radio, button group, dropdown, and image swatch. A request like “I want a date field that blocks past dates” or “I want an image swatch add-on for frame colors” is concrete and easy for us to review against what exists today. If you are new to these, personalization form fields and add-ons explain them.
Explain the outcome you want. Tell us what changes for your shoppers or your team if we build it. Fewer support emails, faster setup, a higher order value: the outcome tells us why the request matters.
Keep your expectations honest. We cannot promise a date for any request. Clear, frequent requests carry weight, and the more merchants who hit the same need, the higher it rises.
Send bugs to the right place. If something does not work the way it should, that is a bug, not a feature. Report it through contact support so we can fix it fast. The common issues guide covers the frequent ones.
How we use your ideas
We read every feature request that comes in. We group similar requests together, so we can see how many merchants share a need. That count is one of the biggest factors in what we build next.
We will not build everything that is requested, and we will not always say yes. But a request that is specific, ties to a clear outcome, and comes up for many merchants has the best chance of shaping the roadmap.
Frequently asked questions
Will you build everything requested?
No, but we read every request and weigh how many merchants it helps. Specific, frequent ideas carry the most weight.
Can I request a new personalization field type?
Yes. Tell us the field you want and the use case, and describe the outcome you want for your shoppers. Concrete requests are easiest for us to review.
Is this where I report a bug?
No. Use contact support for problems so we can fix them fast. Feature requests are for new behavior or improvements.
Next
Need help with something that is not working? Head to contact support.