A buyer opens an inquiry form from the product page for model CS-240. The form rejects the phone number. After correcting it, the buyer submits again, and the sales team receives an inquiry with no model attached. The visible error was fixed; the useful context was lost.

Treat the model as server-owned data, not as a line in the buyer’s message. The page can send a model key with the form, but the server should resolve that key against the products the buyer is allowed to inquire about. Keep the resolved model identifier attached to pending form state across validation failures. If the form supports a general inquiry with no model, store that as an explicit state rather than guessing from a referrer.

My first tests would be small:

  • Submit from a product page, trigger a validation error, correct it, and check that the accepted inquiry carries the original model.
  • Alter the model key to one that is retired or not available in that market. Check that the server does not route it as a valid product inquiry.
  • Open the general inquiry form. Verify that it does not quietly inherit the last product viewed.

Do not use a hidden field as proof of access. It is a hint that needs validation. The test is complete when the receiver can see which model the buyer meant, even after the buyer had to correct the form.