Describe your dispensary workflow. Makeform creates an editable intake form with contact, identification, policy, and consent fields tailored to your store.
Route new registrations to Google Sheets, Slack, and Zapier.
Sample prompts for your registration flow
Choose a workflow, adjust its details, and send the editable prompt to the builder.
Audience
First-time adult-use customers registering before checkout
Format
Mobile intake with identification and policy acknowledgment
Prompt size
331 chars
Example form structure
Mobile intake with identification and policy acknowledgment
Customer name, birth date, and contact details
ID type, number, issuer, and expiration
Upload an ID image if requested
Preferred communication method
I acknowledge the store policies
Suggested routing tags
Ready for staff review
Missing ID details
Medical workflow
Ask for the ID expiration date as a separate required field so staff can identify an expired document without reading a photo.
Step 1
Register
customer and contact information
Step 2
Document
ID type, issuer, and expiration
Step 3
Acknowledge
store policies and data use
Step 4
Review
staff verifies details in the required workflow
Purpose-built intake
Structured registration keeps each identification and permission value in its own field, making incomplete submissions easier to spot.
Capture document type, number, issuer, and expiration separately so missing details are visible.
Show credential or caregiver questions only for customers who select the medical path.
Keep store rules, data use, and optional marketing choices in distinct fields.
Flexible dispensary workflows
Change the fields to reflect your jurisdiction, reviewed policies, and store procedure.
Share a link so customers enter profile and document details on their own device.
Use clear field labels, progress, and a final staff-review message at reception.
Route customers to relevant questions without unnecessary medical details.
Separate loyalty, email, and text permissions from required intake.
Build your intake flow
Describe the operation, inspect the generated fields, and publish a consistent workflow.
Specify visit types, locations, policy text, and the fields staff review.
Require expiration, add conditional credentials, and remove unnecessary sensitive fields.
Notify the right location and tag responses by visit type.
Submit every path and confirm staff see the expected details.
Choose an intake method
Compare how each method structures customer details and staff review.
Field guide
Use these six sections as a practical checklist, then adapt the fields and notices to the store's jurisdiction, record-handling process, and reviewed policies.
Customer profile
Use separate fields for legal name, birth date, phone, email, and address so staff can compare them with presented documents.
Identification
Separate document type, identifier, issuer, and expiration. Clearly label an image upload as optional or required.
Visit type
Reveal medical credential or caregiver fields only when applicable, without unnecessary diagnosis questions.
Store policies
Show the store's reviewed rules before a distinct acknowledgment. Add the policy version when needed.
Data notice
State why information is collected, who reviews it, and where customers can ask questions.
Optional permissions
Give loyalty, email, and text updates their own unchecked choices and preference-change instructions.
Related tools
Connect registration with general intake, feedback, contact, ordering, and carefully separated consent workflows.
Create a general customer profile workflow with contact preferences and account details.
Open toolOrganize detailed onboarding questions and route complete records to the right team.
Open toolAsk about store experience, product discovery, service, and requested improvements.
Open toolGive prospective customers a short path for questions that do not require registration.
Open toolStructure item, pickup, and contact fields for stores with an established ordering process.
Open toolBuild a standalone acknowledgment flow around organization-provided wording and review steps.
Open toolFAQ
Practical answers for dispensary operators planning customer intake and staff review.
It collects a customer's profile, ID details, visit type, store acknowledgments, and communication preferences for staff review. It does not replace required in-person checks.
Use separate fields for document type, number, issuer, and expiration, plus an image upload only when needed. Follow the store's reviewed collection and retention procedure.
Yes. Conditional logic can show credential and caregiver fields only for medical visits. Avoid unnecessary diagnosis or treatment questions, and tag responses by path.
Yes. Share a link or website embed, explain staff review, and state whether documents must still be presented in person. Submission should not imply confirmed eligibility.
Place the store's reviewed wording before its acknowledgment. Keep store policy, data use, and optional communications in separate fields. Seek appropriate review for suitability.
Yes, when an upload fits the store's reviewed process. Explain its purpose and access, configure retention deliberately, and avoid images when structured details suffice.
Yes. Makeform provides unlimited free forms and unlimited free responses. You can generate, edit, publish, and share the registration form without a response cap; the paid tier removes the Makeform badge.
Use separate, unchecked loyalty, email, and text choices. Keep them apart from required acknowledgments and explain how customers change preferences.
Replace scattered intake notes with one clear workflow.
