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.
How do I price irrigation services by zone count?
Record the number of zones in a numeric Site field. Then choose the approach that matches your service policy: fixed prices for bands of zone counts, or a formula that calculates the rate from the number of zones. Zone count is a field your business configures, not an assumed value on every property.
Here is an illustrative winterization policy using bands. These are example rates, not market recommendations or a preconfigured ServeCommand price list.
| Site has | Pricing action | Service rate |
|---|---|---|
| 1–4 zones | Set to a fixed amount | $100 |
| 5–8 zones | Set to a fixed amount | $140 |
| 9–12 zones | Set to a fixed amount | $180 |
| A pump requiring extra work | Add a fixed amount after the zone rule | +$35 |
With this policy, a six-zone property with a pump is $140 + $35 = $175. A property with more than 12 zones needs another band or an explicit review policy; the example does not cover it.
Can I use a formula and a pump fee together?
Yes. A formula can calculate a rate using the configured numeric Site field, and a separate matching rule can add the pump fee. For example, $60 + zones × $10, followed by +$35 when Pump is Yes, produces $155 for six zones with a pump.
Use the formula or the bands according to your intended policy. Applying both would change the result. Put the pump addition after the rate-setting action: a later Set to action would replace the running total. A yes/no Site field can represent the pump condition when it is configured for the relevant service category.
Check the policy before your team uses it
- Confirm that zone count and pump details are recorded correctly for the Site.
- Test the edges of each band, such as four and five zones.
- Test a property with a pump, one without, and one outside your defined bands.
- Check a property with missing details. Missing numeric formula inputs are treated as zero, so incomplete data can produce an unintended rate.
- Review any saved Site-specific price or membership commitment before replacing it.
These are checks for configuring your policy, not a claim that every incomplete property is automatically blocked.
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.