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
Beta · In testingSee 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.
The Chrome extension is being prepared for launch. Public downloads are not available here yet. See Beta access below for details, including how to connect an existing test installation.
Already have the test extension? Sign in to Ecomwith and connect it from your store archive.
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.
From browsing to saved research
01
Inspect with the test extension
With the extension installed, 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.
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.
BETA ACCESS
Beta access
Public access to the Chrome extension will be provided here. We are preparing for launch; downloads are not available yet. For now, explore what it checks and how it works.
If you already have the test extension installed, open your Ecomwith store archive to create a pairing token and manage records you send. Signing in alone does not install the extension or scan a store.