Why BotShield
Not every unusual visit is a threat. When something looks wrong, you should have more than a feeling to go on. BotShield keeps a record of supported storefront activity, and lets you set the response.
What a sales report leaves out
Orders and ad clicks describe the business. They do not describe a suspicious visit. These are patterns BotShield may evaluate.
The same kind of visit shows up again.
A browser behaves more like a script than a shopper.
Requests reach parts of the shop that ordinary browsing usually does not.
An address you already chose to stop comes back.
BotShield can evaluate a visit that runs on your storefront. A visit that never reaches that check may not be inspected.
BotShield in action
This scene is a sample. It is not a live feed, and it is not a customer's data.
Someone requests a page. If that visit runs BotShield's storefront check, it can be evaluated. If the check never runs, the visit may not be seen.
Why this matters
A strange visit can disappear into a sales chart. BotShield keeps a record of supported storefront activity and can call out repeated requests, automated browsing, sensitive paths, and previously blocked visitors. You can point to a visit and decide whether the response was right.
A single on-or-off switch is a blunt tool. Sensitivity can be Low, Medium, or High. You can trust an address, block one, turn Auto Block on or off, or pause blocking for 10 minutes. Loosen a rule that caught a real shopper, or tighten one that let a pattern continue.
Each evaluated visit can show allow, challenge, or block, with a short reason. Allow means the visitor continued. A challenge asks them to confirm they are a shopper. A block shows BotShield's page instead of the store. The label is a signal to review, not proof that someone is a bot.
Fraud Orders, when order access is in place, shows supported order-risk details beside the storefront record. It does not cancel, refund, or take over checkout. The recommendation is a signal to review, not proof of fraud.
You enter a few assumptions: a value per blocked event, a value per challenge, staff minutes, and an hourly cost. BotShield applies them to recorded activity over 7 or 30 days. The result is an estimate you can question. It is not guaranteed savings or recovered revenue.
Why the record matters
Without a record, two shops can look equally careful. One is turning away real shoppers. The other is letting a repeated pattern through. Memory will not tell you which is which.
That is the practical cost. You have fewer facts when you decide how to respond, and little to go on if you want to change the rule.
In your hands
These notes are samples of what each control is for. They are not a live view of your shop.
Sample · recent visit reviewed
Open recent visits and the signals that stood out, including the path, the action, and a short reason.
The product pages walk through each part. Pricing explains BotShield Basic. If you want to ask about your own store, write to us.
