Comparison · Native vs BackToMe
Is your platform's native feature enough?
Good news: some platforms have rolled out a native withdrawal button, activatable from the admin. It is a good starting point, and for the basic requirements it can do the job. But one point is essential: the native feature covers the display of the button; it does not update your terms and conditions, and rarely provides proof that holds up in a dispute. The button alone is not enough to be fully compliant.
The head-to-head, line by line
| Criterion | native | BackToMe |
|---|---|---|
| A visible button on the site | ||
| Label compliant with the applicable national text | covers the basics | |
| Acknowledgement of receipt by email (that the customer keeps) | depends on the platform | |
| Archiving that cannot be altered, that holds up in a dispute | rarely provided | |
| Retained for 5 years, hosted in France | ||
| Monitoring: alert if the button disappears | ||
| Follows you if you change platform | lost on migration | |
| Works on all your platforms from one account | a single platform | |
| Explicit grounding in the applicable consumer law (Directive 2011/83/EU) | framing often generic | |
| Installation | admin activation | 5 minutes |
| Cost | often included | 25 € excl. VAT/month |
Comparison at the level of the category of solution, not a named product. Established from the criteria of Directive (EU) 2023/2673 and Directive 2011/83/EU and common practice; subject to change.
When native can be enough
- •You are settled on this platform for the long term and do not plan to change.
- •You only need the basic button and you manage your terms and pre-contractual information yourself.
- •You accept not having proof that cannot be altered in the event of a dispute.
- •The platform explicitly commits to keeping the feature up to date with the applicable consumer law.
When you need BackToMe
- You want proof that holds up, not just a button that shows.
- You have several sites, or you might change platform one day.
- You want dated archiving kept for 5 years, hosted in France.
- You want to be monitored (alert if the button disappears after a theme update).
The verdict
The native feature is a good start, and if your platform offers it, turn it on. But it covers the display, not the proof: on the day of a dispute or an inspection, it is the proof that holds up that protects you. BackToMe adds that proof, the monitoring, the portability between platforms and the explicit grounding in the applicable consumer law, for 25 € excl. VAT/month.
Frequently asked questions
Does my platform's native button make me compliant?
It covers the basic requirements (the button shows). But compliance with the European obligation (EU Directive 2023/2673) does not stop there: your terms and pre-contractual information must mention the feature and stay consistent, and you have every interest in holding proof that stands up for each request. The native button generally handles neither the proof that cannot be altered, nor long-term retention, nor your terms.
What happens if I change platform?
The native feature is tied to the platform: on migrating, you lose it and have to start from scratch. BackToMe is platform-independent (a line of code in the <head>): you re-lay it on the new site in five minutes, and your history of proofs stays intact.
Can I use native AND BackToMe?
It is not necessary: BackToMe covers the button and the proof. If you keep the native button, take care not to show the visitor two competing buttons. Most merchants simply replace native with BackToMe to have the proof and the portability.