Validation rules
Define checks that run as data is entered — on staff-facing forms, client-facing forms (the booking request), or both. Pick a field (client, pet, booking, expense or invoice), choose a rule (required, min/max length, numbers only, number range, letters only, valid email, phone, postcode, date range, one-of-a-list, starts with, or a regular expression), and optionally set a custom message. Optional fields stay optional — only the "Required" rule fails on an empty value.
Example
You add a rule that the client phone must be a valid number, applied to client-facing forms — now a booking request with a bad phone number is rejected with a clear message before it’s saved.
FAQ
Where are rules enforced?
Anywhere the plugin validates input — currently the public booking request form. Rules are scoped to an area (client, pet, etc.) so they only apply where relevant.
Does a rule block optional fields?
No. Every rule except “Required” passes when the value is empty, so optional fields remain optional.
Can I write my own pattern?
Yes — the “Matches a pattern” rule takes a regular expression, e.g. ^[A-Z]{2}[0-9]{4}$.
When are the rules checked?
On the client, pet and expense screens, each time you leave a field, and again when you save: the record is not saved until every rule passes, and the field that needs attention is outlined in red with the message under it. Client details added in the staff app are checked too, and so are booking requests from customers if the rule applies to customer forms.
Are rules checked on the New client wizard?
Yes. Each Next checks the fields on that step, so a missing phone number is caught on the first step, before you move on. Create checks everything again, and so does the server.
How do I change a rule?
Press Edit beside it under Current rules. The rule opens in the form below; change it and press Save rule. The boxes a rule needs appear only for rules that need them, named for what they are, such as Minimum and Maximum, or Earliest and Latest date.
Was this helpful?
Thanks for letting us know.
Sorry this did not answer it. Thanks for telling us: we use it to improve the guides.
Still need help? Sign in to your account and raise a support ticket. The people who wrote the code will help, and most tickets are answered the same working day.