A parts inquiry says the customer needs a replacement for the small blue unit. The catalog contains two sizes, an older revision, and several similar accessories. Staff must identify the product before answering the question. The missing step is a reliable lookup clue.
WordPress form product reference fields should collect the identifier staff use, explain where the visitor can find it, and admit when it is unknown. Preserve the answer exactly. Treat a submitted model or SKU as a lookup clue until someone checks the catalog.
Choose a model, SKU, or part reference
Choose the identifier that changes the first staff decision. A product SKU, manufacturer model, catalog page link, and customer order reference have different purposes. Ask for the one needed to identify the item rather than collecting every possible number.
Write a label that explains the reference. Product model number is clearer than Reference. Add a short instruction about where to find it, such as the product label or a catalog page. Use an example that belongs to your catalog and label it as an example.
These common uses can help you choose the field. Your maintained catalog decides which reference is authoritative:
- Model number commonly identifies a product model or variant.
- SKU commonly identifies an item in the seller’s catalog.
- Serial number commonly identifies an individual unit; collect it only if this inquiry needs that distinction.
- Part number commonly identifies a component or replacement item.
Keep identifiers as text
Model numbers may contain leading zeros, letters, spaces, or punctuation. A field that treats the answer as a quantity can change the identifier before staff see it. Keep product references in a text field unless the catalog has a narrower, verified format.
Do not silently strip characters to make the answer look tidy. Check whether the form, notification, stored record, and any review result retain the same value. Quantity and measurements belong in their own fields; the guide to quantity and units covers that separate question.
W3C’s labeling controls guidance explains why each field needs a descriptive associated label. A placeholder example alone is not enough to identify the field after the visitor types.
Give unknown references a useful path
Some visitors cannot read a worn label or are asking about an item they have not bought yet. Add an I do not know option when staff can still help. Ask for the product description or a public product-page URL instead of forcing an invented number.
If staff truly cannot act without a reference, explain why and where to find it. Use a fixable field message that identifies the missing detail. Avoid turning a missing model number into a vague failed submission.
Keep photos and files separate from the reference field. The guide to reviewing uploads without sending files to AI explains the distinction between a submitted file and a text review packet.
Preserve references in the review aid
A useful review aid might say: Visitor supplied model AB-004, described the blue unit, and asked about a replacement cover. Catalog match not verified. This keeps the exact identifier and the question visible without inventing compatibility.
Sentient Forms Entry Summary can condense a submitted request for staff. Use Missing Information Review when the checklist needs to flag an absent reference or another detail that blocks the next decision. Ask the review to preserve unknowns and keep the original submission available.
Review surfaces vary by form source. Gravity Forms supports native results where the action permits them; Contact Form 7, WPForms, and Elementor Pro Forms use the enabled Sentient Forms Submission Ledger where native display is unavailable. The plugin listing describes the current boundary.
Verify the match before a commitment
Compare the submitted reference, product description, and maintained catalog record before staff quote or promise fit. If the values disagree, ask a clarification question and keep the lookup open. A correctly copied identifier can still refer to the wrong item.
Do not let a review note promise fit, stock, a price, or delivery. Those answers depend on current records and the business’s approval process. The form can prepare the lookup; the owner still makes the product decision.
Test the references that usually break
Submit a leading-zero reference, a mixed-case model, punctuation, and a value pasted with surrounding spaces. Try two similar product identifiers and a description that contradicts the selected model. Compare the original answer with the notification, stored record, and summary.
Test an unknown reference and an obsolete product-page URL. Retain the original text and flag ambiguity for staff. Use ordinary catalog choices when you maintain a small fixed list; reserve text input for cases where the list cannot cover the visitor’s answer.
Count lookup rework
For a fixed sample, count inquiries that need an extra product-identification question, references changed by the form, and matches corrected after staff check the catalog. Compare the same measures after revising the field.
Keep the smallest field set that helps the reviewer reach the right item. Add a second identifier only when the first leaves a repeated, named ambiguity. If that second field produces guesses instead of better matches, simplify or remove it.
Frequently asked questions
A text field is usually safer for a model number, SKU, or part number because identifiers can contain leading zeros, letters, and punctuation. Use a narrower rule only when the maintained catalog format supports it.
Offer an unknown path when staff can still help, and ask for a product description or public catalog link. If the reference is essential, explain where to find it and why staff need it.
A form summary is not proof of compatibility. Staff or an approved product system must check the submitted reference against current catalog records before making that commitment.
Start with the form that prompts the most “Which product?” follow-ups. Fix the reference field and test exact preservation. Add a review action only if it removes a repeated scanning task.
