Before sending a Yupoo product inquiry, record the product URL, code, selected option, intended quantity, destination context if relevant, and one missing field. A Yupoo WhatsApp inquiry should ask that question in a form that can be answered with a number, option, photo, document, or explicit condition.
A reply is dated information from the sender. It does not verify identity, stock, product quality, payment protection, or delivery.
Prepare the record before the message
- Original public URL and date checked.
- Neutral product name and visible code.
- Exact color, size, material, and included parts.
- Intended quantity or sample request.
- What the page already shows.
- One field that would change the decision.
If you cannot identify one stable item, return to the catalog-record workflow before contacting anyone.
Use a compact message structure
Hello. I am reviewing [neutral product name], code [code], in [color / size / option].
Planned quantity: [quantity or sample].
Page: [public URL].
Could you confirm [one decision-changing field] and state what the answer applies to?
Please include the option, unit, currency, quantity basis, and date where relevant. Thank you.
Keep personal details, payment information, and customer data out of early research messages. Share only what is necessary through the responsible service.
Ask one decision-changing question at a time
Weak
“Best price? More details? Fast shipping?” combines several undefined requests and gives the reply no stable basis.
Stronger
“For code A17, black, size M, 20 units: does the minimum apply per color or across the style?” identifies the item and the decision.
Group questions only when they share the same basis, such as measurements and their unit. Otherwise, resolve identity and option before price, then quantity before shipping.
Turn every reply into an explicit state
| State | Meaning | Next action |
|---|---|---|
| Confirmed | The answer names the same item, option, basis, and date. | Attach it to the record and continue. |
| Conditional | The answer depends on quantity, option, route, or another condition. | Write the condition beside the value. |
| Unanswered | The reply does not address the requested field. | Ask once more with a narrower question. |
| Conflict | The reply disagrees with the page or an earlier message. | Preserve both and request clarification. |
| Expired | The reply is too old or the product record has changed. | Reconfirm before using it. |
Keep a reply ledger
Record the date, channel, item code, exact option, question, short answer, state, and next action. Do not publish private contact information or full customer conversations.
| Date | Item / option | Question | Answer summary | State | Next step |
|---|---|---|---|---|---|
| Aug 22 | A17 / black / M | MOQ scope? | 20 per color; sizes may mix | Conditional | Confirm size ratio |
Follow up only when it can close the gap
A useful follow-up repeats the stable code and option, quotes the unresolved part briefly, and asks for one missing condition. Stop when the sender changes the item, avoids a decision field repeatedly, pressures payment, or moves the conversation to an unexplained account.
Silence, a sent indicator, or a message marked delivered is not a product, payment, shipping, or service outcome.
Keep inquiry records privacy-safe
Store only the information needed to understand the product decision. Redact phone numbers, personal names, addresses, account identifiers, order numbers, payment details, and unrelated chat content before sharing a research note.
Use the buyer-safety guide when contact identity, payment pressure, or protection becomes part of the decision.