Ask which product a buyer means before asking for every specification

A buyer can arrive knowing a product family but not the exact item. A form that requires a complete part number may stop a useful inquiry. A form that asks only for a message may leave staff with another round of clarification.

Offer the right starting point

A Czech supplier's catalog can distinguish an exact item request from help choosing within a family. The second route can ask about the intended use and constraints your team actually reviews. It should not pretend to make an engineering decision automatically.

Keep identity and description together

When a buyer selects an item, include a stable product reference and a readable name in the request. A page title alone may change during editing. Staff should be able to identify the product without asking the customer to resend the link.

Use two fictional requests

Buyer knows	Helpful first question
The exact item	Which reference and quantity are required?
The application only	Which requirement should staff help clarify?

Test both routes with the sales or technical reviewer. Remove fields that do not help the first decision and make optional information recognizably optional.

W3C's form-instruction guidance supports clear questions and examples. Your business determines the technical information it needs. We can scope the catalog route and request tool around those two starting points.