Download websites that use Ordergroove

About Ordergroove

Subscription commerce splits the retail world into two groups, and the split is more informative than most technology signals. A store that installs Ordergroove has decided that its products are consumed and replaced on a predictable cycle, that its customers will accept a standing order, and that recurring revenue is worth rebuilding a checkout for. Coffee, supplements, pet food, cosmetics and household consumables generally qualify. A furniture retailer does not. As of October 2026 we detect Ordergroove on 89 sites.

What that implies about the merchant is unusually specific. Recurring billing brings requirements that a single purchase checkout never raises: card updating, dunning, pause and skip flows, subscriber portals, churn reporting. A retailer that has taken those on is operating at a size where the engineering cost was justified, and is measuring lifetime value rather than order count. Detecting Ordergroove on a domain is therefore a proxy for a mid market or larger merchant with a retention function, a far narrower population than a list of stores that merely accept payments.

The platform is written in JavaScript and runs in the browser, which shapes both what we can see and how the count should be read. Client side integrations leave evidence a crawler can record, so a subscription widget that loads on a page is detectable. The catch is where it loads. Subscription options usually appear on product detail pages rather than on a front page, so a crawl that samples the front of a site will miss merchants who are genuinely running the platform. Read the total as a floor.

The commercial reading follows from that. If you sell payments, retention analytics, fulfilment, packaging or support tooling, a subscription merchant is a better prospect than an ordinary store, because the recurring model creates operational problems ordinary stores do not have. If you compete in subscription commerce, the same file is a displacement list with the qualification already done. And if the market itself is the research subject, a hostname level list lets you measure which retail categories have actually adopted recurring purchase rather than which ones the vendors say have.

Ordergroove has been available since 2010 and is Proprietary, so there is no public deployment record to check our figure against and no version signal to date individual installs. What the dataset offers instead is breadth and verifiability: every domain in the file is a site where the integration was observed, and the file can be joined against the rest of a merchant's stack to see what a subscription retailer runs alongside it.