What Is TrustLens?

[LAST UPDATED: 2026-03-25]

The Hidden Cost of Not Knowing Your Customers

Most WooCommerce store owners think about their customers as a pool of people who buy things. Some buy often. Some buy once. Some return things occasionally. That’s the mental model, and for a small store with 200 orders a year, it’s close enough to reality.

But when your order volume grows, something shifts. A small number of customers — consistently — start costing you more than they spend. The serial returner who orders clothing every month and sends back 80% of it. The shopper who has claimed your “first order” welcome discount seven times across seven email addresses. The cluster of accounts at the same address, all with different names, all hitting chargebacks when disputes arise.

These patterns exist in your order data right now. They are not visible in a standard WooCommerce order list. You would have to manually cross-reference customer histories — hundreds of orders, dozens of accounts — to see them. Almost nobody does this, which means the patterns grow quietly until they become expensive problems.

TrustLens is built to make the invisible visible. It watches every order, every refund, every coupon redemption, and every checkout fingerprint — and turns all of that into a single number per customer: a trust score. When the score drops, something is worth looking at. When it drops to the bottom segment, you have a decision to make.

What TrustLens Is

TrustLens is a WooCommerce customer risk intelligence plugin built by Webstepper. It runs entirely within your WordPress installation — no external service, no data sent anywhere by default — and analyzes every customer’s behavior across your store’s order history to assign them a trust score from 0 to 100.

Customers are automatically grouped into six risk segments based on their score: VIP, Trusted, Normal, Caution, Risk, and Critical. These segments appear on the customer list, on individual customer profiles, on the WooCommerce orders list, and on the order edit screen. Wherever you process orders in your admin, the trust context travels with the customer.

There are two versions: a free version on WordPress.org that includes the full scoring engine and all five detection modules, and a Pro version that adds automation rules, webhooks, chargeback tracking for Stripe and WooPayments, payment method risk controls, and advanced notifications. The free version is not a trial — it is a complete, functional product.

How the Trust Scoring Engine Works

Every customer starts with a base score of 50. From there, TrustLens’s five detection modules analyze behavior and apply positive or negative adjustments. All adjustments are summed, added to the base score, and clamped to the 0–100 range. The final number is saved to the customer’s profile and used to determine their segment.

Here is a concrete example of what scoring signals look like in practice. A customer with a solid order history might have a signal breakdown like this:

Total: 50 + 45 = 95. VIP segment. A high-value customer who deserves allowlist protection so a future unusual order doesn’t accidentally flag them.

Now a riskier example — a customer who has been gaming your return policy:

Total: 50 − 75 = clamped to 0. Critical segment. Every signal that contributed to that score is visible in the customer’s profile. You can see exactly why they’re here.

The minimum order threshold

Customers below the configurable minimum order threshold — default is 3 orders — stay in the Normal segment until enough data exists for reliable classification. This prevents new customers from being flagged on the basis of a single transaction. The signals still accumulate; the segment just won’t move until the data is meaningful.

The account age loyalty bonus

Long-standing customers earn a loyalty bonus that adds up to +15 points to their base score. The bonus scales based on how long the customer has been ordering:

• 3 months or more: +5 points
• 6 months or more: +10 points
• 1 year or more: +15 points

This is intentional. A customer who has been ordering from you for two years deserves a trust premium, even if their return rate is slightly elevated. The loyalty signal acts as a counterbalance to occasional risk signals from otherwise reliable customers.

The Six Customer Segments

Trust scores map to six named segments. The thresholds are configurable in Settings, so you can tune them to match your store’s risk tolerance. Here is how the segments work and what each one means operationally:

The Five Detection Modules

TrustLens uses five detection modules to build each customer’s score. All five run in the free version. Each module hooks into WooCommerce events — order creation, order completion, cancellations, refunds, coupon applications — and calculates a signal adjustment. The score updates asynchronously via Action Scheduler so there is no checkout performance impact.

How the linked accounts module fingerprints customers

The linked accounts module deserves more explanation because it is the most technically sophisticated part of TrustLens and the one that catches the most sophisticated abusers.

When a customer places an order, TrustLens extracts up to six fingerprint types from the order data:

1. Shipping address — normalized (abbreviations expanded, punctuation stripped, lowercased) before hashing so “123 St.” and “123 Street” match
2. Billing address — same normalization process
3. Phone number — normalized to digits only, country code stripped
4. IP address — stored per order (excludes localhost)
5. Payment method token — Stripe card fingerprint or saved payment token ID
6. Device user agent — browser and OS fingerprint

Each value is hashed with HMAC-SHA256 before storage, using a site-specific secret key. The raw values are never stored in the database. This means the fingerprinting system cannot leak personal data even if someone gains read access to the database — and the hashes are non-transferable across sites.

When a linked account is detected, the risk level of the linked accounts factors into the current customer’s score. Being linked to one high-risk account carries a penalty. Being linked to a blocked account carries a larger one. Multiple linked accounts scale the penalty further.

Real Abuse Patterns TrustLens Surfaces

Abstract descriptions of what the detection modules do are useful, but it helps to see the actual patterns they catch. These are the most common scenarios stores report once they install TrustLens and run the historical sync.

The Command Center Dashboard

When you navigate to TrustLens in your WordPress admin, the first thing you see is the command center dashboard. It is a 9-section overview of your store’s risk picture — not a per-customer view, but a store-wide one. The goal is to answer the question “what is actually happening with my customer base right now?” without requiring you to click through individual profiles.

What the dashboard shows

• Store health score — an aggregate measure of how the risk distribution across your customer base looks today, with a health attention message when your risk-customer count is elevated
• KPI cards — total customers profiled, average trust score, new high-risk customers, events in the last 24 hours, total orders analyzed, and store return rate
• Trust score trends — a 30-day line chart showing average trust score movement across your customer base, using Chart.js with interactive tooltips
• Segment distribution — a visual breakdown showing what percentage of your customers are in each of the six segments, so you can see if your Critical count is growing
• Refund activity — refund volume over time, helping you distinguish seasonal variation from trend changes
• Activity by hour — order and event volume by hour of day, useful for spotting unusual activity spikes
• Category return rates — which product categories have the highest return rates across your customer base
• Revenue protection overview — an ROI scorecard showing money protected, money at risk, protection rate, and actions taken
• Top returners and high-risk attention list — the customers with the highest return rates and the highest-risk segments, surfaced at a glance

All charts use Chart.js and show polished empty states when data isn’t available yet — for example, immediately after install before the historical sync has run.

Customer Management Tools

Beyond the dashboard, TrustLens provides three layers of customer management: the customer list, individual customer profiles, and bulk operations.

The customer list

The customer list shows every TrustLens-profiled customer with their trust score, segment badge, return rate, and order summary. It is filterable by segment, searchable by name or email, and sortable by score. The segment filter is particularly useful when you want to work through all Risk or Critical customers as a batch — filter to that segment, then decide case by case.

Individual customer profiles

Each customer has a full profile page showing:

• Trust score and current segment with the score calculation breakdown — every signal listed with its module, adjustment amount, and reason text
• Key metrics — total orders, total refunds, return rate, refund value, coupon usage, cancellation count
• Linked accounts — all detected linked accounts with their email, segment, match types, and match count
• Event timeline — a full chronological log of every order, refund, coupon use, cancellation, and trust score update, with timestamps and order links
• Action buttons — block, unblock, allowlist, recalculate score, and (in Pro) generate a dispute evidence report

WooCommerce order screen integration

TrustLens adds two integrations to the WooCommerce orders interface. On the orders list, each order row shows a color-coded trust segment badge next to the customer name. You can filter the orders list by segment — a dropdown lets you show only orders from Critical or Risk customers. You can also sort by segment severity (Critical first). Clicking the badge links directly to the customer’s TrustLens profile.

On the individual order edit screen, a metabox shows the customer’s trust score, current segment, and key risk metrics — so you see risk context while processing a specific order without having to navigate away.

Bulk operations

The customer list supports bulk actions: block, unblock, allowlist, recalculate scores, and delete customers. Bulk recalculation is useful after changing scoring thresholds in Settings — you can trigger a fresh calculation for a whole segment without waiting for order events to retrigger individual updates.

Checkout Enforcement — Blocking and Allowlisting

TrustLens gives you two enforcement tools: the block list and the allowlist. They are opposite controls, and both are important.

Blocking customers

Blocking is opt-in — checkout enforcement is disabled by default and must be turned on in Settings. Once enabled, blocked customers see a customizable message when they try to add items to their cart or proceed to checkout. The block applies to both logged-in users and guest checkouts using the same email address. All blocked checkout attempts are logged to the customer’s event timeline.

The block message is configurable. The default is a neutral statement that doesn’t explain the reason for the block and directs the customer to contact support — which is generally the right approach, since you do not want to reveal your risk detection logic to the people you are trying to block.

The allowlist

Allowlisted customers are locked at a score of 100, regardless of any signals in the detection modules. This protects high-value customers from false positives. A business buyer with unusual order velocity, a reseller with above-average return rates, a VIP who had a run of genuinely defective products — all of these can look risky to the detection modules without actually being problematic.

The allowlist is the right answer for those situations, not adjusting the scoring thresholds. You want the thresholds set to catch real patterns; the allowlist is where you override the system’s judgment for specific individuals you have good reason to trust.

Historical Sync — Building Profiles From Past Orders

When you first install TrustLens, your existing customers don’t have trust profiles yet. New orders are analyzed automatically from the moment of activation. But what about the months or years of order history already in your database?

The Historical Sync processes your existing WooCommerce orders in the background to build trust profiles from past data. It runs in batches using Action Scheduler — the same background processing system WooCommerce itself uses for background jobs — and does not affect frontend performance. You can monitor its progress, pause it, and resume it from the dashboard.

The historical sync is thorough: it backfills coupon behavior metrics, category return aggregates, linked-account fingerprints, and a full event timeline using the original order and refund timestamps from your historical orders. When the sync completes, your customer profiles reflect the complete behavioral history your store has accumulated, not just orders placed after activation.

For a store with several years of order history, this is often where the most valuable discoveries happen. Patterns that have been building quietly for 18 months suddenly become visible in the segment distribution on the dashboard. The high-risk attention list surfaces names you recognize.

Free vs. Pro: The Complete Breakdown

Pro pricing: Personal $79/year (1 site), Business $149/year (5 sites), Agency $299/year (30 sites). Full details on the TrustLens product page.

What Pro adds — in plain terms

The free version gives you visibility and manual control. You can see everything, understand everything, and act on it manually. For many stores, that is exactly what they need.

Pro is for stores that need the loop to close automatically. Automation Rules let you configure what happens when a customer’s risk segment changes — so a customer who moves into Critical can trigger an action without requiring you to check the dashboard. Payment Method Risk Controls let you hide specific payment gateways for high-risk segments at checkout, which can reduce chargeback exposure by steering risky customers toward payment methods with lower dispute rates. Chargeback Tracking connects dispute history from Stripe and WooPayments into customer scores so you have the complete picture. And the Dispute Evidence Report generates a professional, print-ready behavioral summary for uploading to payment processor dispute portals — which matters when you are fighting a chargeback and need to demonstrate a documented pattern of behavior.

Who It’s Actually For

TrustLens is worth installing if any of the following are true for your store:

• You have a generous return policy and wonder whether a small number of customers are responsible for a disproportionate share of your returns
• You run regular promotions with first-order or new-customer coupons and have noticed the coupon redemption numbers looking higher than expected
• Your refund rate is rising and you are not sure whether it reflects product issues or behavioral patterns
• You process enough orders that reviewing customer behavior manually is not practical — TrustLens is most valuable when you have more customers than you can reasonably know individually
• You have experienced chargeback issues and want better early warning before a customer reaches dispute stage
• You need to enforce policies consistently — being able to point to a score, a signal breakdown, and a 12-month event timeline is more defensible than acting on instinct

It is probably not the right fit if your store is very small (under 200 customers), you know most of your customers personally, you have no return policy and no coupons, or you are primarily looking for real-time payment card fraud detection. TrustLens works at the behavioral layer, not the payment infrastructure layer.