How to Configure Labels, Placeholders, Help Text, and Required Fields
What you will achieve in this guide
Follow this step-by-step documentation to configure custom B2B registration forms, approval workflows, and customer tagging.
Make Shopify registration questions clear with descriptive labels, examples, help text, and required-field settings.
Before you begin
Open the intended form in the builder and identify what the answer will be used for: review only, field mapping, a visibility condition, or an approval rule. Choose the answer type before configuring those dependencies.
Make each question understandable
A label names the requested information, a placeholder shows a short example inside an empty input, and help text explains format or purpose. A required toggle prevents completion without an answer where applicable. A placeholder should never be the only explanation of a question.
Mark questions required only when they are essential to the review or follow-up. For a document request, say what document is acceptable and show the permitted type and size so applicants can correct an error without contacting support.
Set up this workflow
Open the form and expand a field.
Enter a label that names the information requested.
Use the placeholder for a short example where that field supports it.
Add help text explaining format, purpose, or acceptable documents.
Enable Required only when the answer is essential, then save.
Test both an empty answer and a valid answer on the storefront.
Example
Label a required text field Registered business name, use Acme Retail as the placeholder, and explain Enter the legal name used on your business documents in help text.
Expected result
The applicant sees clear guidance and cannot submit with the required answer empty.
Limits and important behavior
- A placeholder does not replace a clear field label.
- Your own field labels and help text can be written in the language you need.
- Avoid marking every optional business detail as required.
Troubleshooting and verification
If applicants misunderstand a required question, add a persistent label and explanatory help text rather than relying on its placeholder. Retest with the field empty and completed. An answer should be required because your review needs it, not simply because a template made it required.
Screenshots to add
Screenshot placeholder: Capture the relevant app screen for “How to Configure Labels, Placeholders, Help Text, and Required Fields” after completing the setup. Show the controls used to open the form and expand a field. Add a second screenshot showing the result of this check: Test both an empty answer and a valid answer on the storefront. Use dummy applicant details and mask any secrets.
Related guides
Was this article helpful?
Your feedback helps us continuously improve our setup guides and documentation.
Thank you for your feedback! Our documentation team reviews all suggestions.