LockStock docs

Troubleshooting

The widget does not show up, search is not intercepted, the cart button opens the product page, products are missing.

Start with the console line: open your page with ?lockstock_debug=1 (or &lockstock_debug=1 after the preview link) and look at the browser console.

The console showsMeaningWhat to do
Nothing from [lockstock]The loader did not runCheck that the snippet is on this page. If the console has a Content Security Policy error, allow our hosts
config unavailable, widget inactiveWe refused this pageRegister this exact domain, including www., and check the key in data-key
launch=off … active=falseThe widget is offSwitch the launch mode
launch=ab group=control active=falseYou are in the A/B control groupUse the preview link to see the widget yourself
launch=on … active=trueThe widget is onContinue below
search input not found: …The input selector matches nothingFix inputSelector on the search page, or place <lockstock-search>
  • Typing shows nothing of ours. The widget's code loads on the first focus of your input, so on a slow connection the first keystrokes go to your own search. If your input is not inside a <form>, set formSelector so the widget knows what to submit.
  • Shoppers land on your usual results page. That is the fallback: AI search did not answer within 1.5 seconds. Nothing is broken; if it happens often, tell your LockStock contact.
  • <lockstock-search> shows your old form. The widget is off or in the control group for this visitor, or our box has not loaded yet. Make sure the tag has display: block in your CSS.

Add to cart

  • The button opens the product page. The cart method is «none», or your function is missing under the configured name, or it threw an error. Check the console.

Catalog

  • Some products are missing. They were skipped as invalid — no ID, name, URL or price, another currency, a malformed price — or they are not in the feed. The sync report lists every skipped offer with the reason. See what we read.
  • Removed products are still shown. The feed would have removed more than 30% of your catalog, so removals were held back. See the 30% safeguard.
  • The feed is not read at all. It must be reachable from the internet at a public address, under 500 MB and downloadable within 120 seconds.

Looks

  • The button covers a cookie banner or chat. Move it with launcher.offsetX / offsetY, or with the --lockstock-launcher-y variable from your CSS.
  • Your site's styles leak into the widget. They cannot: the widget lives in its own Shadow DOM. To change its look, use branding.

On this page