Coverage
Which shops we can scan
Price Gap extracts competitor catalog data from Shopify, WooCommerce, OpenCart, Magento, PrestaShop, Shopware, and most custom shops that embed Schema.org Product markup. This page lays out exactly how each platform is handled, what we can’t reach today, and how to test your own shop in under a minute.
Fully supported platforms
Native API
Shopify
Reads /products.json directly, then fetches each product page for GTIN backfill (in Deep scan). Highest GTIN coverage of any platform. Verified on catalogs with 500+ products at full extraction.
Native API
WooCommerce
Uses the public Store API at /wp-json/wc/store/v1/products. Most modern WC installs expose this. Shops that disable it for security automatically fall through to the universal HTML extractor.
HTML + ld+json
Magento
Detected via Magento-specific markers (Mage.Cookies, data-mage-init, generator meta). Extraction reads the sitemap declared in robots.txt and parses Product schema from each page. Verified on a German watch retailer at 100% SKU coverage.
HTML + ld+json
PrestaShop
Same universal HTML+ld+json pipeline. PrestaShop’s own Web Service API is locked down on ~95% of installs, so we skip it entirely and go straight to sitemap-based discovery.
HTML + ld+json
Shopware
Detected via the application-name meta tag and Frontend theme paths. Extraction runs through the same sitemap → product page → ld+json path as Magento and PrestaShop.
Category-grid crawl
OpenCart
No product API, and most OpenCart shops ship an empty sitemap - so we walk the paginated category pages and read name, price, and SKU straight from the product grid. Verified on a real shop at 3,500+ products, 100% SKU. Heavily customized themes may need extra selectors.
HTML + ld+json
Custom / unknown
Any server-rendered shop with a sitemap and ld+json Product markup works. We don’t care if you built it on a custom CMS, a static site generator, or something we’ve never heard of - if Google can index your products, we can read their prices.
Known limits
These shop patterns don’t currently produce usable data - we surface the reason clearly in the extraction QA panel instead of returning empty results.
- JavaScript-rendered SPAs.Single-page apps built on Vue, React, or Angular with no server-side rendering ship empty HTML - the actual product details load client-side after the page mounts. ld+json arrives empty, so we can’t extract. A headless-browser fallback (Puppeteer / Vercel Sandbox) is on the roadmap for Pro tier.
- B2B “price on request” shops. Prices live behind a login or quote form. The catalog extracts fine but every price is 0, so matching produces no meaningful gaps. Customer-supplied data feeds (Google Shopping XML, custom CSV) will be a future option for Enterprise tier.
- Login-protected catalogs. Wholesale portals, dealer-only sites, password-gated previews. Treated identically to B2B above - fundamentally requires the shop owner to provide credentials, which is an Enterprise-only flow.
- Aggressive bot protection.Some shops run Cloudflare Bot Management, Akamai, or DataDome at maximum sensitivity and block any non-human traffic. SlimFit’s shared cache layer minimizes the footprint each shop sees from us, but a few will still refuse. The dashboard shows the exact HTTP code that came back so you know whether to retry or move on.
Is your shop supported?
The fastest answer: paste your shop URL in the analyze form and run a scan. The Extraction quality panel will tell you exactly what we found - the platform we detected, how many products we could read, GTIN/SKU coverage, and a clear error message if something blocked us.
The first scan of any new shop pays the full extraction cost; subsequent scans (for you or any other user) come from the shared shop-cache for the rest of the UTC day.
What’s next
- Headless-browser fallback - Puppeteer with Vercel Sandbox for JS-rendered SPAs. Pro tier.
- Customer-provided data feeds- Google Shopping XML and CSV upload paths so Enterprise customers can analyze any shop they control. Doesn’t need scraping.
- BigCommerce + Squarespace - both expose clean public APIs; dedicated extractors land when ICP demand justifies the work.
- Variation-level WooCommerce extraction - size, color, and other variant axes; currently we only read the simple-product parent.