The situation
A machine, a material, a made-to-measure piece of furniture: customers ask before buying whether it fits. The question arrives by mail, and it does not say which model was meant.
Advice right at the product
Products that need explaining generate questions. If the question comes through a contact page, the one thing it is about is missing.
The job
Where the built-in tools stop
A form on a contact page of its own cannot know the product. And a form that sits on every product page is only in the way for standard goods.
This is what the form looks like
The company fields hang on a condition on the row, the rush notice on the number in the slider.
What matters here
your-shop.example/admin
FormsCancelSave
FormStructureElement
Elements
#NameTypeWidth
Create top-level element
Only where it helps
An assignment names the products that get the form. An assigned parent product covers all of its variants.
Two conditions, two kinds
The company data hangs on a choice, the rush notice on a number. Both rules run in the browser without reloading, and the server checks them again.
The product stays attached
The submission carries the product number as its context. Whoever answers it sees straight away what it was about.
Where it sits
Product assignment, position "Below buy box", collapsed behind a button. That puts the question next to the price without cluttering the page.
What comes back
Context "product" with the product number, plus customer type, quantity and urgency as columns of their own. A high urgency can be filtered in the export.