Detect Welcart

PluginView evaluates public page signals in these classes when identifying Welcart. Individual fingerprint rule bodies are proprietary and are not published.

• Cookies
• Script sources
• DOM selectors
• HTML markup

Illustrative indicators derived from public catalog metadata for Welcart. A live scan may match additional proprietary rules beyond these examples.

• usces_cookie
• uscesL10n
• link,link
• <link?href="usces_default.min?.css
• <!-- Welcart version : v

Establishes

One or more public signals on the scanned page matched a known Welcart signature (5 rules) at the time of the scan.

Does not establish

A sitewide install of Welcart, an active vendor contract, exclusive use, or that Welcart is still in place today.

1. 1. Enter the website URL in the scan form — homepage, pricing, checkout, or login pages usually expose the strongest Welcart signals.
2. 2. PluginView reads only public responses (cookies, script sources, dom selectors) and scores them against the Welcart signature set (5 rules).
3. 3. Review the confidence score and text explanation for Welcart on the results page.

Can PluginView detect Welcart without logging in?

Yes. PluginView only reads publicly accessible responses when checking for Welcart — typically cookies, script sources, dom selectors, html markup. It does not bypass authentication or paywalls.

What category is Welcart?

Welcart is classified under Ecommerce, WordPress plugins in the PluginView directory.

How many fingerprint rules cover Welcart?

This reference currently tracks 5 fingerprint rules across cookies, script sources, dom selectors, html markup. Individual rule bodies are proprietary and are not published.

What public signals suggest a site uses Welcart?

Illustrative public indicators for Welcart include usces_cookie; uscesL10n; link,link. A live scan may match additional proprietary rules beyond these examples.