Rule order, default and loops
Updated November 9, 2026
The first matching rule wins
KodaFill checks the rules from top to bottom and stops at the first one whose conditions are true. Put specific rules above general ones. For example, put Plan is Full camp and Age is less than 10 above Plan is Full camp. Reorder rules with the ↑ and ↓ buttons.
If no rule matches
The If no rule matches value is used when no rule is true. It works like a last rule that always matches, and can use merge tags and {today} values. A field can have only this value and no rules: for example a Pay by date of {today+14}, or a message built from merge tags.
Leave it empty and the field is cleared when nothing matches (or left alone, with Fill it only if it’s empty).
Fields that depend on filled fields
A rule can look at, or copy, a field that KodaFill fills too. KodaFill handles the chain: when field A changes, B is filled, then C, which looks at B, is filled. On submit, KodaFill goes over the form up to five times until every value settles.
Loops
If fields fill each other in a circle (A looks at B and B looks at A, or a longer circle), the KodaFill tab shows a warning naming the fields, for example These fields fill each other in a loop: Price → Total → Price. The values may then never settle, so change the rules to break the circle.
Thanks for letting us know.
