A branded returns portal on your own domain — with the EU withdrawal flow (§356a BGB) built to spec alongside it. Pay once. Own it forever. No SaaS fees, no per-return charges.
Built to the §356a two-stage specification. Final legal wording confirmed by your own counsel — this page is not legal advice.
Most fashion SMEs handle returns through email threads and a spreadsheet. The customer waits days for a reply. Nobody on the team has full visibility. Refunds slip. Labels get generated by hand.
The tools that promise to fix this come with their own problems. They put your returns portal on their domain, so the customer leaves your brand mid-return. They're priced for enterprise — €150 to €340 a month, plus per-return fees that punish you for growing. And almost none of them meet the new EU requirement.
Because there's a second problem most brands haven't seen yet: from 19 June 2026, the amended Consumer Rights Directive (EU 2023/2673), transposed into German law as §356a BGB, requires every webshop selling to German consumers to provide a clearly labelled digital withdrawal button — a distinct legal mechanism, separate from the ordinary returns process. Most international returns apps were built around general returns UX. They don't have it.
That's two gaps in one. The operational gap, and the legal one. We close both.
The returns process and the legal withdrawal are two different things. We keep them separate — as the law intends — and run both from one branded portal on your own URL.
A normal, branded returns journey: customer selects items, gives a reason, uploads photos of the product condition (generous upload limits — not the 4-file cap the off-the-shelf apps impose), gets a carrier label, and tracks the return through to refund. Your team sees everything in one dashboard.
A separate, two-stage mechanism built to the §356a specification: the customer declares the withdrawal, then confirms it. A timestamped receipt is issued automatically, and every withdrawal is recorded in an audit log. This is the statutory right of withdrawal — no reason required from the customer — and it is kept distinct from the ordinary returns flow, exactly as the directive requires.
German-first, with an English toggle. Multi-carrier label generation for DHL, GLS, DPD and Hermes — the carriers European brands actually use, not just US ones. Everything lives on your domain. The customer never leaves your brand.
Important: the §356a withdrawal button is not the same as the §312k cancellation button for ongoing contracts. They are different legal obligations. We build the §356a withdrawal mechanism. We do not blur the two.
This page describes what the app does. The final legal wording shown to your customers is confirmed by your own legal counsel before launch. This is not legal advice.
The demo runs the full flow — the customer returns portal, the two-stage withdrawal mechanism, the audit log, and the staff dashboard. German by default, English on toggle.
It's a working demo, not screenshots. Click through it the way your customer would.
One price. Delivered in about two weeks, on your own domain. You own the code outright — no monthly fee, no per-return charge, no contract you have to fight your way out of later.
If you sell to German consumers, the withdrawal button isn't optional after that date. You can bolt on a niche German tool that only does withdrawal, keep paying monthly for a returns app that lives on someone else's domain — or have one portal that does both, on your domain, owned outright.
Built to the §356a spec — final legal wording confirmed by your counsel. Not legal advice.