Shopify Detector & Spy vs Shopify Spy and Koala Inspector
Compare public catalog research and JSON/CSV exports with Shopify Scraper & Parser and Koala, then inspect the output from the same collection.
If a Shopify export leaves you fixing identifiers, looking for missing variants, or guessing which collection it captured, another download is only useful if you can check its quality.
Shopify Detector & Spy is my extension for detecting Shopify storefronts and inspecting public competitor catalogs. Its version 1.0.4 build offers direct JSON and CSV downloads plus an Excel workbook inside the ZIP. Here is how its documented workflow compares with Shopify Scraper & Parser — Shopify Spy and Shopify Spy Tool & Sales Tracker for Dropshipping — Koala Inspector.
I build Shopify Detector & Spy. Its features here follow the version 1.0.4 source documentation; the store listing may still show the earlier name. Competing features use public listings checked on 29 October 2026, not a controlled head-to-head runtime benchmark. It does not establish that either competing extension fails on a particular store.
Distinguish the products behind similar Shopify Spy names
My Shopify Detector & Spy is separate from Shopify Scraper & Parser — Shopify Spy and Koala Inspector. The word “spy” in my extension refers to inspecting public catalog data; it does not mean sales estimates, private-store access, or theme/app detection.
Shopify Scraper & Parser — Shopify Spy describes a product-export workflow with CSV and XLSX, collection filtering, single-product downloads, image downloads, and additional fields through a slower extraction mode. Its listing also advertises a Shopify-compatible import format and an undocked scraping workflow.
Koala Inspector describes a broader store-research product: app and theme detection, product research, estimated sales and traffic, advertising intelligence, monitoring, and CSV exports. Its listing identifies sales and traffic figures as estimates rather than verified merchant measurements.
Those descriptions establish advertised workflows. They do not establish the accuracy or completeness of an export from your intended source.
Compare by the deliverable you need
| Requirement | Shopify Detector & Spy | Shopify Scraper & Parser | Koala Inspector |
|---|---|---|---|
| Main job | Shopify detection and public competitor catalog research | Product scraping and export | Broader store and competitor research |
| File output | Direct JSON and CSV; text-typed Excel inside ZIP in v1.0.4 | CSV and XLSX advertised | CSV export advertised |
| Scope workflow | Website, current product/collection, discovered collections | Collection filtering and single-product export advertised | Store/product research described |
| Media | Image links and associations | Image downloads advertised | Product research; verify required export fields |
| Sales or traffic estimates | Not provided | Not assessed in this comparison | Advertised as estimates |
| Long-running workflow | Keep popup open; restore saved progress | Undocked scraping advertised | Monitoring advertised, depending on plan |
The competing-product columns summarize their linked listings. Confirm plan access and current behavior before relying on any feature.
Choose a broad research suite if you need technology detection or estimated demand signals. Choose a catalog exporter when the next task is reviewing products, variants, and source values in a file.
Where Shopify Detector & Spy fits
Shopify Detector & Spy keeps catalog records on your device, exposes separate scope counts, and lets you preview captured products before downloading. Its ZIP includes the catalog, image-link table, normalized JSON, and a manifest describing source scope and coverage.
The spreadsheet workbook stores literal catalog values as text. Missing data stays unknown; public availability is not converted into actual stock quantity. This is useful when you want to inspect an export's evidence before preparing it for another workflow.
Shopify Detector & Spy exports observed source data. It does not create a ready-to-import native Shopify catalog automatically, download image binaries, or claim revenue estimates. If you need those jobs, assess them separately rather than assuming every exporter is interchangeable.
Run the same acceptance check on every tool
Choose a public collection small enough to review, record its exact URL, and capture it near the same time in each product. Keep the original downloads.
Check these points:
- Does each file identify the same store and collection?
- Do several selected products retain all returned variant identities?
- Are leading-zero SKUs and long IDs unchanged after opening the file?
- Are gallery links associated with the correct product?
- Is currency stated with a clear source or left unknown?
- Does the result explain limits, incomplete pagination, or blocked access?
A product count alone cannot answer all six questions. The export-quality guide gives you a more detailed worksheet.
What if your current exporter is not working?
Record the source URL, chosen scope, symptom, and capture date before switching tools. A difference may come from scope, source access, pagination, file interpretation, or the implementation itself.
The troubleshooting guide helps isolate those cases. It gives you a useful comparison record without needing to assume the cause in advance.
Try Shopify Detector & Spy on a real task
The Free plan includes 100 captured products per UTC month in the browser profile. Pro removes the monthly product quota and has no fixed product or variant cap per run. Browser memory, storage and source access can still limit coverage. Review current terms in the Shopify Detector & Spy listing.
For a local catalog export, start with Shopify Detector & Spy and compare one collection against the worksheet. Keep the tool whose output meets the requirements you can actually verify.