Why clothing works so well on WhatsApp
Clothes are a visual, conversational purchase. The customer wants to see the piece, ask whether the size runs true, and have someone confirm shipping the same day. In a big store that takes a form; on WhatsApp it takes three messages. That's why clothing catalogs are among the highest-order businesses: the channel already exists — only the order is missing.
The other reason is repeat purchase: a customer who bought once and was treated well comes back every season and brings friends. A well-run clothing business grows almost by itself, contact by contact.
Sizes and colors: where half the sales die
The classic mistake is posting 'blue blouse $250' and having every customer ask if there's a medium. Every question is a sale waiting for your reply. The catalog has to answer on its own: size and color in the product title or in visible options, and when something sells out, marked as sold out instead of still taking orders.
If you carry S, M, and L, publish a size chart once — a fixed link in your catalog — and reference it from every product. Answering 'how do I know my size?' before it's asked is one fewer return later.
- Full title: 'Long-sleeve blouse — size M — navy'
- Visible variants: color and size as options, not surprises
- A fixed, linked size chart on every product
- Sold out means sold out: never take payment for what you don't have
Photos that sell clothes (no studio, no pro model)
The most honest clothing photo is the piece on a hanger in good natural light against a clean background; the one that converts best is the same piece worn, even if you or your sister are the model. Publish both when you can: the first shows the product, the second shows how it falls — and that's the doubt that stalls the purchase.
Minimum rules: same lighting across the whole catalog (no half-yellow, half-blue photos), one full shot and one texture detail, and never screenshots of someone else's catalog with brightness eating the color. Your customer compares with downtown shops: a murky photo loses every time.
Orders with summaries, not message chains
A disorganized clothing order on WhatsApp looks like this: 'hi, I want the blue blouse', 'what size?', 'M', 'ship it where you did last time?', 'yes', 'that's 250 plus 60 shipping, can you send the deposit?'. Multiply by thirty customers in one day and something breaks: a wrong size, a double shipment, an untracked payment.
A catalog with a cart fixes that: the customer builds the order — product, size, color, quantity — and a ready summary lands in your chat. You confirm availability, send the total with shipping, done. The chat stays for what genuinely needs a human: recommending, solving doubts, taking care of the customer.
Exchanges and returns: the policy that saves fights
In clothing there will be exchanges: the size didn't fit, the color looked different. Decide the policy before the first order and publish it in your catalog: how many days the customer has, whether exchanges cover sizing or defects, who pays reshipping, and what condition the piece must be in. Written and visible, it filters people trying to return worn items and protects serious customers.
A standard policy that works for catalog sales: exchange within 3 to 5 days, piece unworn with tags, first exchange with split shipping. With that, almost nobody abuses it and almost everyone buys again.
Seasons: how stock arrives and how it sells
Clothing runs in seasons. The practice that sells best on small inventory is the 'drop': announce on Tuesday that 20 new pieces arrive Thursday, take reservations in advance, and publish the updated catalog Thursday with reserved pieces marked. It creates real expectation without big stock.
And season's end is cash, not loss: discount what's left so you can buy the next batch with money in hand, not debt. The published catalog does double duty: selling the new and clearing the old in the same place.