Which E-commerce Platform Is This Website Built On?

If a site shows up as unidentified, you are very welcome to submit it for inclusion! New store-builder systems and commerce tools keep emerging, and this engine’s fingerprint library is maintained and expanded daily.

Commerce architectures are highly diverse. Failed identification is usually related to the following technical scenarios and detection limits:

• Major system rewrites: Some platforms undergo major architecture upgrades, replacing public fingerprints or leaving them unmatched for now.
• Headless architectures or custom microservices: Many large brands use modern front-end frameworks (Next.js, Nuxt, React SPA) backed by APIs, leaving no traditional plugin or template paths in the page source, which can mislead detection.
• Strong anti-bot and WAF protection: Strict Cloudflare WAF, Akamai or custom WAF rules block non-human browsing, preventing full page content from being fetched for analysis.
• Separate subdomains or purely static brand pages: Some brand homepages are static showcase pages while the real cart or booking system lives on a separate subdomain (e.g. shop.example.com) or a redirected checkout page.
• Forged headers or copied code: Some sites keep legacy file paths during redesigns to preserve SEO rankings and layout (e.g. directories that look exactly like WordPress or a specific platform while the underlying system has been swapped); others fake response headers or copy other sites’ front-end code, which degrades accuracy.

From time to time I proactively review and consolidate unidentified query logs, investigate them technically and keep updating detection rules to steadily improve coverage and accuracy.

Most people check other sites for reference or research. If you are a designer, developer or marketer, knowing a client’s or competitor’s current architecture and limits helps you propose realistic redesign directions instead of plans the system cannot support. It is genuinely useful when planning builds or pitches — but don’t overestimate the magic of any particular stack:

• Estimating build costs and market mainstreams: When planning your own store or site, this helps gauge a competitor’s technical investment — whether they pay tens of thousands per year for a hosted template (like SHOPLINE or Cyberbiz) or spent hundreds of thousands on custom development.
  Keep in mind: even if a competitor runs WordPress + WooCommerce, professionals may have heavily customized it. Simply installing the same stack with the free theme and default plugins produces a completely different result.
• A platform is just a tool — it does not bring orders by itself: People often assume choosing the same platform replicates a successful brand. But the system is essentially a place to list products and process payments; it generates no traffic and guarantees no sales.
  Also, some payment and shipping methods require the merchant’s own applications — opening an account does not unlock everything.
• What really defines quality is photography and copy — never the system: Whether a site looks like a premium brand or a street stall depends mostly on product photography, layout aesthetics and copywriting, none of which relate to the underlying platform. Great photos and compelling copy make even a plain template sell; without them, even the most expensive custom build looks cheap.

There are quite a few similar detection tools out there, and I’ve written a roundup article about them: Website Server & Tech Info Detection Tools. In practice, however, most of them only reveal one slice of a website’s technology and fall short of answering the core question — which system this site is actually built on:

• Technology stacks only — no actual system identified: Some tools tell you the site runs Nginx, loads jQuery, or sits behind Cloudflare, but these are just low-level technical clues. They never directly tell you which store-builder or CMS the site uses, so you still don’t get the answer.
• Limited to a specific system or single target: Some tools are built only for WordPress and become useless when facing other CMS or commerce platforms; others merely report whether GA4, Facebook Pixel and similar tracking codes are installed — a very narrow scope.
• Foreign-only databases — Taiwanese systems are not recognized at all: Some tools build their databases around mainstream Western platforms. Querying Taiwanese store builders like SHOPLINE, Cyberbiz, 91APP, Waca or meepShop either returns nothing or gets mislabeled as an “unknown custom site” — a major drawback for anyone working in the Taiwan market.
• Limited help for real needs: If what you really want to know is which commerce platform a competitor uses, roughly what they paid, or whether a certain feature is achievable, these fragmented details can’t be pieced together into a full picture. You still need fingerprint detection designed for commerce systems to hit the answer directly.

For a detailed comparison of these tools and their pros and cons, check out the full roundup in this article。