CommerceRadar

CommerceRadar — Website Commerce Detector

STOP GUESSING — know if a site is really transactional.

CommerceRadar analyses a website using a real browser (Playwright) to determine whether it is genuinely monetized. It does not rely on marketing words or surface-level HTML guesses. Instead, it distinguishes weak signals from strong, verifiable commerce evidence.

The goal is simple: confirm whether users can actually buy something on the site.

⸻

What CommerceRadar actually does

CommerceRadar opens the website like a real user and observes: • pages that look like pricing or plans • product data embedded in the page (JSON-LD) • cart and checkout URLs • real checkout flows (/cart, /checkouts, etc.) • payment provider SDKs and endpoints (Stripe, PayPal, Google Pay, Apple Pay…) • network activity triggered by commerce actions

It then classifies what it finds using conservative logic.

False negatives are preferred over false positives.

⸻

Why “strong” vs “soft” signals exist

Many websites mention prices, “buy now”, or “checkout” without actually selling anything.

CommerceRadar separates signals into two categories:

Soft evidence Textual or visual hints found in HTML (words, buttons, symbols). These suggest intent, but do not prove a real transaction is possible.

Strong evidence Observable, technical proof that a checkout exists (URLs, endpoints, platform-specific flows). These confirm that a user can add a product to a cart and pay.

⸻

Input schema

url (required) The website URL or domain to analyze.

maxPages (optional, default: 5) Maximum number of pages to crawl.

timeoutSeconds (optional, default: 15) Timeout per page in seconds.

⸻

Output schema

domain The analyzed domain.

has_pricing_page True if a dedicated pricing or plans page exists (for example /pricing, /plans, /billing).

has_prices True if currency symbols or numeric prices were detected anywhere on the site. This is a weak signal.

has_prices_strong True only if prices are connected to real commerce evidence, such as a checkout flow, pricing page, or product schema.

has_checkout_soft True if checkout-related words or UI elements were found in the HTML. This does not confirm a real checkout.

has_checkout_strong True only if a real checkout flow is confirmed. Examples include cart URLs, checkout URLs, or platform-specific checkout endpoints. If this is true, users can actually purchase something.

signals A detailed explanation layer containing:

pricing_urls Visited pages that match pricing patterns.

checkout_urls Visited pages that match checkout or cart patterns.

discovered_pricing_links Pricing links discovered on the site, even if not visited.

discovered_checkout_links Checkout or cart links discovered on the site.

payment_providers Detected payment providers based on real SDKs or network calls.

ecommerce_platform Detected platform if identifiable (Shopify, WooCommerce, Magento, etc.).

html_clues Raw clues explaining why signals were triggered (currency tokens, checkout tokens, JSON-LD product data, etc.).

checkout_type High-level classification: ecommerce, saas, donation, or unknown.

confidence A conservative confidence score between 0 and 0.99. It increases only when strong evidence is found.

⸻

How to interpret results (important)

has_prices = informational Numbers or currency symbols exist, but may not indicate commerce.

has_pricing_page = commercial intent The site publicly presents pricing or plans.

has_checkout_soft = hint only Marketing or UI suggests checkout, but no proof yet.

has_checkout_strong = confirmed transactions A real checkout exists. Users can pay.

Recommended strict filter Use has_checkout_strong = true

Recommended commercial filter Use has_prices_strong = true

⸻

Why some big sites may fail

Large enterprise websites (Google, Nike, etc.) often block or hide checkout flows behind heavy bot protection, geo rules, or authentication.

In these cases, CommerceRadar may return low confidence or no strong checkout, even though the site is clearly commercial.

This is intentional. The tool only reports what it can observe reliably.

⸻

Best use cases

CommerceRadar works best on: • Shopify stores • WooCommerce stores • SMB e-commerce sites • Public SaaS pricing pages • Dropshipping and DTC brands

⸻

Design philosophy

Words do not equal commerce Prices do not equal checkout Only observable browser behavior counts

If CommerceRadar says a checkout exists, it is because it actually saw one.

⸻ Note: “Self-serve pricing” vs “Checkout confirmed” (important) Some SaaS websites show clear, self-serve pricing on public pages, but complete the purchase inside an authenticated app, modal flow, or backend API redirect. In these cases, CommerceRadar can detect strong pricing while only having soft checkout evidence (no public /checkout or /cart URL). This is expected behavior and avoids false positives.