Download websites that use Shopatron

About Shopatron

The fingerprint carries one name and the vendor field carries another, and the distance between those two facts is the first thing worth explaining about this record. Shopatron is what we detect on the page. Kibo Commerce is who owns the technology today. A brand absorbed into a larger commerce suite keeps turning up in markup long after the sales material stops mentioning it, and the lag is exactly what makes the detection useful to somebody studying the market.

The underlying product solved a problem specific to manufacturers who sell through dealers. An order placed on a brand's own website has to be fulfilled from somewhere, and routing it to a nearby retail partner instead of a central warehouse stops the dealer network from treating the brand's site as a competitor for its own customers. Software that arbitrates between ecommerce and a physical distribution network sits in an awkward place, which is why our catalogue files it under Ecommerce even though most of the interesting work happens after checkout rather than before it. Order routing of that kind is also a signal about the business behind the website, because only a company with a physical distribution network underneath it has any reason to buy the capability.

Age is the other half of the story. The platform dates to 2001 and the license is Proprietary, so a deployment still visible now has survived an acquisition, at least one generation of ecommerce replatforming and the general tendency of retail technology to be ripped out and replaced every few years. As of October 2026 we record Shopatron on 5 sites. A count that small, attached to a product with that history, fits a long tail of installations that were never fully migrated rather than a stream of new sales. Nothing in the record exposes a version string either, so an ageing install and a maintained one look identical from outside.

Which leads to the caveat any serious user of this data needs to carry. A detection proves that markup, a script reference or a routing endpoint associated with the platform is still being served. Detection does not prove that orders still flow through it. Some of these pages are working integrations and some are archaeology left behind by a migration that finished everywhere except one template, and separating the two means looking at the sites themselves.

The list is worth having anyway, for a reason no domain-by-domain check can serve. Anyone selling order management, anyone doing migration work, anyone studying how an acquired platform decays inside its buyer's stack has to start from the population and qualify downwards. Start from the technology, take the sites, then verify by hand. Starting from a domain assumes you already knew which domain to ask about, which is the part the dataset is actually for.