Customer Support for Shopify Apparel Stores: Sizing Questions, Returns, and Exchanges

Clothing is the highest-return category in e-commerce, consistently running return rates of 20–30% compared to 8–10% for most other product types. The reason is structural: fit is subjective, sizing varies across brands, and a customer can't try something on before buying it. That uncertainty generates support volume before the purchase (sizing questions) and after it (return and exchange requests) at a rate that other store types don't experience.

The good news is that most of this volume is predictable. The same questions come up again and again, and the same processes handle them. That makes apparel support particularly well-suited to automation once the patterns are documented.

Reducing sizing questions before they hit your inbox

The best sizing question is one that never gets sent. Most pre-purchase sizing emails exist because the product listing didn't give the customer enough to make a confident decision:

• Add actual measurements to every size option. "Small = fits 34–36" chest" is more useful than a generic size chart link. If a customer can see measurements, they compare to their own — the question is answered before it's asked.
• Include model sizing context in product photos. Showing a 5'9" person wearing a medium gives a customer a reference point they can actually use. Generic lifestyle photography is nice; sizing context is functional.
• Address fit in the product description. "This runs slightly slim — if you're between sizes, we recommend sizing up" preempts a support email and reduces size-related returns in the same sentence.
• Add a size chart to the product page, not just the footer or FAQ. Customers don't hunt for size charts. If it's not visible on the product page itself, most won't find it — they'll email you instead.

Handling return and exchange requests efficiently

For sizing-related returns, exchanges are almost always the better offer. A customer who ordered the wrong size wants the right size — not a refund. Defaulting to "would you like to exchange for a different size?" converts a potential revenue loss into a retained sale in most cases.

A clean exchange process for an apparel store looks like:

1. Customer emails saying something doesn't fit or they want a different size
2. You (or your bot) confirms the exchange policy and asks which size they'd like instead
3. Customer sends back the original item (with a return label you provide, or at their own expense depending on your policy)
4. You ship the replacement once the return is received

The part that generates the most back-and-forth is step 2 — customers often don't know what to do next, so they wait for instructions. If your bot can walk them through this immediately when they first email, you reduce the exchange cycle from 4–5 emails to 1–2.

For returns (not exchanges), the friction is similar: customers don't know the return address, aren't sure whether they need a return authorization, or don't know how long the refund will take. A reply that answers all three preemptively — with the address, the process, and the timeline — turns a multi-email chain into a single transaction.

Setting up Chepa for apparel-specific support

Chepa connects to your Gmail and Shopify store and handles the pattern-based emails automatically. For an apparel store, this primarily means sizing questions, return requests, exchange requests, and order status — the four categories that make up the majority of inbound volume.

The setup that works specifically for apparel:

1. Write your exchange process into the bot instructions. Describe what happens step by step — how the customer initiates, whether you send a return label, when the replacement ships, how long the refund or exchange takes to process. The more specific this is, the more accurately the bot walks customers through it without escalating to you.
2. Add sizing guidance for each product or line. If your clothing runs small, say so explicitly in the instructions: "Our hoodies run about one size small — if a customer is asking about sizing, recommend they size up if they're between sizes." Include any per-product notes that differ from your general sizing.
3. Use the delay refunds rule for size-related return requests. Chepa has a "delay refunds" behavior option — instead of processing a refund immediately, the bot first offers an exchange. For sizing returns, this converts a percentage of refunds into exchanges, which preserves revenue and usually satisfies the customer better anyway since they wanted the item in the right size, not their money back.
4. Write instructions for defective or damaged items separately. These are different from sizing returns and need a different process — usually a replacement or full refund without requiring the item back. Handling them explicitly prevents the bot from treating a "this arrived with a hole in it" email the same as a "this doesn't fit" email.
5. Escalate anything outside your standard policy. A customer requesting a return on a 90-day-old purchase when your policy is 30 days needs a human decision. An instruction like "if a customer is requesting a return outside the 30-day window, do not auto-approve — forward to escalation with the order context" keeps those from being handled incorrectly.

With this setup, the majority of your apparel support volume — sizing questions, standard exchanges, within-policy returns — gets handled automatically. You see the edge cases, the exceptions, and the complaints that need genuine judgment. The routine stays off your plate.

Frequently asked questions