product code / inquiry / shortlist / catalog
Why Product Codes Matter in Catalog Inquiries
A guide to using the displayed product code as the stable reference in shortlists, screenshots, WhatsApp messages, and inquiry forms when titles or similar-looking items can be ambiguous.
Treat the code as the conversation anchor
Catalog titles are written for people and may describe several similar items in comparable language. The displayed product code distinguishes the exact catalog record you viewed. Copy it when you add an item to external notes, save a screenshot, or ask a question. A link is useful too, but the code remains readable when a message preview fails or a screenshot is separated from its original page.
Do not infer brand model numbers, production dates, or other meaning from an internal-looking code unless the page explicitly identifies that meaning as a verified fact. Some codes originate with a source and others are assigned for catalog management. Their dependable role on VivaMode is reference: they connect an inquiry to the correct visible record. They are not, by themselves, evidence about origin, authorization, availability, or product specification.
Pair each question with one item
When sending several choices, group questions by code. Write the code, a short recognizable title, then the missing information you need. Avoid placing all codes in one line followed by a broad question such as which is best. The responder should be able to see whether a dimension, image request, or color clarification belongs to one item or the whole shortlist.
- Copy the code directly from the product page.
- Include the semantic product link when available.
- Label screenshots with the code before sending them.
- Recheck the page if a code and image appear mismatched.
Preserve a simple decision record
Keep the code in your final notes alongside the date, visible facts used, and any answers received. This is especially helpful when a shortlist changes over several conversations. If a page later becomes unavailable, the code still identifies what was discussed, although it does not preserve or promise the product state. Clear references reduce avoidable ambiguity and leave more room for the actual comparison.
