Separate browsing from specifying

A customer exploring a product range is not necessarily ready to specify an order. Give them a clear way to understand the choices before asking for detailed requirements.

For a custom product, the path may include selecting a base option, describing a use case and asking about availability. Treat these as different decisions. A single large message box leaves the customer guessing about which details matter.

Capture requirements in a useful shape

List the information your team needs to assess a request. Separate required decisions from preferences that can be discussed later. Use structured fields for predictable choices and open text for the exceptions.

Preserve the product context alongside the enquiry. If a visitor starts from a particular collection or option, the team should not have to ask which page they were looking at. Show a summary before submission so the customer can correct misunderstandings.

  • Which option or product is the enquiry about?
  • Which requirements affect feasibility or price?
  • What still needs human confirmation?
  • Can both sides refer to the same request?

Keep enquiry, quote and payment distinct

A request is not automatically an accepted order. If a team member must confirm feasibility, availability or a price, make that boundary visible. The interface should explain what has happened and what the customer should expect next.

If payment enters the workflow, distinguish an initiated payment from a confirmed one. Decide which system records that state and how the team handles an exception. The exact integration depends on the commerce and payment tools in use.

Give the team an equally considered experience

The customer-facing flow is only half the design. Someone needs to review requirements, request clarification and move an accepted order forward. A clear internal summary can be more useful than an elaborate storefront feature.

Start with one common ordering path and its most important exceptions. Review it with the people who fulfil the work before expanding the system. The best scope is the smallest change that makes the buying and handling of an order clearer.