Fragrance Consultation Intake Form

Use it for fragrance counters, stylists, independent perfumers, beauty advisors, and customer service teams that make personalized scent recommendations. It works best when the goal is to narrow choices before a consultation or product trial. If you only need a quick walk-up recommendation, a shorter preference card may be enough.

This template captures scent family preferences, preferred strength and sillage, occasions, climate or season, current fragrances, sensitivities, ingredient avoidances, and budget range. It also includes consent and contact preference fields so follow-up is clear. The result is a structured brief you can use to match products without asking the same questions twice.

Use it when you need consistent intake across multiple advisors, locations, or consultations. It is also useful when you want a record of what the customer said they like, dislike, or need to avoid. Ad-hoc conversations are fine for casual browsing, but they often miss sensitivities, preferred intensity, or the reason behind a prior purchase.

Complete it at the start of a consultation and update it whenever preferences change, especially after a new sensitivity, a seasonal shift, or a change in fragrance goal. For returning customers, you can reuse the previous intake and only confirm what has changed. That keeps the form short while preserving useful history.

Use the sensitivities section to capture the issue in plain language and keep the field optional unless it is needed for safe recommendations. If the customer names specific ingredients, record only what you need to make a recommendation and avoid collecting unnecessary medical detail. Include a patch-test preference so you know whether to suggest a sample or a skin test first.

Yes. You can tailor the scent family options, add brand-specific notes, or change the occasion field to fit bridal, gifting, retail, or subscription workflows. The structure already supports progressive disclosure, so you can show extra fields only when a customer selects a relevant use case. That keeps the form shorter and easier to complete.

Use clear labels, required and optional markers, and field types that match the data, such as dropdowns for scent families and date or text fields only where needed. If you collect contact details or sensitivity information, include a plain-language consent line and explain what happens after submission. For public-facing use, keep the form WCAG-friendly and collect only the minimum information needed for the consultation.

This form pairs well with CRM records, appointment booking tools, email follow-up, and inventory or recommendation workflows. You can route submissions to a consultant, tag them by scent family, or create a follow-up task for sample selection. If you use automation, keep the routing simple so the intake data stays easy to review.

The biggest mistakes are making every field required, asking for too much detail about sensitivities, and skipping the follow-up explanation. Another common issue is using free-text fields where structured choices would make recommendations easier to compare. Keep the form focused on what you will actually use, and add conditional logic only where it reduces clutter.