---
title: "How storefront protection works"
description: "How a visitor gets a verdict, and how that verdict gates the checkout."
---

> Documentation Index
> Fetch the complete documentation index at: https://use-protect.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# How storefront protection works

Storefront protection gives each visitor a verdict and carries it to the checkout. A checkout without a valid verdict can be tagged or blocked, depending on your rules.

## The path of a visit

1. **The visitor loads a page**

   The theme app embed asks Protect for a verdict. Protect checks the visitor against your rules: bot detection, Tor, geography, IP and network blocklists.
2. **Protect answers**

   An allowed visitor receives a signed token. A blocked visitor sees whatever you set under **Storefront → Settings → Blocked**: a blank page, a redirect or your own HTML.
3. **The visitor checks out**

   The token travels with the cart. For Shop Pay and other accelerated checkouts, which skip the theme, the checkout block issues the token instead.
4. **Shopify runs the functions**

   The cart validation rule applies your checkout rules and, in block mode, rejects a cart with no valid token. The payment customization hides payment methods when the token is missing or invalid.
5. **The order is tagged**

   Every order gets one verdict tag. See [Order tags](https://use-protect.com/docs/storefront/order-tags/).

## What it works without

Protect needs no DNS change and does not sit in front of your store. Everything runs through the theme embed, the checkout block and two Shopify Functions, which is why **Setup Storefront** in the [setup guide](https://use-protect.com/docs/get-started/setup/) has four checks.

## What it cannot do

- **Stop scraping.** The embed runs after the page has rendered, so public pages, `/products.json` and the Storefront API are out of reach.
- **Change Shopify Analytics.** Order tags let you filter bot-attributed orders out of reports; Shopify's own classification stays as it is.
- **Stop a determined attacker using a real browser by hand.** Protect is calibrated against automation tools such as Puppeteer, Playwright and Selenium. Signals such as hosting networks and visit velocity raise the cost for others without closing the gap.
- **Tag past orders.** Orders placed before you enabled Protect are not tagged.

The same list is shown in the app under **Storefront → Settings → Coverage**.

## Pages in this section

| Page | Covers |
|---|---|
| [Dashboard and sessions](https://use-protect.com/docs/storefront/dashboard-and-sessions/) | Reading the numbers and the session log; exports. |
| [Rules](https://use-protect.com/docs/storefront/rules/) | Every rule and its default. |
| [Risk weights](https://use-protect.com/docs/storefront/risk-weights/) | The Suspect Score and how to tune it. |
| [Order tags](https://use-protect.com/docs/storefront/order-tags/) | What each tag means and how to use it. |
| [Checkout monitor](https://use-protect.com/docs/storefront/checkout-monitor/) | An hourly check for checkout redirects. |
| [Settings](https://use-protect.com/docs/storefront/settings/) | Blocked pages, channel coverage, shared reputation. |

Source: https://use-protect.com/docs/storefront/overview/index.mdx
