How-to · 8 min read
How to find every app a Shopify store uses
Every Shopify store is a stack of decisions, and most of those decisions are apps. Reviews, email, subscriptions, upsells, page builders, analytics — the apps a store installs are the clearest public signal of how it actually runs. This guide covers how to find them, why detection sometimes comes up short, and — the part most people skip — how to read the list once you have it.
The fastest way: scan the store
Paste the store's URL into the theme detector, then click "Check the apps on this store." Within a few seconds you get back the apps it found, grouped by category, each with its logo so you can scan the stack visually rather than reading a list line by line.
Behind the scenes, detection works by reading the store's public source code and matching it against known fingerprints — the scripts, styles and tracking snippets that each app leaves behind. ThemeScope currently recognises more than 79 apps across 15 categories, from the big names (Klaviyo, Judge.me, ReCharge) to fulfilment tools (Printful, Printify, DSers) and analytics layers (Triple Whale, Lucky Orange, the Meta and TikTok pixels). The wider the fingerprint library, the more of a store's real stack you see.
Find a store's apps
Scan any store and hit "Check the apps".
The slower way: read the source yourself
If you want to verify a result or hunt for something a detector missed, you can read the source directly. Right-click the store and choose "View page source," then search (Ctrl+F) for tell-tale strings — an app's name, or the domain its script loads from. If you see klaviyo.com in a script tag, Klaviyo is installed. It's slower and you need to know what to look for, but it's how detection works under the hood, and it's a useful cross-check.
Why some apps don't show up
This is the part worth understanding, because it stops you drawing the wrong conclusion from an empty result. Detection can only see apps that leave a public trace. Three cases where an app is present but invisible:
- Custom-built functionality. A store that coded its own subscription system instead of installing one won't show a subscription app — the feature exists, but there's no third-party fingerprint to detect.
- Server-side or "headless" setups. Some larger stores run logic on their own servers, so the browser never sees the app's code.
- Apps that genuinely leave no footprint. A few back-office apps (inventory, accounting) don't touch the storefront at all.
So "no apps detected" doesn't mean "no apps." It means none that leave a public trace — which, for a very custom store, is itself a signal that they've invested in bespoke development.
Every app a detector reports is genuinely there. But the reverse isn't true — absence of a fingerprint isn't proof of absence.
How to actually read an app stack
A list of apps is just trivia until you interpret it. The trick is to look at clusters and gaps, not individual apps.
- Where's the density? Three review apps means a store obsessed with social proof. Four page-builder and upsell apps means a store focused on squeezing more from each visit. The heaviest category tells you where the store is spending its energy.
- What's the business model? Subscription apps mean recurring revenue. Print-on-demand and dropshipping apps mean no held inventory. Those two stores need completely different playbooks — and the apps give the model away instantly.
- What's missing? A high-traffic store with no email app is a genuine surprise — maybe they built something custom, maybe it's a real gap. Either way, the absence is interesting.
Turning it into action
The point of reading a competitor's stack is to find things worth testing on your own store. If three strong competitors all run the same category of app and you don't, that's your first experiment. If one outlier store runs something unusual and it's clearly winning, that's worth a closer look. Don't copy a stack wholesale — a maxed-out store isn't automatically a better one — but let the patterns point you at what to try.
Keep reading: read a competitor's whole growth strategy from its apps, or what a store's theme reveals about its strategy.