Download websites that use Returnly

About Returnly

Two names appear in this record where a technology row usually carries one. The product is Returnly and the vendor field reads Affirm, while the address we hold for the product now serves a notice that Returnly has been shut down and hands merchants to a different returns platform. A withdrawn product is a special case in detection data, because code installed on a merchant's site keeps answering long after the company behind it has stopped selling anything.

Returns tooling is post-purchase software, the part of an ecommerce stack that sits furthest from a homepage. A shopper reaches it from an order confirmation email or a small link in a footer, and the portal itself frequently lives on its own hostname. Our detection sees the pieces that touch a public storefront, which tilts any count toward shops that expose a returns flow openly and away from shops that keep the whole process behind a customer login.

As of October 2026 the fingerprint is present on 5 sites. A figure in that range for a returns product describes a tail rather than a market position. Integrations of this kind are removed slowly and incompletely. A merchant that has already migrated to another returns provider may still carry a leftover script tag, a stylesheet reference or a redirect rule from the previous one, so much of any count for a product that has been withdrawn is residue rather than active use, and separating the two takes a manual pass over the domains.

The record dates the product to 2014 and lists distribution as Proprietary, which together mean no public registry exists to check our count against. Proprietary ecommerce add-ons publish logo walls, not customer lists, and a logo wall is assembled for marketing rather than for completeness. Crawl detection is one of the few repeatable ways to see who actually has the code installed, and its bias runs opposite to the logo wall, being too inclusive rather than too flattering.

The combination of a decaying tail and no public registry is what makes a downloadable list worth more here than a per-domain check. Checking one merchant tells you what one merchant does today. A full list, joined against ecommerce platform, country and the rest of each shop's stack, shows which segment adopted returns automation early, which of those shops still carry code from a service that has stopped running, and which are therefore live candidates for a migration conversation. Competing vendors, payment providers watching post-purchase consolidation and analysts studying how quickly retired tooling gets replaced all want the same file, and each of them needs the caveats travelling with it.