Describe the store, audience, and decision. Makeform turns your brief into a focused Shopify questionnaire for agency discovery, product research, customer feedback, or post-purchase follow-up.
Route responses to Slack, Google Sheets, and Zapier.
Sample prompts for the builder
Choose a starting point, tailor the prompt, and send it to the builder. The example structure is editable.
Audience
Shopify merchants preparing for a redesign or build
Format
Multi-step client requirements questionnaire
Prompt size
317 chars
Example questionnaire structure
Multi-step client requirements questionnaire
Store URL, markets, and product catalog size
What should this Shopify project improve?
Are you migrating from another platform?
Apps, integrations, and sales channels
Launch date, budget, and brand assets
Suggested routing tags
Agency discovery
Product feedback
Follow-up needed
Name the decision responses will influence. A launch survey and agency discovery brief need different questions.
Step 1
Define
audience, moment, and decision
Step 2
Generate
questions, answer types, and branches
Step 3
Share
link, embed, or customer follow-up
Step 4
Act
route issues and review patterns
Questions with a purpose
Connect each answer to a build requirement, product choice, customer follow-up, or storefront improvement.
Show migration fields to migrating merchants and issue follow-ups after low customer scores.
Structure catalog, market, integration, budget, timing, content, and ownership requirements.
Send urgent feedback, client requirements, and research responses to their owners.
Four useful moments
Start with the moment closest to your current work, then change the language, choices, and routing to match the store.
Scope the catalog, apps, markets, content, budget, timeline, and decision-makers.
Test customer problems, priorities, variants, pricing, and buying objections.
Measure product and delivery quality, then follow up on reported issues.
Find friction in navigation, product content, shipping, or checkout.
Build the questionnaire
Provide context, then edit the result around your team's decision.
Say who responds and whether answers shape a proposal, product, store experience, or follow-up.
Use the store's markets, categories, channels, apps, fulfillment methods, and issue types.
Ask migration details only when relevant and request explanations after low ratings.
Publish a link or embed, then route responses to the responsible workflow.
Choose the right starting point
All three can collect information, but they create very different work when responses need to be compared, routed, and turned into decisions.
Field guide
Use these six sections as a menu. Keep only the fields that help your agency or store team understand the respondent and make the next decision.
Respondent context
Record the respondent's role, authority, purchase status, or familiarity so their answers have useful context.
Store baseline
Capture the technical and commercial context that reveals project scope without requiring an unstructured store history.
Goals and priorities
Ask respondents to rank priorities, give evidence, and name the decision that will follow.
Experience feedback
Pair a focused rating with an open follow-up that explains what happened at that touchpoint.
Constraints and ownership
Uncover delivery constraints, decision-makers, available materials, and who owns the next response.
Evidence and attachments
Request links or uploads only when a prepared team member will review and use them.
Related tools
Use a more specialized starting point when the work is primarily client intake, market research, checkout, or customer feedback.
Collect new client context, goals, ownership, timing, and project materials before discovery.
Open toolStudy audience needs, buying habits, alternatives, preferences, and product opportunities.
Open toolGather focused feedback and explanations from customers after key store interactions.
Open toolAsk customers about product quality, fit, usage, expectations, and improvement ideas.
Open toolCreate a structured checkout-oriented form for ecommerce order details.
Open toolLearn what subscribers want to receive and how their interests are changing.
Open toolFAQ
Practical answers for store owners and ecommerce agencies planning requirements or feedback collection.
It is a structured set of questions about a Shopify store, project, product, or customer experience. Agencies use one to scope work; store owners use one for research, website feedback, or post-order follow-up.
Ask about the store, markets, catalog, theme, apps, integrations, channels, goals, content, timeline, budget, and approvals. Show migration questions only when applicable, and request project assets separately.
Use the shortest set that supports the decision. Post-purchase feedback may cover the order, product, delivery, and one comment. Product research may need segmentation and branching. Remove questions your team will not use.
Yes. Conditional logic can show migration fields, reveal details after a low score, or request contact information only when someone wants a reply. Each respondent sees a more relevant path.
You can publish the questionnaire and use Makeform's available sharing or embedding options. Test it on mobile and explain why you are asking for feedback.
Ask for the order or product, the problem, and whether the customer wants a response. Route follow-ups to their owner, and keep support requests separate from aggregate research.
Yes. Makeform supports unlimited free forms and responses, so you can generate, edit, publish, and collect responses without a free-plan response cap. The paid tier is for removing the Makeform badge.
Organize responses for agency discovery, research, customer experience, or operations. Fields such as project type, score, follow-up request, or product category make routing clearer.
Ask only what your Shopify decision needs.
