Cross-Border Returns: The Legal Side of Selling to Other EU Countries

Selling across the EU border is the easy part — PrestaShop will happily take an order from Lisbon, Lyon or Leipzig with the same checkout. The hard part arrives when that customer wants to send the product back. A domestic return is a logistics task. A cross-border return is a logistics task wrapped in a legal question: whose consumer law applies, in which language you owe information, what happens to the VAT you already collected, and who eats the shipping when the parcel has to cross a frontier. Get those wrong and a routine refund turns into a chargeback, a complaint to a foreign consumer authority, or a VAT figure that no longer reconciles.

This guide is strictly about the cross-border layer — the things that only become true once buyer and seller sit in different member states. The baseline mechanics that apply to every EU sale (the 14-day window, who pays return shipping, the exempt product categories, refund deadlines) are covered once, properly, in distance selling and the right of withdrawal. If you only want the rules in plain language, start there; this post assumes them and goes after the international complications PrestaShop merchants actually trip over.

Which country's law binds you — and why it isn't yours

The instinct is to assume your own country's rules govern your store. For cross-border B2C sales, they usually don't. Under the Rome I Regulation and the Brussels I bis Regulation, when you direct your commercial activity at consumers in another member state — and a translated storefront, local-currency pricing, a local delivery option or country-targeted ads all count as "directing" — the consumer keeps the protection of their own country's mandatory consumer law, and can sue in their own courts.

So what does that mean for you? The 14-day withdrawal right is harmonised across the EU under the Consumer Rights Directive, so for ordinary distance sales the core cooling-off period is the same everywhere — member states cannot generally impose a longer default window for the same harmonised scope. But national rules can still add information duties, enforcement practice and local formalities in some areas — a mandatory model form in the local language, stricter rules on who pays return postage — and where they do, that standard is the one that applies to that customer. You cannot contract out of it in your terms. Practically: build your returns policy to the most protective market you sell into, not to the bare EU floor, because in those areas the floor is the minimum, not the ceiling.

The language obligation most stores miss

This is the cross-border trap that catches careful merchants. EU law requires the pre-purchase information — the withdrawal right, the deadline, the model withdrawal form, who pays return shipping, any exemptions — to reach the customer in a clear and comprehensible form. There is no single EU-wide rule that every targeted consumer must receive it in their own official language, but several member states require or strongly enforce local-language consumer information, so serving it in the customer's language is usually the safest compliance approach and may be required by national law. A French consumer authority can act on missing French-language information; an Italian one can act on Italian-language gaps.

The penalty for getting this wrong is not a slap on the wrist. If the withdrawal information is missing or not properly communicated, the 14-day window extends to 12 months plus 14 days — and that extension applies per customer, in whichever language you failed to serve. A single untranslated returns page can leave you holding a year-long return liability across an entire market.

In PrestaShop this is a configuration job, not a copywriting afterthought. Each language you sell in is a real entity under International → Localization → Languages, and your CMS pages, product texts and email templates are all stored per-language. The work:

• Translate the returns CMS page for every active language, not just English. A page that falls back to the default language for a French customer is exactly the gap that extends the window.
• Localise the order-confirmation and withdrawal emails under International → Translations → Email translations, because the confirmation email is the durable record proving you informed the customer.
• Include a model withdrawal form per language — Germany's Widerrufsformular is practically expected by German consumers, and a downloadable per-language PDF closes the obligation cleanly.

The deeper point about translated legal content sits in our terms and conditions guide; here the practical rule is narrow — if you direct sales at a market, serving that market's consumers their return rights in their own language is the safest course, and national law or consumer authorities may require it.

The VAT twist nobody warns you about

Here is where cross-border returns stop being a customer-service problem and become an accounting one. When you sell B2C across borders under the OSS scheme, you charge the destination country's VAT rate — 20% to a French buyer, 19% to a German one, 23% to an Irish one — and report it in your One-Stop-Shop return. When that order is refunded, you are not just giving money back; you are reversing a tax liability you already declared in a specific country, at a specific rate, for a specific reporting period. (If OSS is new to you, the mechanics live in VAT in the EU: OSS and IOSS.)

The mistake merchants make is refunding the gross amount with a manual transaction and no tax document, which quietly breaks the VAT trail. The correct instrument is a credit note (corrective invoice) that mirrors the original — same destination country, same VAT rate, negative amounts — so the reversed VAT lands in the right country and the right OSS period.

PrestaShop's native flow generates a credit slip (the OrderSlip object) when you refund from the order screen, and you'll find them all under Orders → Credit Slips. That covers the basics. What it does not do well for cross-border sellers is treat the credit slip as a properly numbered, compliant corrective invoice with its own legal numbering sequence and the destination-VAT breakdown an accountant or an OSS reconciliation needs.

This is the one place a module earns its keep on cross-border returns specifically. Our Financial Revolution module issues corrective invoices tied to the original order, keeps a clean correction numbering series, and produces per-country VAT and tax reports from the back office — so when a refunded French order has to reduce your French OSS line for the quarter, the document and the number already exist instead of being reconstructed by hand at filing time. So what does that mean for you? Refunds stop being the thing that makes your VAT return fail to reconcile, and a cross-border refund leaves the same audit trail as a domestic one. The legal numbering reasons behind this are in invoice customization and legal requirements and e-invoicing across Europe.

Refund mechanics: same deadline, harder clock

The deadline is the EU baseline — refund within 14 days of being notified, and you may withhold until the goods arrive or the customer proves dispatch. What changes across a border is the clock you can rely on. A parcel returning from Spain to a German warehouse can sit in transit for a week, so the "withhold until received" right is worth far more internationally than domestically — but only if you wrote it into your terms. If you didn't, you may owe the refund before the box is back on your shelf.

Two cross-border refinements worth building into your policy:

• State that you may withhold the refund until the goods are received or the customer provides proof of dispatch, whichever happens first — and say so explicitly. The Consumer Rights Directive lets you do this, and it protects you from the genuine multi-day transit risk that domestic sellers never face. Note that proof of dispatch does not restart a fresh 14-day clock; it simply lifts the right to withhold, and your refund deadline still runs from the customer's withdrawal notice.
• Refund in the original currency, to the original payment method. If you display prices in local currencies, the customer paid in theirs; refunding in yours and pushing an FX conversion onto them is a dispute waiting to happen. Currency-of-display is a front-office setting — our price display rules guide covers how that and the net/gross presentation should look per market.

Return logistics across a frontier

Cross-border return postage is where the customer-experience and the cost arithmetic collide. International return shipping is materially more expensive and slower than domestic, which makes the "who pays" decision — legal in either direction provided you disclosed it before purchase — a real strategic lever rather than a formality.

Whichever you choose, the disclosure rule is unforgiving: if you want the customer to bear return postage, it must be stated before purchase in their language, or you pay it by default. The general process of running returns cleanly inside PrestaShop — the back-office steps, inspection, restocking — is covered in returns and refunds: making the process painless, and the policy strategy (extended windows, free returns as a conversion tool) in returns policy: law versus what smart stores offer.

Turning on the native return system the right way

PrestaShop ships a merchandise-return (RMA) system that handles the cross-border self-service flow well, because it lets a customer in any market request a return from their own account in their own language. It is off by default. Enable and tune it under Customer Service → Merchandise Returns, in the RMA options block:

• Enable returns (the PS_ORDER_RETURN setting). Until this is on, the "Return items" action never appears in the customer's order history — the most common reason merchants think PrestaShop "has no returns feature".
• Set the return period (PS_ORDER_RETURN_NB_DAYS). Set it to the most generous window you offer across your markets, not the 14-day floor, so no individual country's longer right is silently undercut by your own configuration.

When a customer files a request it becomes an OrderReturn record you approve from Customer Service → Merchandise Returns, moving through states (waiting for confirmation, package received, return completed) that give the customer a status without a single support email. Note one limitation that bites cross-border digital sellers: native returns are disabled for virtual orders. Downloaded content may be exempt from the withdrawal right, but only if the required conditions are met — the customer's prior express consent to immediate performance and their acknowledgement that they lose the right of withdrawal once delivery begins. Where you haven't captured that consent and acknowledgement, withdrawal rights can still apply to digital goods, and a mixed cart of physical and digital items needs a hand check regardless.

Country gotchas worth pricing in

The harmonised floor hides real national differences in how aggressively rights are exercised and enforced. Treat these as planning inputs for your most-shipped destinations, not legal advice:

• Germany. The most return-active market and the most consumer-protective in interpretation. The Widerrufsformular is expected, and German buyers are entitled to inspect goods as a shop customer would — opened and tested is still returnable. Fashion return rates running very high are a known reality here; price it into German margins rather than being surprised by it.
• France. The droit de rétractation is the 14-day baseline, but information owed in French is taken seriously, and France layers additional consumer-protection rules beyond the directive.
• Italy. Standard 14 days, but the consumer-protection authority is an active enforcer — the gap that gets penalised is usually missing or poor Italian-language legal information.
• Netherlands. Well-informed, rights-aware buyers who escalate to consumer bodies quickly if a return is mishandled. Process speed and clarity matter more here than almost anywhere.

Prevent the return before it crosses back

Every cross-border return you avoid saves two international shipping legs and a VAT correction, so prevention pays roughly double what it does domestically. The levers are the ordinary ones, applied with international buyers in mind:

• Accurate descriptions and sizing, localised — a size chart in centimetres is worthless to a customer who shops in another country's sizing convention.
• Honest delivery expectations. "Arrived too late" is a common cross-border cancellation; showing realistic per-market transit times with our estimated delivery date module keeps the promise honest before the order is placed.
• B2B handled separately. The withdrawal right is a consumer protection — it does not apply to genuine business buyers. A verified VAT number is strong evidence of business status, but not conclusive on its own: some businesses have no VAT number, so back it with account approval, company details and contractual terms. How to capture and validate it sits in B2B e-commerce with PrestaShop.

Track return rate by country in your reporting and watch for a market that returns far more than the others — that is rarely a "difficult customer" and almost always a fixable signal: a sizing convention you mistranslated, a delivery promise you couldn't keep, or a product page that read differently after translation.

Cross-border returns reward the boring virtues. Build the policy to your most protective market, serve every market its return rights in its own language, reserve the right to withhold the refund until the goods come back or the customer proves dispatch, and make sure each refund leaves a properly numbered, destination-VAT credit note behind it. Do that and selling into another EU country stops being a legal risk and goes back to being what the single market promised — just another order, even when it comes back.