What Fexlo works with - and what it does not
Last reviewed against Fexlo 0.10.1.
Supported
| Source | How Fexlo reads it | Notes |
|---|---|---|
Shopify-style stores with a public product list (/products.json) | Public catalogue files, paged, spaced requests, robots.txt respected, no cookies | Bulk Fetch and single-store extraction. Completeness is cross-checked against the sitemap when no filter is applied. |
| Web pages with repeated product cards or tables | Read from the tab you opened, after you click the toolbar button | Best effort, one page at a time. Accuracy depends on the page; Fexlo shows what it found and says when it is unsure. |
Not supported
Any website in Bulk Fetch that does not publish a public Shopify-style product list is shown as Skipped: not a supported source. Nothing is scraped from it.
What a store does not publish - and Fexlo therefore never invents
- Currency. Catalogue files carry prices without a currency. Prices are shown as published; Insights compares them only as published and says so.
- Stock quantities, low-stock and pre-order. Only available / not available is published.
- Condition, storage, RAM. Used only when written in the title, options, tags or type. Otherwise "unknown".
Limits you should know
- Fexlo never solves CAPTCHAs, logs in, rotates addresses or hides itself. A refusing site is marked Blocked.
- A capped, filtered or interrupted read is never treated as the store's full catalogue. A product is called removed only when both reads were complete with the same filter.
- Cross-store matching is by exact brand + model + capacity + condition. Near matches are counted separately and never mixed into price statistics.
- Data stays in your browser profile: no cloud sync; removing the extension removes local data.
- Fexlo reads public pages only and cannot tell whether a particular use of a website's data is permitted. You are responsible for following each website's terms and the laws that apply to you.
Verified so far
Synthetic stores reproducing the catalogue format and each end state have been tested automatically. Real-store checks are run by the owner and recorded in the project's release notes; no real-store compatibility is claimed on this page until that evidence exists.