Rewrite a returns policy into a plain-language explainer that actually answers what customers search for before contacting support

Rewrite this returns policy into a plain-language explainer page. The goal is reducing support contacts from people who couldn't find the answer in the existing policy text, not producing a shorter version of the same legal document.

CURRENT POLICY TEXT
"Items may be returned within thirty (30) calendar days of the delivery date provided they are unworn, unwashed, and in original condition with tags attached. Return shipping costs are the responsibility of the customer except where the return is due to a defect or fulfillment error, in which case a prepaid label will be issued. Refunds are processed to the original payment method within 5-10 business days of the returned item being received and inspected."

MOST COMMON SUPPORT QUESTIONS ABOUT RETURNS
"Do I have to pay for return shipping?", "How long do I have to return something?", "Can I return something I already wore once to try it?", "When will I get my money back?"

ACTUAL POLICY TERMS THAT MUST STAY ACCURATE
30-day window from delivery, unworn/unwashed/tags-attached condition, customer pays return shipping except defects/fulfillment errors, 5-10 business day refund processing after inspection.

EXCEPTIONS OR EDGE CASES
Final sale items (marked as such at purchase) cannot be returned at all; swimwear must have the hygiene liner still attached.

STRUCTURE
Organize the explainer around the actual common questions given, as a Q&A or short-section format, rather than the policy's original legal-document structure (definitions, then conditions, then process) — customers search for answers to specific questions, not for a document structure. Every factual claim in the rewrite (timeframes, condition requirements, who pays return shipping, refund method and timing) must match the actual policy terms given exactly — do not simplify a specific number or condition into a softer, vaguer version, since that creates a real gap between what the page says and what the policy actually allows, which is exactly the kind of mismatch that generates disputed support tickets. State each named exception clearly rather than folding it into a blanket "see terms for exceptions" — a customer whose situation is the exception needs to be able to find that out from this page directly.

TONE
Write it as if a helpful support agent were explaining the policy out loud, not as if a lawyer were stating conditions — but never at the cost of precision on the actual terms.

WHAT NOT TO DO
Do not add a legal disclaimer stating this explainer supersedes or is separate from the official policy unless one is specifically requested — that undermines the point of the page, which is to be the thing customers can actually rely on.

OUTPUT FORMAT
A short intro line, then the common questions each as its own short-answer section, then a clearly labeled exceptions section.