Clear answers about evidence, access and monitoring.
If the next action is not obvious, start with a free public storefront scan.
What is a potential ecommerce revenue leak?
An observable storefront problem that could reduce discovery, buyer confidence or the chance to complete a purchase. It is a risk description, not a calculated dollar amount.
My store looks fine. Why check it?
A store can be live while a specific product page, image, internal link or purchase signal is broken. ShopMender checks page-level evidence that a homepage visit may not reveal.
Is this just an SEO audit?
No. Discoverability is one category. ShopMender also checks Revenue, Conversion, Performance, Technical and Trust signals across the public buying path.
Which platforms are supported?
Public Shopify, WooCommerce, PrestaShop, Magento and custom storefronts can be scanned. The scan starts from a URL, so it is not limited to an app marketplace.
Do I need to install an app or plugin?
No. ShopMender reads the public storefront and does not require Shopify Admin, WordPress credentials or theme access.
Will the scan change my store?
No. Scans are read-only and do not modify storefront content, themes, applications, catalog data or checkout behavior.
What does the free scan include?
One public storefront scan, up to 20 selected pages, a Revenue Leak Score and three complete findings. No account or card is required to start.
Why is a finding medium or low confidence?
Some conversion and trust signals depend on theme markup and can require heuristics. ShopMender shows confidence so uncertainty is visible.
How reliable are the findings?
HTTP status and parsed markup checks are more direct; theme-dependent checks can be imperfect. Findings include evidence and should be reviewed before action.
Can I share a before-and-after result?
A card can be created from a finding you can access in a full report, with retained before evidence and a later successful recheck for the same supported rule and target. Publishing is a separate, voluntary action. The public page is dated, noindex and limited to selected evidence; it is not a permanent certificate.
Which parts of the buying path are checked?
Within the selected page limit, ShopMender prioritizes public product and collection pages, cart pages linked by the store, and discoverable shipping or returns policies. It reads a cart page but never submits a cart or opens checkout.
Does ‘not detected’ mean the feature is missing?
Not always. Some storefronts render prices, product cards or buttons with JavaScript or theme-specific markup. Those signals are labeled as not detected in fetched HTML, with low confidence where appropriate. Blocked or unstable responses are treated as incomplete coverage rather than confirmed defects.
Why pay monthly after the scan?
A scan shows what is observable today. Monitoring repeats checks after future theme, app and catalog changes so new issues can surface.
Will monitoring crawl my entire site?
Coverage follows the plan limits and scan type. Full scans cover up to 200 pages on Monitor or 1,000 pages per store on Growth; daily critical checks are lighter and separate.
Does ShopMender bypass Cloudflare, CAPTCHA or WAFs?
No. It respects robots.txt, access controls and anti-bot protections. If access is restricted, the report explains that it is limited.
Does it calculate how much revenue I lost?
No. The Revenue Leak Score is a scoped risk and prioritization indicator, not a financial estimate or guarantee of recovered sales.
Can ShopMender scan checkout or private areas?
No checkout automation is performed and private customer, order or account areas are outside the public scan scope.
How is billing managed?
Subscriptions use Stripe Checkout and the Stripe customer portal. ShopMender does not handle raw card data.