Back to all posts
Blogs
How to Collect Customer Requests for New Products on Shopify
A guide to collecting customer requests for new products on Shopify in a structured way.
4 minutes, 3 seconds
Marketing Manager
Published
Customers requesting a product you do not yet carry often mention it in a support message, a social comment, or a passing email, and without a dedicated place to capture that signal, genuinely useful demand data disappears into scattered channels nobody reviews systematically.
This guide is for merchants who want a dedicated way to collect and organize customer requests for new products, turning informal suggestions into a structured source of demand insight.
Quick Answer
Yes, a dedicated request form captures customer product suggestions in one organized place. Hulk Form Builder lets you build a structured intake capturing what customers want, why, and how urgently, routed to a Google Sheets register or Slack alert, so requests accumulate into genuine demand data instead of scattering across support tickets and social comments.
What This Involves
Collecting new product requests means building a dedicated form asking customers what they want, why they want it, and any relevant detail like price expectation or use case, routed into an organized register so requests accumulate into a reviewable source of demand signal rather than disappearing into scattered, unstructured channels.
Who Needs This
- Merchants wanting structured visibility into customer demand for new products
- Stores currently receiving product requests through scattered channels
- Brands wanting a defensible, data-backed case for future product decisions
- Any business wanting customers to feel heard when suggesting something new
- Teams wanting to prioritize product development based on genuine demand
Why It Matters for Your Business
- Scattered requests across channels are impossible to review systematically
- A structured intake turns informal suggestions into reviewable demand data
- This can inform genuinely data-backed product development decisions
- Customers feel heard when there is a clear, dedicated place to suggest something
- This costs little to set up relative to the insight it can surface over time
- Patterns across many requests reveal demand a single comment would not
How to Collect Customer Requests for New Products on Shopify
Step 1
Start by deciding what information makes a request genuinely useful.
- Decide what to ask, product description, use case, price expectation
- Keep the form short enough that customers actually complete it
- Consider an optional field for how customers would use the product
Step 2: Install and Configure Hulk Form Builder
Install Hulk Form Builder and build the request intake.
- Build the form with the fields that make a request genuinely actionable
- Route submissions to a Google Sheets register for ongoing review
- Add a Slack alert if immediate visibility on new requests is useful
Step 3
Make the form easy for customers to actually find and use.
- Link the form from your site navigation or a dedicated page
- Reference it in support responses when a customer mentions wanting something
- Keep the request path short from mention to actual submission
Step 4
Test the form and its routing before promoting it widely.
- Submit a test request and confirm it lands in the register correctly
- Verify the Slack alert, if used, fires as expected
- Check the form is easy to complete on both desktop and mobile
Step 5
Launch and use the accumulated data to inform decisions.
- Review the register periodically for recurring themes or patterns
- Use genuinely popular requests to inform product development priorities
- Consider following up with requesters when a suggested product actually launches
Examples & Use Cases
Specialty Food Retailer (Food and beverage)
Problem: Customers regularly requested new flavors through scattered support emails that were never reviewed collectively
Setup: Built a dedicated product request form through Hulk Form Builder, routed to a Google Sheets register
Result: Recurring flavor requests became visible as patterns, directly informing the next product development cycle
Home Goods Brand (Home goods)
Problem: Product suggestions arrived through social media comments with no way to track or prioritize them systematically
Setup: Added a request form linked from the site, capturing structured suggestions instead of scattered comments
Result: The brand built a genuine demand pipeline instead of relying on memory of scattered social mentions
See more case studies.
Best Practices
- Keep the request form short enough that customers actually complete it
- Ask for use case detail that makes a request genuinely actionable
- Route submissions to an organized, reviewable register
- Link the form prominently so customers can actually find it
- Reference it in support responses when relevant
- Review the register periodically for recurring patterns
- Follow up with requesters when a suggested product eventually launches
Summary
Customer requests for new products are genuinely valuable demand signal that scatters and disappears without a dedicated, structured place to capture them, and a simple form routed to an organized register turns informal suggestions into reviewable data. The core steps are deciding what information makes a request actionable, building and routing the intake, and reviewing the accumulated data periodically for patterns worth acting on.
If product suggestions are scattered across support tickets and comments, Hulk Form Builder can turn them into a structured demand pipeline.
Frequently asked questions (FAQs)
Scattered requests across support tickets and social comments are impossible to review systematically, while a dedicated form organizes them into reviewable data.
What the customer wants, why, and ideally their use case or price expectation, enough detail to make the request genuinely actionable later.
A Google Sheets register works well for ongoing review, with a Slack alert added if immediate visibility on new requests is useful.
Following up when a suggested product ships can strengthen the customer relationship and encourage future engagement with the request form.
Many merchants find that patterns across accumulated requests provide a genuinely data-backed case for prioritizing certain product development ideas.