Understand observable activity, review the reasons behind a decision, and see exactly which store actions your integration can cover.
Discuss a pilotWe’re starting with three to five conversations about a specific store problem. Keep existing protections in place. Agree an evidence question and a review date before any monitor-only installation; live-store readiness still needs to be established.
Read the design-partner offerRepeated cart activity, unwanted scraping or unusual account activity can deserve investigation. Start with the business problem and the evidence your store can provide. Neither an abandoned cart nor a fast shopper establishes abuse.
Stable Shopify API 2026-07; platform review 2026-09-24. Initial observations were received on a Basic development store. Each merchant still needs a connection and coverage check; installed telemetry does not mean active protection.
Consent-permitted theme observations and page/product pixel events.
No edge firewall. Disabled scripts and non-executing clients are outside this observation path.
Development observation, 25 September 2026: consent-permitted page and product events received. Merchant-store setup remains to be verified.Only page events where the activated theme runs.
No native form, login or account blocking; new customer-account pages are not theme surfaces.
Live platform test: pendingCart viewed, item added and item removed pixel events.
Browser events do not establish execution, cart ownership or protection of direct API requests.
Development observation, 25 September 2026: item-added events received. Cart views, removals and direct paths still need live checks.Consent-permitted checkout progression pixel events; Function receives Shopify cart quantities.
No active checkout protection in this build. Remote Blokk scoring requires Enterprise custom distribution and approved network access.
Development observation, 25 September 2026: ordinary checkout start received. Completed, accelerated and enforcement journeys still need live checks.No raw payment-attempt feed collected.
No payment credentials, card-testing prevention guarantee, or inference of fraud from abandoned checkout.
Live platform test: pendingSigned order lifecycle webhooks when approved scopes are granted.
An order webhook does not prove a prevented action; browser checkout completion is not an authoritative order outcome.
Live platform test: pendingNo automatic theme/pixel coverage assumed.
Validation has documented exceptions including Create Order API, POS and recurring subscription orders.
Live platform test: pendingThe inspector below uses labelled synthetic data from the generic core to explain the evidence model. It is not a Shopify session, customer record or live result.
webdrivertrueThe browser reported an automation flag. This is a client assertion and can be changed or hidden. Automation can be welcome: this action was later confirmed legitimate.
New installations start in monitor mode. A policy match says “would have matched,” not “blocked.” Supported controls need an explicit surface, clear rule logic, a preview and reversible activation. Unsupported actions remain unavailable.
For the current checkout slice, deterministic quantity validation source exists but has not intercepted a live Shopify checkout. It is not adaptive bot scoring or card-testing prevention. A normal public app cannot assume a real-time call to Blokk during checkout.
Missing telemetry, fast interaction, keyboard navigation, autofill and a shared network are not sufficient reasons to reject a shopper. Crawler claims remain unverified without an appropriate trusted observation point. An authorised agent may be welcome; automation alone does not establish malicious intent.
A merchant needs a server-authenticated way to stop supported enforcement, and an honest explanation of configuration propagation. Review requested actions separately from executed effects. Keep later legitimate, abusive, unresolved and corrected outcomes visible. Integration errors are not “bots blocked.”
The monitoring pilot still needs validation on your store. Shopify Functions in public apps are supported across plans; custom apps using Functions require Plus. Remote validation fetch has additional Enterprise custom-app and network-approval restrictions. None of that establishes activation or tested coverage for Blokk.
No demonstrated card-testing prevention is claimed. We do not collect raw payment attempts or card credentials. Checkout progression is observational and a post-order event cannot establish that an attempt was prevented.
No approved public listing is available. Request access so we can review the permitted pilot route, required setup and remaining gaps.
One bounded pilot, followed by an optional recurring package when its protection workflow is demonstrated. Coverage, observation allowance, support, review date and any fees are agreed in writing before onboarding. No public paid plan is available; discussing a pilot creates no charge. Read pilot pricing status.
Share your business email, store and main problem. Context is optional. We review fit before arranging any installation; this form creates no subscription. The first step is a conversation about your workflow and the evidence a scoped evaluation could deliver.
Go deeper: Shopify bot protection and coverage, checkout abuse evidence and AI shopping agents.