--- title: Preventing Disputes | Shopware Community Hub description: >- Apply five prevention levers—descriptors, communication, returns, documentation, subscriptions—and monitor dispute rate trends in the Dashboard. canonical_url: 'https://hub.shopware.com/learn/unit/preventing-disputes' --- # Preventing Disputes - **Apply** the five high-return prevention levers—**descriptor clarity**, **communication**, **returns**, **documentation**, and **subscription self-service**. - **Reduce** "forgot to cancel" subscription disputes with clear customer paths and expectations. - **Explain** how **SCA** at checkout supports fraud defense without extra merchant configuration. - **Monitor** **dispute rate trends** in the **Merchant Dashboard** and escalate to **Shopware Support** when patterns shift. # Unit 5: Prevention Habits Most disputes are predictable. Not in the sense that you can see each one coming — but in the sense that the same five root causes generate the large majority of cases across merchants of all sizes. **Strum & Co.** ran their dispute report at the end of their first quarter and found a pattern: eight of their eleven disputes in that period were "item not received" cases — and six of those came from orders placed in the two weeks before Christmas. The carrier had been running three to four days late. Customers had not heard anything about the delay. When the package did not arrive on time, they assumed fraud and opened a case. Nothing was wrong with the product, the shipping, or the payment. The problem was silence during a known delay. This unit covers the five prevention levers that reduce dispute volume before cases are opened. --- ## Lever 1: Billing Descriptor Clarity When the name on the customer's bank statement does not match the shop they remember buying from, the first assumption is fraud — not a trading name they have not seen before. **What a weak descriptor looks like:** a parent company name, an abbreviated legal entity, or a generic string with no recognizable shop name. **What a strong descriptor looks like:** shop name + city + support contact. For example: `STRUM AND CO ESSEN +49 201 XXXXXXX` This is often a five-minute configuration change with a high return. Set it before you go live — not after your first "I don't recognize this charge" dispute. --- ## Lever 2: Proactive Order Communication When customers cannot get information about a delayed or missing order, they escalate — to **PayPal** or directly to their bank. The dispute is filed not because anything went wrong with the payment, but because communication stopped. **The prevention habit:** send proactive order status emails, especially when something is delayed. A single email saying "your order is running three to four days late due to carrier delays — here is your tracking link" eliminates a significant share of "item not received" disputes before the customer reaches the **Resolution Center**. > **Strum & Co.'s fix:** after identifying the Christmas pattern, they added an automated delay notification trigger in **Flow Builder** — when a shipment passes its estimated delivery date without a carrier scan update, a status email goes out automatically. "Item not received" disputes in the following quarter dropped by more than half. --- ## Lever 3: Frictionless Returns When returning is difficult, customers bypass the merchant entirely and go to their bank. The result is a "credit not processed" or "item not as described" dispute — more expensive and more time-consuming than a straightforward return would have been. **The prevention habit:** - Returns policy visible at checkout and in the order confirmation email — not buried in a footer - Return process that requires minimal steps from the customer - Refund processed promptly once the return is received — not held pending manual review A customer who can return easily does not need to dispute. --- ## Lever 4: Documentation Awareness Your strongest fraud defense is built into the checkout — you do not need to configure it, but you do need to know it exists. Every **Shopware Payments** card transaction captures: - **IP address** used at checkout - **Device and browser signals** - **Strong Customer Authentication (SCA) outcome** — runs automatically for card payments; the result is logged with the transaction These signals do not prevent disputes from being opened. They give you a factual record to submit when an "unauthorized transaction" claim arrives. Know how to access the transaction detail and authentication result before you need it. --- ## Lever 5: Subscription Cancellation If you offer subscriptions, "I forgot to cancel" is a significant source of "unauthorized transaction" disputes — not because the transaction was unauthorized, but because the customer felt they had no easy way out. **The prevention habit:** one-click cancel in the customer account. Visible, accessible, no support ticket required. Merchants who resist making cancellation easy typically see higher dispute rates and higher churn from customers who cancel through a bank dispute rather than through the shop. Making it easy to leave reduces the motivation to leave via dispute. --- ## Monitoring — Catch Trends Before They Become Fees Review your dispute rate in the **PayPal Merchant Dashboard** regularly — at least monthly, and weekly during peak seasons. A rising trend almost always has an upstream cause: | Trend | Common upstream cause | |-------|----------------------| | Spike in "item not received" | Carrier performance issue or delay without communication | | Spike in "not as described" | Product listing accuracy, photography, or quality issue | | Spike in "unauthorized" | Fraud pattern targeting your shop or checkout | | Spike in "credit not processed" | Returns process friction or refund processing delay | | General upward trend | Policy ambiguity or a new method with different customer expectations | Investigate early. A pattern identified in week two of a month is fixable before month-end fees arrive. A pattern identified at month-end is a post-mortem. If the cause is unclear after reviewing the **Resolution Center** data, contact **Shopware Support** with the transaction IDs and dispute reasons — they can help route the investigation. --- You now have the full Shopware Payments learning path—from platform evaluation through method strategy, daily operations, finance close, and dispute handling—and can return to any section when a real incident maps to that step.