The moment browsing becomes a real inquiry
A catalog is good at helping me discover wholesale products from China. It is usually much less complete at telling me what one specific order would cost or include. A clean photo may sit beside an old caption. A visible price may belong to a different quantity. “Low MOQ” may mean one piece per style, one carton per color, or a minimum total value across the order.
Before I contact anyone, I make a short inquiry note. It contains the public page URL, product code, screenshot date, category, intended quantity, destination country, and every detail still marked unknown. That note is more useful than forwarding a screenshot with no context.
1. I send a product code and the page URL
A screenshot alone can be cropped, reposted, or detached from the listing that explained it. I include the exact product code and the public catalog or album URL whenever they are available. If the page has no code, I use a neutral description such as “black zip hoodie with grey lining” and state that the identifier is missing.
I also ask the respondent to repeat the code in the quote. That small step helps catch a reply for a similar item, a different color, or a replacement product before I compare prices.
2. I choose a test quantity before asking about MOQ
“What is your MOQ?” sounds precise but often produces an answer that is hard to use. I decide what I am actually considering—for example, 20 pieces split across two colors and four sizes—then ask how the minimum order quantity is calculated.
| Question I ask | Why it matters | What I record |
|---|---|---|
| Is the MOQ per style, color, size, carton, or entire order? | The same minimum can create very different usable assortments. | The exact unit and any required mix. |
| Can I place a smaller test order? | A sample quantity may have a different price or may not be available. | Test quantity, unit price, and restrictions. |
| Which quantity tiers change the price? | A low headline price may apply only to a much larger bulk order. | Price at each quantity I might realistically buy. |
| Are colors and sizes counted together? | Mixing variants may be allowed, limited, or priced differently. | Permitted mix and minimum per variant. |
3. I separate unit price from everything around it
I never save a wholesale price without its currency, quantity tier, variant, date, and source. I ask whether the amount includes domestic delivery, export packing, payment fees, customization, or international shipping. If the reply says only “$8,” I still do not know what eight dollars buys.
For a useful comparison, I keep product cost, packing, local delivery, service charges, and international freight in separate fields. I do not add them into a pretend landed cost until the route and quantities are clear.
4. I ask for colors, sizes, and measurements as data
“Available in all colors and sizes” is not a size chart. For clothing, I ask for the measurement table for the exact product code, the measurement method, the unit, and any stated tolerance. For shoes, I ask which size system is used and whether an insole or foot-length reference is available.
I write the requested mix directly in the message: color, size, and quantity on separate lines. If a color name is ambiguous, I reference the catalog image and ask for a current photo. I do not assume the screen color, stock color, and final packed color will be identical.
5. I ask what the QC photos will actually show
Requesting QC photos is useful only when I know what those images represent. I ask whether they will be taken before shipment, whether they show the specific handled goods, which angles are included, and whether the product code or order reference will remain visible.
- For clothing, I ask for front, back, label, seam, print or texture, and measurement views relevant to the item.
- For shoes, I ask for both sides, toe, heel, outsole, interior label, and size evidence.
- For bags, I ask for dimensions, interior, closures, straps, base, and hardware.
- For electronics, I ask for the exact model label, connectors, included parts, and whatever functional test is explicitly available.
QC photos can reveal visible condition and differences. They do not prove authenticity, hidden construction, future performance, or that the photographed item will definitely be the shipped item. I keep those limits in the note.
6. I prepare the destination before requesting a shipping quote
An international shipping quote needs more than a country name. I provide the destination country and postcode, expected quantity, and any relevant product restrictions. I ask for estimated packed weight and dimensions, whether boxes or protective packing are included, which delivery terms the quote uses, and how long the quote remains valid.
If batteries, liquids, magnets, or other route-sensitive components may be involved, I state that before accepting a route estimate. I treat shipping time as an estimate and keep it separate from handling or production time.
A WhatsApp product inquiry I would actually send
I keep the first message short enough to answer, but complete enough to avoid a long sequence of basic follow-up questions:
Hello. I am asking about product code [CODE] from this page: [URL].
My test quantity is [QUANTITY], split as [COLORS / SIZES]. Please confirm the MOQ rule, unit price at this quantity, currency, material, current available variants, and the size chart for this exact code.
Please also tell me whether pre-shipment QC photos are available, the estimated packed weight and dimensions, and the shipping quote to [COUNTRY / POSTCODE]. Please show product cost and shipping separately.
I do not treat a WhatsApp profile, fast response, or polished product catalog as supplier verification. I still compare the public identity, source link, payment terms, protection, and independent evidence before deciding whether to continue.
How I read the reply
A reply I can use
It repeats the item and answers in fields
The code, quantity, variant mix, MOQ unit, price tier, currency, measurement source, QC stage, packing estimate, destination, and quote date are explicit. Unknowns stay visible.
A reply I pause on
It replaces details with confidence
The item is not identified, the price has no quantity, “all sizes” replaces a chart, shipping is bundled into an unexplained total, or the reply pressures me to pay before the basic questions are answered.
My comparison note after the chat
- The product code in the reply matches the page I sent.
- The MOQ unit and permitted color or size mix are explicit.
- The unit price has a currency, quantity tier, variant, and date.
- The size or specification information belongs to this exact product.
- The QC-photo stage and promised views are described without unsupported guarantees.
- Product, packing, fees, and international shipping remain separate.
- The destination, packed-weight basis, route assumptions, and quote validity are recorded.
- Missing answers remain marked unknown; I have not filled them from a similar listing.
Why I do not begin with brand or quality claims
A familiar brand term may help someone locate a directory, but it does not answer my sourcing questions. I start with the product type, code, material, construction, quantity, and measurable details. I do not repeat claims such as “official,” “authentic,” “genuine,” or “original” unless the person making the claim provides lawful, independently checkable support.
The small rule that saves me the most time
I never convert silence into an answer. If the MOQ basis, size chart, QC stage, or shipping calculation is unclear, I leave that field blank and ask once more. A shorter comparison built from explicit answers is more useful than a long supplier list built from assumptions.
Before continuing, I use the product-evidence checklist, compare the album and QC views, and review the contact and payment warning signs.