Skip to main content

​
Overview

Automation rules evaluate every quote that arrives in your Inbox and stage a response for you — reject the ones below your floor, counter the ones worth countering, flag the ones that need a human eye. Your team starts each session from a triaged queue instead of a raw one. Rules live in Settings → Automations .

​
How rules behave

Four principles are worth knowing before you write your first rule.

Rules never auto-send

A matching rule stages its action — as a basket item, a counter draft, a note, or a flag. A person still reviews and sends. Staged items are marked in the basket.

First match wins

Rules evaluate in priority order and stop at the first one that matches. Put narrow rules above broad ones.

Arriving quotes only

Rules fire when a quote arrives. Re-arrival of the same quote doesn’t fire them a second time.

Schema-driven

The available fields, operators, statuses, and actions come from the platform, so new options can appear without any change on your side.

​
Managing rules

The rules table shows priority position, name, type, an Enabled switch, and per-row actions.
  • Add rule — give it a name, choose a type, and fill in the type’s form.
  • Priority — drag the handle to reorder. Position #1 runs first. There’s no priority number to enter; list order is the priority.
  • Enabled — switch a rule off without deleting it.
  • Edit and Delete — from the row actions.

​
Execution Log

Every rule has its own Execution Log , a newest-first timeline of what the rule actually did. Each entry names the material number and manufacturer, the partner, the quantity and unit price, and the margin and margin % of the offer that matched — or the error, when the rule failed to run.
The log records only matched-and-acted and error outcomes. Routine non-matches are omitted, so an empty log means the rule has never matched or errored — not that it never ran.

​
Health checks

Qualification rules point at columns in your reference data and attributes on your programs. When those change underneath a rule, it can silently stop resolving — so rules are re-checked whenever reference data is refreshed, and a warning indicator appears beside any rule whose operands no longer resolve. The warning names the exact condition and side, for example “Condition 2’s left operand references warehouse_qty, which is not in your current reference columns.”
Health is recomputed on a reference-data refresh, not when you save a rule. Every surface that shows a health indicator also shows when it was last checked — a rule you just fixed keeps its stale warning until the next check.

​
Rule types

Act on a single arriving quote when it satisfies your conditions.Filters — narrow which quotes the rule applies to, by Inbox statuses (actioned, not actioned, unassigned, pending, closed), Approval statuses, and Thread statuses. Leave a filter empty to apply to all.Conditions — one or more comparisons, all of which must hold. Each pairs a field (margin, margin %, unit price, or quantity) with an operator (greater than, greater than or equal, less than, less than or equal, equal to) and a value.Action — what to stage on a match:
  • Action — reject, accept, counter, or note
  • Reject reason — required when the action is reject, chosen from your configured reasons
  • Message — the text carried with the action
  • Target thread — this thread, or the latest quote in the group
  • Target price — a fixed value, a template, or the threshold price
Example — “When a quote arrives on a not actioned thread with margin ≤ $500, stage a reject with reason Price too low.”

​
Template variables

Fields marked as supporting variables — messages, internal comments, and target prices on comparison-rule branches — accept these placeholders, filled in when the rule runs:
Use the variable picker on the field rather than typing the braces by hand — it only offers the variables that field actually supports.

Inbox

Where staged actions land for review before they’re sent.

Approvals

Route responses through approval when a flow requires it.

Reference Data

The columns qualification rules resolve against.

Programs

The attributes qualification rules resolve against.