Enterprise · Platform history
We have tracked online stores since 2017, and our platform history goes back to 2013. 2.2M European stores have platform history and 86,255 have a detected platform change; changes detected since mid-2025 come with the date we saw them. Find merchants worth reviewing for migration, integration or sales opportunities.
A detected platform change is a reason to investigate, not confirmation of a completed migration.
Synthetic example — proposed report format
Domain: merchant.example
Earlier snapshot: Platform A detected
Later snapshot: Platform B detected
Snapshot dates: included in the agreed report
Observation dates: included where available
Interpretation: review the detected difference
Commercial relationship: not verified
Define markets, categories and the platforms to compare. Historical availability and coverage are checked for that scope.
Agree before/after values, snapshot dates, available observation dates and merchant context. Source URLs are included only where available and explicitly agreed; a URL documents an observation, not a commercial contract.
Use the agreed file to prioritize account research. Missing observations, website changes and detection coverage can affect differences between snapshots.
For custom datasets, we agree the available fields, scope, price, permitted use and delivery date before purchase. Coverage varies by field and market. A missing payment or carrier signal means we did not detect it, not that the merchant does not use it.
A software vendor reviews stores that changed platform in its markets, checks the merchant websites and prioritizes accounts that fit its integration requirements.
This describes a possible workflow, not measured customer results.
We rebuild the searchable index typically every 2–4 weeks. Observation dates vary by source and field; a rebuild does not mean every website was observed again. Delivery dates and any recurring schedule are agreed separately for your project.
No. A missing observation can reflect a page change, a failed observation or a detection gap. Verify candidate changes before treating them as a migration.
Platform migration datasets require an Enterprise agreement. We confirm historical availability, fields, format, permitted use, price and delivery before purchase.
No. These reports compare observed website signals and available history. They do not verify purchases, checkout availability, parcel volumes or provider contracts.