The store's built-in captcha checks that a form is sent by a person, not a program. No keys or third-party services needed; new stores already protects all five forms.
When you need this:
- Spam reviews under products — programs can't send them, customers write as before.
- “Quote request” is flooded with empty requests — contact and quote requests come only from people.
- Hundreds of empty customer accounts — at the “Adaptive” level, a suspicious sign-up confirms with a code from a picture.
- You already use Google reCAPTCHA — choose it instead of the built-in protection.
Where to start: “Store settings” → “Security” → the “Form protection” card → “Protection level”.
What form protection can do
- Check five forms — registration, guest checkout, reviews, returns, contact.
- Stay out of the customer's way — at the “Invisible” level they do nothing.
- Ask only suspicious visitors for a code — the “Adaptive” level.
- Limit submissions from one address — an hourly limit for each form.
- Work through Google reCAPTCHA v3 — the second option, with Google keys.
How to turn protection on
Protection is set in two places: the module card sets how strictly to check, and “Store options” sets which protection works and on which forms.
- Open “Store settings” → the “Security” section → the “Form protection” card.
- Check that the “Enabled” switch at the top of the screen is on.
- “Protection level” — start with “Invisible”. “Check difficulty” — “Normal”. Click “Save”.
- Open the “Store” section → the “Store options” card → the “Form protection” block.
- In “Bot protection for forms”, choose “Elbuz form protection”; in “On which forms”, tick the forms. Click “Save”.
1
Enabled switch2
Protection level3
Check difficulty4
Submissions per hour5
Still to set up card- A turned-off module checks no forms.
- What happens to a suspicious submission: rejection or a code from a picture.
- How long the customer's browser works on the challenge.
- How many submissions of one form to accept from one address per hour.
- What is still missing for the protection to work.
1
Bot protection for forms2
On which forms- Which protection is active: built-in, Google reCAPTCHA v3 or none.
- Which forms are checked.
In a new store all of this is already set: “Elbuz form protection” is chosen and all five forms are ticked. In a store created earlier, the forms you chose stay ticked — check “Registration” and “Guest checkout”.
If a protection is chosen in the options but its module is off, “Still to set up” shows “First set up and turn on “Form protection””. The options won't save, with the same message.
“— None —” in “Bot protection for forms” turns off the check on all forms. How the settings window works in general is covered in “Store settings”.
What the customer sees: protection levels
While the customer fills in the form, their browser solves a small task in the background. The store accepts the form if the task is solved, the hidden trap field is empty and 3 seconds have passed since the first touch. Clicking “Submit” sooner shows “Checking that you are not a robot…” — the form is sent by itself.
What happens to a submission depends on “Protection level”:
| Protection level | Regular customer | Submission looks like a bot |
|---|---|---|
| Invisible (default) | Does nothing | Refused with an explanation |
| Adaptive | Does nothing | A code from a picture instead of a refusal |
| Always a code | Types a code on every submission | Types a code |
Looks like a bot means sent in under 3 seconds, over the limit, or after a failed attempt from the same address. The last one counts only at the “Adaptive” level.
A submission with an unsolved task, a filled-in trap or a replayed old answer is rejected at any level. A code from a picture doesn't replace this. That's why the form won't send without JavaScript in the browser.
Code from a picture
The code is 5 letters and digits with no look-alike pairs: no 0 and O, no 1 and l. Upper or lower case doesn't matter.
“Another code” shows a new picture; “I can’t see the picture” shows an addition question in words, for example “What is seven plus two?”. The answer can be digits or a word.
After five wrong answers the code expires; the store shows a new picture with the next submission. New codes are limited to 20 per hour per visitor, and the same per network address.
Check difficulty
“Normal” suits most stores. “Strong” makes the browser compute about four times longer: mass spamming gets more expensive, and a customer on a phone waits up to a few seconds. Use it when spam gets through even at the “Adaptive” level.
How many submissions to allow per hour
“Submissions per hour” is how many times one form accepts a submission from one network address per hour. Only accepted submissions count. The default is 10; allowed values are 1 to 1000.
Over the limit, the “Invisible” level refuses with an explanation; all forms together accept up to five times the limit from one address. “Adaptive” and “Always a code” ask for a code as soon as the address has sent the limit across all forms together.
Customers in one office or on one network share an address. If they hit the limit, raise it or choose “Adaptive”: they'll type a code instead of being refused.
Which forms are protected
A form is checked only if it's ticked in “On which forms” in the store options.
| Tick | What it checks |
|---|---|
| Registration | Creating an account, including during checkout, and affiliate sign-up |
| Guest checkout | A guest's order |
| Reviews | A review on the product page |
| Returns | A return request |
| Contact | The contact page and the “Quote request” form |
A customer signed in to their account isn't checked at checkout. A guest is checked at the last step, once the other fields are filled in correctly: a mistake in the address doesn't make them pass the check again.
Trade-in and prize games have their own switch: “Bot protection (captcha)” and ““I am not a robot” check”. When it's on, the form uses the protection chosen in “Bot protection for forms”, even if it isn't ticked in “On which forms”.
When to choose Google reCAPTCHA v3
The built-in protection and reCAPTCHA are two options of the “Bot protection for forms” field. Whichever is chosen works.
| What we compare | Elbuz form protection | Google reCAPTCHA v3 |
|---|---|---|
| Keys | Not needed | A site key and a secret key from the Google console |
| What the customer sees | Nothing, or a code from a picture | Nothing; a reCAPTCHA badge in the page corner |
| How it decides | Browser task, trap, time to fill in, limit | Google's score from 0 to 1 against “Minimum score (0–1)” |
| Google unavailable | Doesn't depend on it | No reply within 5 seconds or a Google failure — the form goes through unchecked, and the store writes this to the log |
| Visitor data | Stays in the store | Google scores the visitor |
How to connect reCAPTCHA
- In the Google reCAPTCHA Admin Console, register a site: reCAPTCHA type — Score based (v3), Domains — your store address. Copy both keys.
- “Store settings” → “Security” → the “Form protection (reCAPTCHA)” card. In the “Google keys” block, enter the “Site key” and “Secret key”.
- Turn on “Enabled” at the top of the screen and click “Save”.
- In “Store options”, the “Form protection” block, choose “Google reCAPTCHA v3”, tick the forms and save.
1
Enabled switch2
Site key3
Secret key4
Minimum score5
Hide badge6
Not set: Site key- reCAPTCHA works only when it is enabled and selected in the store options.
- The site key from the Google reCAPTCHA console, type v3.
- Not shown after saving; you only see that it is set.
- Submissions scoring below this Google score are rejected.
- Removes the reCAPTCHA badge from the pages.
- Without both keys reCAPTCHA does not work, and forms are protected only by the built-in protection.
The keys are required only while reCAPTCHA is chosen in the options. Then the card won't save without them: “Required — the module will not work without it”.
1
Bot protection for forms2
Module warning3
Still to set up- Google reCAPTCHA v3 is chosen as the protection for site forms.
- The reCAPTCHA module has no keys or is turned off, so form protection will not work; “Open the module” leads to its card.
- Until the module is set up, the options will not be saved.
“Minimum score (0–1)” is 0.5 by default; submissions with a lower score are rejected. If real customers complain, set 0.3. “Hide badge” removes the badge, but then Google's rules require you to mention reCAPTCHA on the site.
Scenarios
Electronics: spam reviews under smartphones
In “On which forms”, tick “Reviews”; level — “Invisible”. If the spam hasn't stopped after a week, choose “Adaptive”. Customers write reviews without pictures; programs can't.
Home appliances: empty requests for a quote
The “Contact” tick also covers “Quote request”, not just the contact page. Set “Submissions per hour” to 5: a real customer rarely sends more requests.
Any store: empty accounts
Tick “Registration”; level — “Adaptive”. Suspicious sign-ups type a code first; everyone else registers as before.
A store under attack
Spam gets through even at “Adaptive” — set “Always a code” and “Strong”. When the attack is over, go back to “Adaptive”: a code on every submission gets in customers' way too.
What to do when a form won't send
| What you see | Why | What to do |
|---|---|---|
| “To send the form, turn on JavaScript in your browser.” | JavaScript is off in the customer's browser; the check can't run without it | The customer turns on JavaScript (protection levels) |
| “Too many submissions from your network. Please try again a little later.” | This address has already sent the hourly limit of forms | Raise “Submissions per hour” or choose “Adaptive” (limit) |
| “We could not confirm that you are not a robot. Reload the page and try again.” | The submission was taken for an automated one | The customer reloads the page. If several customers get it — choose “Adaptive” |
| “Too many new codes in an hour. Please try again later.” | The visitor asked for more than 20 new codes in an hour | Wait an hour (code from a picture) |
| In the options: “First set up and turn on “…”” with the module name, “Form protection” or “Form protection (reCAPTCHA)” | The chosen protection's module is off, or reCAPTCHA has no keys | Open the module card in the “Security” section, turn it on and save, then save the options (how to turn it on) |
| “Bot protection verification failed! Please try again.” | reCAPTCHA: keys for v2 or another domain, Google didn't reply, or the score is below the threshold | Check the type and domain in the Google console, lower “Minimum score (0–1)” (reCAPTCHA) |
FAQ
How do I turn off form protection?
In “Store options”, choose “— None —” in “Bot protection for forms” and save. While a protection is chosen in the options, you can't turn its module off: the card won't save.
What happened to the captcha after the store update?
Where “Simple picture with a code” or nothing was set, it's now “Elbuz form protection”. The forms you ticked stay ticked: tick “Registration” and “Guest checkout” yourself. A store with reCAPTCHA stayed on it.
Does the protection send customer data anywhere?
“Elbuz form protection” doesn't: the check runs in the store itself. reCAPTCHA passes the visitor to Google for scoring.
Will the protection stop ads written by hand?
No. The protection blocks programs, and a person will pass any check. Don't publish such reviews without reviewing them.
Does the protection also check the callback form?
No. “Callback request” and “Found cheaper” have their own bot trap and a limit of one request per minute from an address.
Where to find it and who has access
- Menu
- Directories → Operations → Store settings → “Security” → “Form protection”
- Other entry points
- “Store” → “Store options”, the “Form protection” block — choosing the protection and the forms
- Access rights
- the “Store settings” window in group permissions
- Prepare
- for reCAPTCHA — a Google site key and secret key
Related topics
- If you need to set up other options — checkout, stock, statuses — Store options.
- If you need to understand how the store settings window works — Store settings.
