Form Submission Rules: 7 Simple Ways to Stop a Form
In short:
- Form submission rules decide whether a form may be sent at all. When a rule holds, such as “the order is not paid”, the form is blocked and the visitor is told why.
- They are different from field validation, which checks one field, and from conditional logic, which shows or hides questions.
- Hiding the Send button is a weak way to enforce form submission rules: it says nothing, it only works in the browser, and it is hard for screen reader users.
- In FillKite Pro, form submission rules are called Submit rules. You write each rule as a sentence, add a message and an optional link, and the same rule is checked again on your server.
- Below: what they are, seven real examples with live demos, how to set them up in five steps, how to write the message, and the mistakes to avoid.
Some forms should not be sent yet. A support request for an order that has not been paid. A booking for more people than the room holds. An event sign-up from someone who is too young. In each case you need form submission rules: a way to say “not until this is true”, and to tell the visitor what to do about it, instead of letting the entry arrive and cleaning up later.
This guide explains what form submission rules are, how they differ from validation and field logic, and why hiding the Send button is not a real answer. Then it shows seven examples you can try live, five simple steps to set them up in WordPress, how to write a message that helps, and the mistakes that make form submission rules frustrating.
What are form submission rules?
Form submission rules are conditions on the whole form. Each rule says: when these answers are given, the form must not be sent, and here is why. The condition is written the same way as field logic, with a field, a comparison and a value, for example “Is the order paid? is No”.
Three things make form submission rules different from other form settings. They look at the answers together, not one field at a time. They stop the whole submission, not just one question. And they come with a message, so the visitor knows what to change. A good rule never feels like a locked door; it feels like a signpost.
Form submission rules, validation and field logic: what is the difference?
These three features are easy to mix up, because they all react to what a visitor types. They answer different questions, so a good form often uses more than one.
| Feature | The question it answers | Example |
|---|---|---|
| Field validation | Is this one answer in the right format? | An email address needs an @ sign |
| Conditional logic | Which questions should this person see? | Show “Company name” only for businesses |
| Form submission rules | May this form be sent at all, given the answers? | Block the form while the order is unpaid |
| Conditional confirmations | What should happen after a successful send? | Show a different thank-you page by department |
If you want to change the questions, use conditional logic. If you want to stop the form and explain why, use form submission rules. The two share the same rule editor in FillKite, so the second one feels familiar once you know the first.
When do you need form submission rules?
Use form submission rules when sending the form would waste your time or break a process. These are the most common cases:
- Unpaid orders. Support requests that only paid customers should send.
- Age limits. Events, competitions and products that are for adults only.
- Capacity. Group bookings above the size you can host, which need a quote instead.
- Regions. Quote requests from countries you do not serve yet.
- Eligibility. A scholarship, a trial or a discount that has conditions.
- Missing prerequisites. A request that needs an order number or a document before anyone can help.
- Answers that cannot both be true. A delivery date before the order date, or “no pets” and “two dogs”.
Why hiding the Send button is not enough
The quick fix is to hide or disable the Send button with conditional logic or a few lines of CSS. It works as a demo, but it is a weak way to enforce form submission rules, for four reasons:
- It says nothing. A button that vanishes leaves people guessing what they did wrong.
- It lives in the browser. If JavaScript fails, or someone sends the form another way, nothing stops the entry.
- It is hard for assistive technology. A button that disappears can confuse screen reader users. The Web Content Accessibility Guidelines ask that an error is identified and described in text, which the W3C explains in Understanding Error Identification.
- It cannot offer a way out. A visitor with an unpaid order needs a link to pay, not a missing button.
Real form submission rules fix all four: they explain, they are checked again on the server, they stay reachable for everyone, and they can link to the next step. We covered the short version in how to block form submission in WordPress; this guide goes further.
How form submission rules work in FillKite Pro
In FillKite Pro, form submission rules are called Submit rules. You find them in the form’s Settings tab. A rule has a condition, a message, an optional link with its own text, and a look: a calm warning for something the visitor can fix, or a firmer error for something final.
While a rule holds, three things happen on the page. The Send button looks faded and is marked as unavailable to screen readers, using the aria-disabled attribute. Your message appears in an alert box under the button, with the link if you added one. The moment the answers change and no rule holds any more, the message goes away and the form can be sent. If more than one rule holds, every message is shown.
The same rules are checked again on your server when the form arrives. So they also work with JavaScript turned off and when someone skips the browser entirely. If a rule holds, the entry is refused: nothing is saved, no email is sent, and uploaded files are not stored. Fields that are hidden by conditional logic count as unanswered, exactly as on the server.
Because the button is marked unavailable instead of being removed, keyboard and screen reader users can still reach it and hear why it will not send. That small detail is the difference between a rule that respects people and one that traps them.
How to set up form submission rules in 5 simple steps
- Open the form. In the FillKite builder, go to the Settings tab and choose Submit rules.
- Build the condition. Pick a field, a comparison and a value, the same way as for field logic. For example: Is the order paid? is No.
- Write the message. Say what is wrong and what to do, such as “The order must be paid first.”
- Add a link. Optional but useful: “Pay now”, “Contact us” or “See events for all ages”.
- Choose the look and save. A warning for something the visitor can fix, an error for something final. Then update the form and test it on the page.
The comparisons you can use are the same as in field logic: is, is not, contains, does not contain, more than, less than, is empty and is filled in. You can have several rules on one form, and each has its own message and look. The full reference is in the Submit rules guide.
Seven form submission rules examples
The first four examples are live demos. Nothing you type is saved or sent, so try them freely: pick the answer in the rule and watch the Send button.
1. Support only for paid orders
Rule: Is the order paid? is No. Message: “The order must be paid first.” Link: Pay now. This is the classic case, because it saves your team from answering requests that cannot be helped yet. Try the paid order support demo.
2. An age limit
Rule: Your age is less than 18. Message: “This event is for people aged 18 and over.” Link: See events for all ages. The error look fits here, because the visitor cannot fix their age, so the link offers something else to do. Try the age-limited event sign-up.
3. A group size limit
Rule: Number of guests is more than 40. Message: “Groups of more than 40 need a quote. Please talk to us first.” Link: Contact us. Here form submission rules turn a dead end into a better lead, because the big group is sent to a person. Try the group booking with a size limit.
4. One country only
Rule: Where are you? is not United Kingdom. Message: “We only serve the United Kingdom for now.” Link: Join the waiting list. This keeps out-of-area requests from clogging your inbox while still collecting the people you want to serve later. Try the quote request for one country only.
5. Eligibility for a trial or discount
Rule: Have you used a trial before? is Yes. Message: “The free trial is for new customers. See our plans instead.” Link: See plans. Pair this with a warning look, so it reads as helpful rather than hostile.
6. A missing prerequisite
Rule: Order number is empty. Message: “Please add your order number so we can find your order.” The is empty comparison is useful when a field is optional for most visitors but needed for one kind of request. Combine it with a rule on the request type, using “all of these” so both must hold.
7. Answers that cannot both be true
Rule: Do you have pets? is No, and How many pets? is more than 0. Message: “Your answers do not match. Please check the pet questions.” Use “any” or “all” to match the logic you need. Contradictions are a common source of messy entries, and one clear rule prevents them.
How to write a message that helps
When a rule blocks the form, the message is the whole experience. Form submission rules are only as good as the words under the button. These habits help:
- Say what is wrong, then what to do. “Please confirm your age first” beats “Not allowed”.
- Stay calm. The visitor did nothing wrong. Use the warning look when they can fix it, and save the error look for things that are final.
- Link to the fix. One link with plain words on it: “Pay now”, “Sign in”, “Contact us”.
- Keep it short. One sentence, under the Send button, where people are already looking.
- Do not rely on colour alone. The message is text in an alert box, so it reaches people who cannot see the faded button.
For more on wording, see our guide to form error messages, and for the wider picture, accessible forms.
Common mistakes with form submission rules
| Mistake | What goes wrong | Fix |
|---|---|---|
| Only hiding the button | No explanation, easy to bypass | Use a rule with a message |
| A message with no next step | The visitor gives up | Add a link to the fix |
| Blocking too early | The rule fires before the visitor has answered | Base the rule on an answer that is already required |
| Rules that overlap | Several messages at once | Keep each rule about one thing |
| Not testing on a phone | The message is out of sight | Try the form on a phone and with the keyboard |
| Forgetting the server side | A bot or script skips the browser | Use rules that are checked again on the server |
Can you add form submission rules without Pro or code?
FillKite free shows Submit rules as a locked card with a Pro badge in the form settings, so you can see what they do before you buy. Rules themselves need FillKite Pro 1.2.0 or newer on top of FillKite 1.2.0 or newer, on every Pro plan.
If you write code, there is a developer route. The fillkite_before_save_entry filter lets you return a WP_Error to stop an entry, and on the page window.fillkite.holds() checks whether a set of rules holds for the current answers. There is a worked example in the developer guide.
How do other form plugins handle form submission rules?
We checked each plugin’s public documentation, and for Fluent Forms its plugin code, in October 2026. The short version: this is rarely a one-click setting elsewhere. WPForms documents a code snippet for hiding its Submit button, and Gravity Forms can hide the Submit button with conditional logic but needs code for a message of your own. Fluent Forms has an Advanced Form Validation setting, and the free plugin shows it as available in the Pro version. For a wider comparison, see FillKite as a WPForms alternative or a Fluent Forms alternative.
The side-by-side table on our compare page lists this row along with the rest of the feature comparison. If something looks out of date, tell us and we will fix it.
Frequently asked questions
What are form submission rules?
They are conditions on a whole form that stop it from being sent while certain answers are given, and tell the visitor why. They are different from field validation, which checks one field, and from conditional logic, which shows or hides questions.
How do I stop a WordPress form from being submitted until a condition is met?
In FillKite Pro, open the form’s Settings tab, choose Submit rules, build the condition, write a message and save. The Send button is faded and the message appears while the condition holds, and the form can be sent as soon as it no longer does.
Do form submission rules work without JavaScript?
Yes. FillKite checks the rules again on your server when the form arrives, so a form that should not be sent is refused even without JavaScript. Nothing is saved.
Are form submission rules accessible?
The Send button is marked as unavailable instead of being removed, and the message sits in an alert box right under it. Keyboard and screen reader users can reach the button and hear why the form will not send.
Can I have more than one rule on a form?
Yes. Each rule has its own condition, message, link and look. If several hold at once, every message is shown, so keep each rule about one thing.
Can a rule link to another page?
Yes. Add a link and link text, such as “Pay now” or “Contact us”, so the visitor has a way forward instead of a dead end.
Is this part of the free FillKite plugin?
Submit rules are part of FillKite Pro, on every plan. The free plugin shows them as a locked card so you can see what they do.
Stop a form until it is ready. Form submission rules in FillKite Pro block a form with a clear message and a link, and check again on your server. Read the Submit rules guide, try the live demo, or see what else FillKite Pro adds. The free plugin is on WordPress.org.
Last updated:
