An inquiry basket is a different promise from a checkout

A buyer may want to ask about several products together. An inquiry basket can help, but it should not look like an ordinary purchase checkout if price, availability or suitability still require review.

Explain the action

A Czech supplier can describe the basket as a request list and explain what staff will check. The final button should identify the action accurately. A received inquiry is different from a confirmed commercial order.

Keep each item identifiable

The request should preserve the item reference, readable description, quantity and any approved option choices. A staff member needs to understand the list even if a product page is edited after submission.

Try a mixed example

Use fictional items: one standard product, one variant and one custom request. Check whether the customer summary and staff record retain the distinctions. Explain how unavailable or changed items are handled.

Decide the next conversation

The business defines who replies, which information may need clarification and what creates an accepted offer. Commercial and professional review cannot be inferred from the existence of a web form.

W3C's notification guidance supports clear status feedback. We can develop a catalog inquiry route with the staff handover included, rather than borrowing checkout language that suggests an unsupported commitment.