Conditional pricing lets you define when a service price should change and how to calculate that change. Saved rules give the team a repeatable calculation for new work.
Conditions describe when a rule applies
Service pricing conditions can use a Site’s state, city, distance from the office, and structured Site data. Supported Site fields include numbers, yes/no values, and single-choice or multiple-choice values.
For irrigation work, a numeric Site field might describe the number of zones. A rule can use that field when it has been configured for the service category and the Site has a recorded value.
Office distance is straight-line distance. It is not a driving route or a travel-time estimate.
Actions describe what happens to the price
A pricing action makes two choices:
| Choice | Meaning |
|---|---|
| Set to | Replace the running rate with the rule’s amount or formula result. |
| Add | Add the rule’s amount or formula result to the running rate. |
| A fixed amount | Use an amount defined in the rule. |
| A formula | Calculate an amount from numeric Site fields and arithmetic operations. |
The distinction between setting and adding matters. Setting defines a rate; adding builds on a rate. Choose the behavior that matches the policy you intend. Matching rules run in order, so a later Set to action can replace an earlier result.
Example: pricing by irrigation system size
Suppose your startup service includes a base amount, with additional pricing for larger systems. If your Site records include zone counts, you can express the additional amount through a formula using that numeric field.
Before relying on the rule, compare a few representative Sites: a small system, a larger system, and a Site without the required detail. Check that the recorded inputs and calculated result match your policy. Missing numeric formula inputs are treated as zero, so test that case deliberately.
This example describes a possible configuration. It does not prescribe your rates or create a rule automatically.
Missing information needs review
A calculation is only as useful as its inputs. If a distance rule cannot be evaluated because the Site or office coordinates are unavailable, pricing review identifies that limitation and shows the available calculation separately.
A manual price or a saved Site-specific rule can also differ from the broader company calculation. Review the reason before changing a customer price. Agreed membership rates require their own context.