Commerce platform
Identify public signals for Shopify, WooCommerce, BigCommerce, Wix, Squarespace and Webflow, with confidence levels. Insufficient evidence leaves the platform unknown.
STORE INSPECTOR · STOREFRONT RESEARCH
Chrome Extension · LiveSee what a store is built with.
Research another storefront or inspect your own. Check public platform, theme and app signals alongside product samples, then keep the findings and their sources in Ecomwith.
Store Inspector is live in the Chrome Web Store. Install it to inspect the public storefront open in your browser, then save only the records you choose when you want a research history in Ecomwith.
The extension works locally after installation. Sign in to Ecomwith only when you want to pair it and save records you explicitly send.
ECOMWITH / STORE ARCHIVE
Inside a saved record
Each record retains its capture time, page and sources.
Product sample
Names, links, public prices and image sources
Platform & theme
Findings, confidence and supporting evidence
Evidence & technology
Observed technology signals and their sources
Full JSON · Products CSV · Evidence CSV
What can you learn from a storefront?
Inspect the public store page open in your browser. Results depend on the platform, the page and the information it exposes.
Theme name and version
Read exposed Shopify theme details or WordPress theme asset paths on WooCommerce pages. Versions appear only when exposed; conflicting theme signals stay unresolved.
Apps and technology signals
Match known technology signatures in public scripts and stylesheets, review sources and confidence, and count page scripts. Findings are not a complete list of installed apps.
Product and price samples
Review captured names, links, public prices, currencies and images. Shopify and WooCommerce scans can also try public catalog endpoints. Unavailable fields remain empty.
VERSION 0.6
Beyond one look: follow changes, keep a report
These features arrive with extension version 0.6. Everything will run in your browser, free and without an account. The AI shopping readiness guide below is already available.
Change timeline
For a store you choose to Watch, the extension keeps a compact record in this browser. Each later scan is compared with the previous one: theme, apps, published product count, same-currency prices and genuinely new products. Products moving in or out of the sample are only a hint, not proof of a launch or removal. There is no background checking; it updates only when you open the store and scan again, and you can delete or export the record at any time.
Evidence report
Create an HTML report (print it to PDF if you like), a Markdown file, or a brief you can paste into an AI assistant. It is built locally and never uploaded, and each finding carries its confidence and source.
AI shopping readiness
See which public signals the store exposes: UCP and ACP profiles, llms.txt, the robots.txt rules for AI crawlers, a sitemap and complete product markup. The result reads “observed N of M” and is never a score. Not observed does not mean unsupported.
Measured app weight
Reads the performance data your browser recorded for this one page load and assigns requests, measurable bytes and main-thread script time to the apps it recognised. It is not a speed score or a long-term average, and it does not estimate price or sales.
From browsing to saved research
01
Install the extension and inspect a store
Install from the Chrome Web Store, then open a public storefront for a light scan. Manually run a bounded deep scan when you need more product samples.
02
Choose what to save
Save locally or export JSON. To keep a record in your account, create a pairing token in Ecomwith, paste it into extension settings, then choose Send to Ecomwith.
03
Review and export
Review capture times, products and evidence in your Ecomwith store archive. Export JSON, products CSV or evidence CSV for product selection and competitor research.
New to the extension? The guide walks through a first scan, how to read each block of a result and three worked workflows. Read the Store Inspector guide
What these records can tell you
- Products are a public sample from that capture, not necessarily the full catalog. Prices reflect the page at capture time.
- Theme and technology findings retain their sources. Unconfirmed results stay unknown.
- Page signals do not establish sales, traffic or profit. Script count alone does not establish a performance problem.
You choose what to save
Only records you explicitly send reach your account. The extension excludes cookies, form values, customer data, carts, checkout, orders and payments. URL parameters are removed before saving. You can revoke a pairing token or delete an individual account record. Watch records and reports stay in this browser; the 0.6 watch history and report data are never included in a snapshot you send.
CHROME EXTENSION
Install from the Chrome Web Store
Store Inspector is available for public installation. It reads evidence exposed by the storefront you open and leaves unsupported findings unknown.
Already installed? Open your Ecomwith store archive to create a pairing token and manage records you explicitly send. Signing in does not scan pages or upload browsing history.