The withdrawal button is as much an integration question as an interface one

Since 19 June 2026, selling to consumers online comes with a new requirement: a withdrawal button — a clear function on your site that lets a customer cancel a purchase as easily as they made it, without logging in or hunting for a contact form.

It's tempting to read that as a front-end task: add a button, done. But the button is only the trigger. Behind it, a single cancellation has to move through every system that handled the original order: the payment provider that issues the refund, the stock that goes back on the shelf, the ERP that holds the order, the logistics that may already be shipping it. The button is easy to build. Making that chain respond cleanly every time is where the complexity shows up.

What has changed?

The shortest possible answer: the right of withdrawal itself hasn't changed. Your customer still has 14 days to cancel a purchase, counted from the day the goods are delivered. You still handle returns and refunds exactly as before.

What's new isn't which right the customer has, but how easy it should be to use. The idea behind the law is simple: cancelling a purchase should be just as easy as making it. No contact form buried at the bottom of the page, no email address to hunt for. A clear function, in the same place where the purchase was made.

The rules come from an EU directive and have been implemented in Swedish law through changes to the Distance Contracts Act (distansavtalslagen, proposition 2025/26:84, "Stronger consumer protection in distance contracts"). The Swedish Consumer Agency (Konsumentverket) is the supervisory authority.

What does the law require?

It's easy to read "withdrawal button" and assume a button in the checkout will do. In practice, there are four requirements, and they all have to be met at once:

• Findable. The function has to be easy to locate and available throughout the entire withdrawal period, on the same website or in the same app where the contract was made.

• Understandable. It has to be clearly and legibly labelled, for example, "cancel your order here." The customer should understand what the button does.

• Tied to the right purchase. The customer has to be able to state or confirm which contract it concerns without needing to log in.

• Acknowledged automatically. When the customer cancels, they should receive an acknowledgment of receipt confirming the request has been registered. Automatically, in a readable electronic format.

It's that last requirement that's most often underestimated, and it's where a button on the page stops being enough.

What does the requirement touch beyond the interface?

The withdrawal button is one thing in the interface, but the requirement affects the whole flow behind the scenes. Think through what actually has to happen when a customer clicks:

• The request has to be registered and acknowledged automatically.

• The order has to be flagged or cancelled in your ERP.

• The refund has to be initiated with your payment provider.

• The item has to go back into your stock count.

• Logistics may need to be stopped if a shipment is already on its way.

• And all of it has to be documented and traceable afterwards.

If you run a standard e-commerce platform, some of this can be handled with an add-on. If you have a more custom setup or several systems that need to talk to each other, it often turns out bigger than it first looks. The real challenge lies in whether your whole chain of systems can handle what the button sets in motion.

What triggers an extended withdrawal period?

There's one consequence merchants should be particularly aware of. If you don't inform the customer about the withdrawal function and how it's used, the withdrawal period is extended automatically.

That means a half-finished solution doesn't just risk a remark from Konsumentverket. It can create a drawn-out period of liability you won't discover until there's a dispute. Getting both the function and the information right protects both you and your customer.

Who does the requirement apply to?

The requirement reaches most businesses selling goods or services to consumers via a website or app, where the purchase is already covered by the right of withdrawal today. That includes physical products, digital services, and subscriptions.

But not everything is covered by the right of withdrawal; some purchases are exempt, and those exemptions aren't changed by the new law. The law doesn't create any new withdrawal rights; it makes the existing right easier to use. If you're unsure whether your products are covered, it's worth sorting out before you start building.

Where does Junipeer fit in?

Junipeer doesn't sell the withdrawal button. The button itself belongs in your e-commerce platform or checkout.

What we do is what happens after the click. Junipeer is an integration platform built for Nordic e-commerce, connecting your e-commerce platform, ERP, payment providers, PIM, POS, and logistics. When a withdrawal request comes in, that's exactly the kind of flow that should run automatically and traceably across every system, so that refund, stock count, and ERP don't fall out of sync and don't require manual cleanup.

In other words: if you're already wondering how the chain behind the button is supposed to hold together, that's the kind of problem we're built to solve. And if a simple plugin covers your needs, we'll tell you that too.

In short

• The right of withdrawal is unchanged. What's new is the requirement for a simple, digital function to use it.

• The function has to be findable, understandable, tied to the right purchase, and acknowledge the request automatically.

• The button is the easy part. The hard part is the flow behind it: refunds, stock, ERP, logistics, and traceability.

• Inform the customer — otherwise, the withdrawal period can be extended, in the worst case by up to a year.

• Not everything is covered by the right of withdrawal, but where it applies, it now has to be easy to use.

This is not legal advice. For how the rules apply to your specific business, check with Konsumentverket or a lawyer.

See it work across your systems

Wondering whether your systems can handle what the button sets in motion? Book a demo and we'll show you how Junipeer connects your store, ERP, payment providers and logistics — or start a free trial and try it yourself.

Book a demo · Start a free trial