Here in the Community, we get a lot of feedback about what’s working well—in addition to things we could improve. It is incredibly insightful for us to hear firsthand what’s not working for you and how we can fix it. When we receive feature requests in the Square Community, a few different things happen behind the scenes. We thought we’d pull back the curtain and share some of our processes with you.
The Life of a Feature Request
Customer Advocacy — The first thing we do internally is share your request with the people building our products. From data-centric approaches like tracking the request in our internal databases, to more qualitative methods like the community moderators talking directly with the appropriate product team, we make sure your feedback and ideas get to the right person.
Look for an Alternative — We always try to provide a workaround when it makes sense. Even if our products don’t do exactly what you need them to, we want to help you get closer to your goal (see an example of a work-around in this thread). Many times, we’ve heard the request before and have an alternative solution in mind. When we don’t know of a great workaround, we turn to the community to get advice from other sellers.
Share a Resolution — The best days for us (and we hope for you, too!) are when we get to share with the community that a feature request has been built into the product. We’ve been able to do that several times, including this thread about incremental improvements we're continuing to make for Square Online deliveries. If you’re interested in seeing a resolution, make sure to subscribe to the thread so you’re notified if we update it.
But what if there isn’t a resolution?
Even the best feature requests take time for our team to build. Our Product Managers take a lot of things into consideration when developing new features and addressing limitations of current features. Customer feedback is one huge piece of the puzzle that impacts prioritization, but it’s not the only piece.
In cases where a resolution is not yet available, we continue to take our jobs as customer advocates seriously. We’ll keep sharing your stories internally and funneling your feedback to our developers. If we can’t prioritize a feature, we also give feedback to our Partnerships team so they can look for great opportunities to partner with other companies who specialize in the features you need.
If you would like to get involved in a deeper level with the feedback process, be sure to join the Beta Community — a space where you get access to newly designed features before everyone else!
Sometimes we don’t have an update for weeks or months. In those cases, thank you for bearing with us. We know it can be frustrating, but we are continuing to work on your behalf. As soon as we have an update, we’ll post to let everyone know.
Thanks again for sharing your feedback with us!
How to submit a feature request in the Community
Note: The steps below may vary slightly as we work to improve the Community.
Sign in at sellercommunity.com and click Ideate from the homepage.
Use the search bar search to see if your request exists already - or browse existing requests by product name.
Click Submit a Request to create a new feature request.
If your request exists already, click the star icon to like the request. Or, click on the title of the request – from there you can click Subscribe to follow the progress of the request. You can also add a comment to share how the request would benefit you.
That’s it! The status of your request will be changed overtime, e.g. from ‘New’ to ‘Needs Beta Testers’, or it may be merged into another matching request.
Examples
Here's a look at the current feature requests for the Square Point of Sale app.
Here's an example of a new feature request:
We're looking forward to receiving your feature requests!
Read more
