✅ Best Practices ✅
- Search first before creating a new post. A similar post may already exist for you to “like” or comment on, keeping related feedback in one place instead of across many posts.
- Stick to what you know. Avoid making broad generalizations and share your own personal experience.
- Write a descriptive title. Keep it succinct while including key information.
- Explain the problem. Context is key! Share what the pain point is and describe a real-life scenario.
- List any workarounds you’ve used. It could be a partner app, a manual process, or existing Square functionality that needs optimizing.
- Propose a solution. Let us know the new feature or upgrade you would want to see developed in the product.
- Predict some benefits. It’s helpful to share what some positive results might be, like how much time or money will be saved, etc.
- Include relevant attachments. Share screenshots, a short video, or another attachment to supplement your request when possible.
🤔 Frequently Asked Questions 🤔
What happens after I submit my request?
We share the request directly with the people building our products. After we’ve talked to the responsible team, we return to the post to add comments and update the status as the idea moves through the development process. You’ll automatically receive email notifications whenever there is an update to the post so you can stay up-to-date on changes.
| STATUS | DEFINITION |
| Open | The feature request is open for votes and comments. |
| Not Right Now | The feature request has been reviewed by the Product team. The idea is not currently on our roadmap, but may be revisited in the future. The idea is still open for votes and comments. |
| On Roadmap | The feature is on our roadmap, however a release date is not set. The status will be updated when the feature is ready for delivery. |
| Delivered | The feature request has been implemented and is fully available in the Square product. |
| Closed | The feature request has been reviewed and has been determined to be duplicate, spam, inactive, or does not meet our guidelines for ideas. Closed requests are not open for comments or votes. |
Can I see an example of a well written feature request?
Of course! Here’s a great example:
How long does it take for new features to be developed?
Even the most meticulously planned features take time to build, and how long it takes depends on a multitude of factors. We may give a projected release date when we respond to your post if we can project which quarter of the year it comes out. Additionally, you can find upcoming opportunities to test new features in Feedback Discussions.
Why was my feature request rejected?
There is no one-size-fits-all reason for rejections. Sometimes the idea requires more planning and scoping. Other times there is a viable workaround or partner app. When able, we will share with you why the idea wasn’t accepted.
Can I see an example of a rejected feature request?
Absolutely! Here is an example:
What can I do if I still have questions?
Please don’t hesitate to ask any questions you have! The best way to do that is simply comment on this article so a Square Community team member can help.
Thank you for reviewing this article. Every feature request you share helps shape the future of Square and makes life easier for fellow business owners. We’ll continue working on your behalf here at Square, while you keep brainstorming and sharing new ideas. And as always, leave a comment if there is anything we can help with!
