How to Handle Size and Color Inquiries for Apparel on WhatsApp

A customer messages you on WhatsApp: "Does this come in red?" You reply "Yes." Now he wants the color code, the fabric, whether it's in stock, and the MOQ — at least three more rounds before you even talk price. The fix for how to handle size and color inquiries for apparel on WhatsApp isn't a friendlier script. It's giving the full picture in one shot: a structured image reply built from a color card and a size chart, instead of a wall of text.

Why Customers Keep Asking About Size and Color — The Real Cost of Back-and-Forth

Describing sizes and colors in text hits three walls.

First, interpretation drift. You write "wine red," and the customer pictures true red, brick red, or purple-red. You write "slim fit," and he guesses based on how his usual M fits — then finds the shoulder is two centimeters off when the goods arrive. Second, incomplete information. When one message crams in color, size, stock, and price, the customer grabs one point and replies to that, leaving the rest buried. Third, forced re-confirmation. Every new dimension the customer asks about means you reorganize your words from scratch. Both sides do the same work twice.

The hidden cost of back-and-forth is higher than it looks. Cross-border chat runs on time zones. You send in the morning, the customer replies at night — one round eats half a day. Confirming one color and one size, if split into "Do you have red — what color code — is it in stock — what's the MOQ — can I mix colors," easily drags the deal one to two days. In peak season, that day or two can decide who gets the order.

A concrete scene. Customer: "Does this hoodie come in red?" You: "Yes." Customer: "What kind of red? Got a picture?" You send a phone snapshot. Customer: "Which looks better, this red or navy?" You type a paragraph. Customer: "Is the red in stock? How fast for 500 pieces?" That's five rounds, and you haven't discussed price. If round one had been a color card labeled with color code, fabric, and stock status, the customer could scan every color himself and say "I'll take R03, 500 pieces." Five rounds become one.

The Core of Structured Replies: How a Color Card and Size Chart Replace Paragraphs

A color card isn't a collage of product photos. It's an information card. Each color gets one cell, and each cell holds three things: a color swatch or small product shot, a color code (R03, NV07), and fabric plus stock status (in stock / made to order / MOQ). One glance tells the customer what's available and what each option requires. No follow-up needed. The color code matters most — it becomes the anchor for everything after. "R03" is far more precise than "that red."

The size chart solves returns. Writing S/M/L alone means nothing. Give real numbers: chest, length, shoulder, sleeve, all in centimeters, plus a measurement diagram showing which seam each number comes from. A customer with a tape measure can check his own garment against the chart — far more reliable than "fits 60–70 kg." You can add a recommended height/weight column for reference, but state clearly it's a guide, and actual measurements govern.

Pre-building common Q&As as image cards is how structured replies get done. Customer asks "What colors?" — send the color card. "How do I pick a size?" — send the size chart plus "Can you tell me your height and weight? I'll recommend one." "Is this color in stock?" — the color card already shows stock status; point to it. The same cards get reused, so reply quality no longer depends on who's on shift or how well they remember.

In Practice: A Standard Reply Flow from First Inquiry to Confirmed Order

Lock the flow down, and a new hire can follow it.

Step one. Customer asks "What colors does this style come in?" — send the color card immediately with one line: "Here are all current colors. Please tell me the color codes you're interested in." Note: color codes, not colors. This trains the customer to reply with codes. If he says "R03 and NV07," you know to pull detail shots and stock for those two.

Step two. Customer asks "What size should I wear?" — send the size chart and proactively ask height, weight, and his usual size. Don't wait for him to study the table; many customers won't measure. Say: "Do you usually wear M or L? Roughly what's your height and weight? I'll match it for you." Once he gives numbers, recommend from the chart and add: "If you like a looser fit, go one size up."

Step three. Once color and size are confirmed, send the quote directly. Include unit price, MOQ, lead time, payment terms, and whether mixed colors/sizes are allowed. The key is "send directly" — don't ask "So how many do you want?" and wait another round. Pre-set price tiers by quantity and let the customer choose. When he replies "500 pieces, R03, half M half L," the order info is complete. You only confirm payment and scheduling.

Done well, the whole flow runs three to four rounds. Compare that to no color card and no size chart: the customer wants color photos, color codes, stock, size data, measurement method, and a price breakdown — six to eight rounds minimum.

Double Your Reply Speed: Building a Pre-Made Asset Library and Quick Replies

Build the asset library by category, name by code. Suggested structure: T-shirts / Hoodies / Pants / Outerwear, with two folders per category — color cards and size charts. Name files like "category-style-colorcard-Spring2026" so typing the style number finds it without relying on memory.

WhatsApp's quick reply feature does the rest. In settings, bind common image-text combos to shortcuts. Type "/color" to pull up the color card plus the guiding line; "/size" for the size chart plus the height/weight question; "/quote" for the quote template. Even a new hire unfamiliar with the asset library can send a standard reply via shortcuts.

Update assets on a schedule. Check stock status on color cards weekly; gray out or remove sold-out colors. If the fit or fabric changes, update the size chart data in sync — otherwise customers order off the old chart, and the return cost dwarfs the effort of remaking one image. At season change, archive old color cards and file new ones under the same naming rule, so old and new never get mixed up.

Multilingual Pitfalls: Keeping Size and Color Info Accurate Across Languages

The most common error is unit confusion. You write "chest 52." A European customer reads centimeters; a US customer may read inches. Nobody fits a 52-inch chest. Fix it by labeling both "cm" and "inch" columns in the size chart image, or at minimum state the unit in the header. Don't leave it to guesswork.

Literal color translation also breaks. "藏青" rendered as "dark blue" may read as deep blue or navy — far from the actual shade. The safer route: present colors as images, label both the Chinese and English color names inside the image, and add the color code. The customer looks at the picture; text is secondary, so translation error matters less.

For anything that must be text, standardize a glossary internally. "现货" is always "in stock," "起订量" always "MOQ," "交期" always "lead time" — not one person writing "delivery time" and another "production time." Keep the glossary in a shared doc; it's the first thing a new hire reviews. If you serve multilingual customers, reconfirm key details in their language to avoid misunderstanding.

From Manual to Assisted: Turning Color Cards and Size Charts into Draft Replies

Manually sending from an asset library has limits. New hires don't know where files live, busy days mean forgotten sends, and multilingual customers add translation time. One rep juggling five chats can burn half a day in the find-image-send-image-explain loop.

Tools can carry part of this. A Chrome extension like Sellenca overlays directly on WhatsApp Web — reps keep their number, don't migrate to the Business API, and change nothing about their chat habits. It drafts replies based on your company's own product knowledge base, including color card and size chart information, and the rep confirms before sending. Note: draft plus confirmation, not an unattended bot. The knowledge base mines Q&As and scripts from real closed conversations, so the longer you use it, the closer the drafts match your own phrasing. You can see the specifics on the features page.

One team's production numbers offer a reference: 97% AI suggestion acceptance rate, 1,973 average monthly AI calls, 960+ customer profiles, and 907 knowledge-base Q&As. These figures show that once structured reply content is deposited into a knowledge base, it gets reused efficiently instead of being rebuilt from zero every time.

Action Checklist: Five Moves You Can Start Today

1. Organize your current color cards and size charts into image format, named "category-style-type-season."
2. Set up five quick replies in WhatsApp covering the five high-frequency questions: color, size, stock, price, lead time.
3. Post the asset library link in your team group so everyone can find it; walk new hires through it on day one.
4. Review inquiry logs weekly and add any asked-but-missing Q&As to the library.
5. Try Sellenca's free trial (coming soon) to see AI-generated structured reply drafts. Pricing and trial details are on the pricing page.

FAQ

When a customer asks "Do you have other colors?" what else can I do besides sending the color card?

The color card answers "what colors exist." But "other colors" usually means he's not happy with what's shown. Add a nudge: "What palette do you prefer — cool or warm? I'll check for something close." Also point out any colors marked "made to order" on the card, explaining they can be produced to his needs but require meeting the MOQ. If nothing fits, say so plainly. Vagueness only creates more rounds.

What should a size chart include to reduce returns?

At minimum chest, length, shoulder, and sleeve — four core measurements, all in centimeters, plus a measurement diagram showing start and end points for each. You can add a recommended height/weight column as a guide, but note that actual measurements govern. If the fabric stretches or the cut is special (oversize, for example), flag it on the chart so customers factor it into sizing. The more specific the data, the better customers judge for themselves, and the lower the return rate.

How do I handle a customer's size that doesn't match our chart?

First confirm which sizing system he's using. EU, US, and Asian sizes can differ by one to two sizes for the same letter. Ask for his height, weight, and the brand size he usually wears, then recommend against your chart. If he insists on ordering his size, note in the order confirmation: "Produced to customer-provided size; sizing risk borne by customer." Keep the chat record in WhatsApp for reference.

Does replying with images look unprofessional?

The opposite. A color card labeled with color codes, fabric, and stock status reads far more professional than a paragraph of "We have red, blue, black; the red is wine red, the blue is navy..." The key is that the image is clear, the info accurate, and the naming consistent. A blurry phone screenshot or an outdated image does look unprofessional. Treat color cards and size charts as formal product materials, and customers read it as supply chain competence.

To see how structured replies run in a real WhatsApp conversation, book a demo and test a round with your own product materials.