E-commerce
July 1, 2026
"Free return advertised, but I'm being charged €6.90." "Defective product, why am I paying for the label?" "Return fees will be deducted from the refund, where was that stated?" Three tickets where poorly explained return fees generate disputes, abandoned returns, and negative reviews.
The e-commerce return fee support covers who pays for return shipping, prepaid labels vs. refund deduction, compliance defect exceptions, and checkout misunderstandings. Distinct from the general returns guide and eligibility: here, we focus on return shipping cost only.
This guide #509 covers policy RETSHIP-SUP, flow RS-1 to RS-8, and matrix RETSHIP-MAP. First content on return fees. Pairs with the future customer service return fee bot (#510).
Summary
Why do return fees generate tickets?
The customer reads "easy returns" on the homepage and discovers a paid label or a deduction from the refund on the portal. The gap between the marketing promise and the actual policy feeds customer service queries.
Five typical frictions
Free vs. paid: free return on the website, fees on the portal
Surprise deduction: €49 refund, €42 received after return fees
Defect vs. withdrawal: customer believes the brand always pays
Restocking confusion: return fees confused with processing fees
International: return from the EU outside France, high unanticipated cost
Narvar points out that the clarity of the return policy influences purchases and post-purchase disputes (Narvar, returns 2025). Loop Returns documents prepaid labels vs. refund deductions as common models (Loop Returns, policy 2026).
RETSHIP #509 vs returns guide, eligibility #365 and international returns
Four pieces of content, four customer return layers.
Quick matrix
#509 RETSHIP: return shipping costs who pays exceptions
Returns guide: RMA process refund timeframe
Bot eligibility #365: eligible yes/no SKU timeframe
International returns #379: cross-border customs cost
Returns guide = complete workflow. #509 = return shipping cost layer and exceptions.
Which ret_ship_* typologies to classify?
Eight return shipping cost ticket scenarios.
Eight ret_ship typologies
ret_ship_who_pays: who pays return shipping for change of mind
ret_ship_free_claim: site said free, portal charges fee
ret_ship_deduct_refund: deducted amount from refund disputed
ret_ship_defect_exception: defective product paid label
ret_ship_label_cost: how much does the return label cost
ret_ship_restocking_confusion: confuses return fee and restocking
ret_ship_international: international return high cost
ret_ship_store_dropoff: free store drop-off vs paid post mail
Tags: ret_ship, returns. Lookup return_reason + RETSHIP-MAP before macro.
How should the RETSHIP-MAP matrix be structured?
The RETSHIP-MAP matrix documents who pays for returns by reason, market, and channel for agents and future bot #510.
RETSHIP-MAP Columns
return_reason: change_mind defect non_conform late gift
market: FR EU UK US shipping zone
customer_pays: Y/N partial amount EUR
label_type: prepaid deduct_refund customer_buy
free_return_threshold: order > X € free return
defect_exception: merchant_pays_label Y/N proof required
store_dropoff_free: Y/N locations list URL
policy_url: returns page exact fee section
RETSHIP-SUP policy in six rules
Six rules support return costs.
RETSHIP-MAP grounded: who pays amount from map only
CITE-POLICY-URL: visible return costs section link
DEFECT-PROOF: free defect label if photo proof provided
NO-FREE-PROMISE: not free if map customer_pays Y
DEDUCT-EXPLICIT: announce deduction before RMA approval
ESCALATE-DISPUTE: formal dispute → lead + finance
Flow RETSHIP RS-1 to RS-8
Flow agent eight steps return fees.
RS-1 Intake: ret_ship_* intent + order ID
RS-2 Return reason: change mind defect non conform
RS-3 RETSHIP-MAP: lookup market reason customer_pays
RS-4 Classify: free claim deduct defect international
RS-5 Respond: macro RETSHIP grounded amount
RS-6 Label action: prepaid link or deduct confirm
RS-7 Exception: defect proof → free label ops
RS-8 Close: tag ret_ship_resolved fee_cited
SLA: ret_ship_who_pays answered in one interaction with policy_url and EUR amount if applicable.
Essential RETSHIP macros
Four macro agents.
RETSHIP-PAY-01
"Return change of mind: return fees [amount] € at your expense [label_type]. Details: [policy_url]#shipping-fees. Free threshold: orders > [free_return_threshold] €. "
RETSHIP-DEFECT-01
"Defective product: prepaid return label after photo proof. Send photos of product + packaging. Label link within 24 hours. "
RETSHIP-DEDUCT-01
"Product refund [product_refund] € minus return fees [ship_fee] € = [net_refund] €. Confirmed before portal validation. "
RETSHIP-STORE-01
"Free in-store drop-off: [store_dropoff_free locations]. Postal return: [amount] € depending on policy. "
Edge cases: damaged parcel, gift and B2B
Four cases outside the standard macro.
Damaged package in transit: #363 merchant pays for claim return
Gift return: #459 recipient fees according to policy
International return: #379 customs cost + shipping
Partial bundle: #185 return fees per package or single
Each market + return_reason requires a RETSHIP-MAP line aligned with the public returns page.
Essential ret_ship KPIs
Five RETSHIP steering metrics.
ret_ship_ticket_rate: tickets / initiated returns
ret_ship_dispute_rate: fee disputes / returns
ret_ship_free_claim_rate: ret_ship_free_claim tickets
ret_ship_defect_label_sla: free defect label hours
ret_ship_abandon_rate: RMAs abandoned after fees displayed
Target: ret_ship_dispute_rate < 3% after explicit RETSHIP-DEDUCT-01 checkout and portal.
RETSHIP anti-patterns
Five common mistakes.
Promising free return without map: NO-FREE-PROMISE
Deducting refund without warning: DEDUCT-EXPLICIT
Confusing restocking and shipping: cite distinct policy line
Defect without proof auto free: DEFECT-PROOF workflow
Duplicating entire return guide: #509 = shipping fees only
RETSHIP with Qstomy
Qstomy on Shopify + Loop/Returnly: RETSHIP-MAP lookup by order market reason, macros PAY grounded, defect photo collect, handoff dispute, reroute #510 bot tier 1 who pays.
Pipeline: #509 agents exception defect → #510 bot who pays pre-RMA tier 1.
Explore AI support and request a demo.
Checklist, FAQ and going further
RETSHIP Checklist (8 steps)
RETSHIP-MAP v1: reason market pays amount label type
RETSHIP-SUP Policy: 6 legal review rules
8 ret_ship_* typologies: helpdesk tags
4 RETSHIP-* macros: PAY DEFECT DEDUCT STORE
Returns page fees section: policy_url #shipping-fees
Portal displays fees before RMA: deduct preview EUR
Training defect vs mind 20 min: DEFECT-PROOF workflow
KPI Dashboard: ret_ship_* section 9
FAQ
Difference returning guide?
Guide = complete RMA workflow. #509 = return shipping cost and exceptions.
Defective product, does the customer pay?
Often no if DEFECT-PROOF is validated. RETSHIP-DEFECT-01.
Is Bot #510 enough?
Tier 1 who pays and amount. Defect dispute → agents #509.
International return?
Reroute #379. RETSHIP-MAP market EU/UK/US.
Going further
p: Returns guide
This week: audit returns page vs RETSHIP-MAP, test RETSHIP-DEDUCT-01 on 5 RMAs, measure ret_ship_dispute_rate baseline.
Enzo
July 1, 2026
