Row Validation Rules

Documentation Index

Fetch the complete documentation index at: https://docs.getveles.com/llms.txt

Use this file to discover all available pages before exploring further.

Row Validation Rules evaluate individual Quote Lines — single products on a Pricing Option. Unlike Quote Validation Rules, which look at the deal as a whole, Row Validation targets specific products or line items and surfaces feedback directly on the affected row. The primary advantage is granularity. When a Row Validation rule fires, the alert appears on the exact line item that triggered it. The rep doesn’t have to search through a long quote to figure out which product has a problem — the issue is flagged right where it occurs. Use Row Validation Rules when the condition is about a specific product’s pricing, discount, quantity, or category — not the overall deal structure.

---

​

When to use Row Validation

Row Validation is the right kind when:

• The condition applies to a specific product or SKU (not the deal total)
• You need to enforce a per-line discount cap or price floor
• The rule should fire for a specific product category regardless of what else is on the deal
• You want the alert to appear on the line item itself for immediate clarity
• The constraint involves quantity minimums or unit-level pricing for a particular product

For deal-level constraints (total discount, TCV thresholds, required product combinations), use Quote Validation Rules instead.

---

​

Creating a Row Validation Rule

1. Navigate to Admin Console > Price Books > Rules.
2. Click Create New Rule.
3. Set the Kind to Row Validation.
4. Enter a Name and Description.
5. Set the Status to Active.
6. Click Save, then click New Rule Set to build the logic.

---

​

Building the rule set

​

Scope

For Row Validation rules, the scope is Row — the rule evaluates each line item individually. If a quote has 5 line items, the rule is checked against each of the 5 independently.

​

Available facts

These are the data points you can build conditions against for each line item:

​

Operators

​

Combining conditions

Add multiple conditions to target a specific product with a specific constraint. All conditions must be true for the action to fire. Example: A rule that triggers only on the Platform product when its discount exceeds 15%:

• Condition 1: Product SKU equals PLATFORM-001
• Condition 2: Row Discount ≥ 15

Without the SKU condition, the discount rule would fire on every line item. Adding the SKU condition scopes it to one product.

---

​

Actions

​

Message

The message appears directly on the affected line item. Write messages that are specific to the product and the problem, since the rep is looking at the exact row. Good examples:

• “Platform discount exceeds 15%. Requires Sales VP approval.”
• “This custom integration requires an engineering scoping call before the quote is sent.”
• “Minimum order quantity for this product is 10 units.”
• “This product cannot be sold below $500/unit.”

​

Severity

​

Approval routing

Toggle Requires Approver and select an Approval Tier. When the row rule fires, the deal is routed for approval at the specified tier. The alert on the line item shows which tier needs to sign off.

---

​

Examples

​

Per-product discount cap

Limit the discount on a high-margin product that reps tend to over-discount.

​

Price floor

Prevent a product from being sold below cost.

​

Quantity minimum

Enforce a minimum order quantity for a specific product.

​

Engineering review flag

Flag products that need technical review before the deal is sent to the buyer.

​

Category-wide discount limit

Apply a discount cap to an entire product category rather than individual SKUs.

---

​

The rep experience

When a Row Validation rule fires on a line item:

1. A warning or error icon appears directly on the affected row in the Calculator.
2. Clicking or hovering on the icon displays the custom message.
3. If severity is Warn, the rep can continue building the quote but cannot publish until the issue is resolved (either by fixing the line or getting approval).
4. If severity is Error, the rep must fix the line item (adjust price, discount, or quantity) before the quote can be saved.
5. If an approval is required, the line-level alert shows which tier needs to sign off.

Because the alert is on the specific row, the rep knows exactly which product needs attention. For quotes with many line items, this is significantly clearer than a deal-level alert that says “something on this quote needs review.”

---

​

Row Validation vs. Quote Validation

You can (and should) use both kinds together. Row Validation handles product-specific guardrails. Quote Validation handles deal-level guardrails. They complement each other.

---

​

What’s next