VKT Toolkit · October 23, 2026 · 7 min read

Which Stores Does VKT Cart Lock Support? 24 Presets and the Universal Fallback

The short answer is "your store, most likely", but that sentence deserves a page. A checkout lock only works if it recognizes the checkout step, and recognition is the least glamorous part of the product. This guide lists every preset, explains what a preset adds, and is explicit about the cases where the lock will not help.

24 Presets, Plus Everywhere Else

VKT Cart Lock ships with 24 site presets and a generic fallback. The presets are the 24 stores listed below; the fallback is what makes the extension usable on the long tail. Neither is a promise, and both are described accurately below.

The mechanism does not change by store: the first checkout click starts a countdown, the order is not submitted, and checkout buttons, links, form submits and checkout pages stay blocked until the timer ends. There is no skip or snooze, and the timer survives a tab close or browser restart. A preset only changes how reliably the checkout step is recognized.

The Full Preset List

That is 24. The categories are for reading convenience, not for separate behavior — each preset does the same job on its own store.

What a Preset Adds

On a preset store, the extension knows where checkout usually lives: which buttons and links to watch, which form submissions to intercept, and which page patterns indicate the checkout step. That matters because the words on a button are not stable. Stores test labels, localize them, and move the primary action around.

On a store that is not on the list, the extension falls back to matching checkout text — "checkout", "buy now", "place order" — and common selectors. In practice this catches most standard carts, including many small shops running familiar platforms. It is less certain on icon-only buttons, unusual wording and custom checkout flows that never use the word "checkout" anywhere.

Two practical consequences. First, a store missing from the list is not a dead end; try it before assuming it will not work. Second, if you shop somewhere repeatedly and the timer never starts, do not keep testing — force-lock the domain and report the page.

Why Payment Pages Are Excluded

Payment-provider pages and iframes — Stripe, PayPal, Adyen, checkout.com, Braintree — are explicitly excluded from the extension's scope. It never runs on the payment-provider page or iframe where card details are entered.

There are three reasons, and all of them are deliberate. The payment step is the worst possible place to break something: a blocked card form is a support incident, not a cooling-off. By the time a payment page loads, the decision has already been made — the useful intervention is earlier, at the checkout click. And scoping the extension away from payment frames keeps its permissions and behavior easier to reason about.

The honest consequence: a store that jumps straight from a product page into an express payment frame, without a normal checkout step, gives the lock nothing to intercept. Force-lock helps where a checkout trigger exists; where it does not, the browser extension is not the right tool for that purchase.

Unsupported Stores and Wrong Blocks

Two different problems, two different fixes.

• The checkout was not blocked. Add the domain to the force-lock list, which marks it as always locked rather than relying on matching. Then run one test purchase attempt to confirm the timer starts. If the site still sails through, use the support address with the URL and the button text;
• Something was blocked that should not have been. Use the misblock report. One click marks that element as a false positive, and it is excluded next time, so the same page does not keep triggering a lock. This is the fastest route for pages that merely talk about checkout — a returns policy, a help article, a seller dashboard.

Force-lock and allowlist pull in opposite directions, so use them with intent: one store should not sit on both lists. For a store where most purchases are small and occasional, the small-amount exemption is often cleaner than allowlisting the whole domain.

What "Support" Does Not Mean

It is worth being plain about the boundaries, because overclaiming here produces disappointed users:

• Desktop only. VKT Cart Lock is a Chrome and Edge extension; it does not run in mobile browsers or inside shopping apps;
• Not in-store. The lock has no opinion about a physical checkout counter;
• Not every checkout variant. Large stores run experiments, and a layout the preset has not seen can slip through until it is reported;
• Not payment. As above, payment pages are out of scope by design, not by omission.

Given those limits, the realistic promise is modest and useful: on the stores you actually use, the lock will usually catch the checkout step, and when it does not, force-lock and a report are a two-minute fix. If you have not configured it yet, the 10-minute setup guide covers the exemption and force-lock screens in order.

FAQ

More guides in the VKT blog; questions to [email protected].