Price Guidance Compliance Agent (Configuration)

The Price Guidance Compliance Agent monitors whether quotes or transactions comply with your pricing-guidance rules (floor, target, stretch) and flags any violations requiring corrective action.

Create Agent

1. Go to Pricefx Agents > Agents.

2. Click Create New Agent.

3. In the Create New Agent menu:

   1. Enter the Agent Name.

   2. Enter a Label for the Agent (optional).

   3. In the Type field, select Flex Agent.

4. Click Create.

Definition

Agent Type

In the Select your agent field, select Price Guidance Compliance Agent.

Configure Agent

Negotiation Guidance Model – Select an existing Negotiation Guidance Model that is in Ready status. This model serves as the source of truth for pricing guidance.
Model Optimization Type – This read-only field displays the metric optimized by the selected model (e.g., Margin %, Discount %). It is automatically pre-selected based on the Negotiation Guidance Model.
Source – Indicates the Datamart (Data Source) containing the transaction data to be analyzed. This value is typically pre-filled based on the Negotiation Guidance Model’s configuration but can be modified.
Scope (Customer Scope/Product Scope/General Filter) – Optional filters that restrict the set of transactions to be analyzed (e.g., by business unit or time period).
Scope's Currency – The currency in which price guidance values are displayed for this agent. When the Source is a Data Source (DS), the default is USD. When the Source is a Datamart (DM), the default is the Datamart's base currency. Changing this setting does not convert existing values.

Mandatory Field Mapping

This crucial step allows you to map abstract elements from the Negotiation Guidance Model (such as segmentation fields, revenue, and quantity) to the corresponding fields in the Datamart (Data Source). This section is collapsed by default and automatically pre-filled with the settings from the selected Negotiation Guidance Model.

Compliance Criteria

This section defines when a transaction is considered non-compliant.

Guidance Metric – This field defines which Negotiation Guidance threshold to compare against:

•  Floor

•  Target

•  Ceiling

Condition – Defines whether a transaction is non-compliant based on whether the metric is:

• Below – Specifies cases that fall below the selected metric.

• Above – Specifies cases that fall above the selected metric.

Metric Offset –  A tolerance percentage. For example, a 2% offset for a “Below Floor” condition means that the Agent will only flag transactions more than 2% below the floor price. (Optional)

Detection Rule

This section defines how issues are flagged, particularly when data is grouped.

Calculated for (Group By) – Allows you to select one or more fields to group transactions (e.g., Salesperson, Country). If left empty, the Agent runs in transaction-level mode.
Rule type – Required when grouping is used:

• % of cases – Flags the group if the percentage of non-compliant transactions exceeds a threshold.

• % of revenue – Flags the group if the percentage of revenue from non-compliant transactions exceeds a threshold.

Threshold – The threshold percentage for the selected rule type (e.g., flag a Sales Representative if more than 10% of their cases fall below the floor).

Impact Calculation

This section defines how to estimate the financial impact of non-compliance.

Closer to Threshold by – A percentage (1–100%) used to determine the “suggested” metric. For example, if a deal is 10% below the floor and this parameter is set to 50%, the suggested metric will be halfway between the current value and the floor. This value is used to calculate Potential Revenue and Potential Profit.

Performance

Limit amount of transactions for preview – Restricts the number of rows loaded into the configurator’s live preview to maintain responsiveness. This limit applies only to the preview, not to full Agent execution.

Summary Table

Difference to Threshold – The amount by which the current metric (e.g., unit margin) deviates from the selected guidance threshold (floor/target/ceiling, including any configured offset).
Threshold Unit Margin – The guidance value used for compliance (chosen from the Negotiation Guidance floor/target/ceiling for unit margin), optionally adjusted by a user‑defined offset in the compliance criteria.
Potential Revenue – The estimated additional revenue if the unit margin on the item is raised from the current level to the suggested level while holding the current quantity constant; operationally, it sums per‑unit margin uplift times current quantity.
Potential Profit – The estimated additional profit if the unit margin on the item is raised from the current level to the suggested level while holding the current quantity constant; because unit margin is profit per unit, this equals the revenue uplift expression in the unit‑margin case.
Current Unit Margin – The profit per unit realized at the current level. Conceptually gross margin divided by quantity.
Suggested Unit Margin – The proposed unit margin obtained by moving from the current unit margin toward the guidance threshold.

Schedule

Configure the preferred start date and frequency for Agent execution.

Start Date – The first execution date.
Period – Defines the period type.

• Day

• Month

• Year

Interval – The number of repetitions within the selected period. Valid characters: 0–9. An interval of 0 indicates a one-time execution.

Action Definition

This step defines actions which will be created by the Agent once the alert conditions are met so that the specified user can address the detected problem or opportunity. The Agent creates Actions on the row level in the Detected Insights (i.e., if there are 5 rows in the identified data, 5 actions will be created).

• Group Actions by – Detected Items are grouped based on the fields defined in this configuration option. The Group Actions by setting controls how Detected Items are aggregated into a single Action. The list of available fields is derived from the fields defined in the Group By configuration option in the Definition step.

• Keep Top Actions – Only Detected Items with the highest potential impact, based on the first impact defined in the Impact Definition are considered. There is a system-enforced maximum limit of 500 Actions. If the configured value exceeds this limit, it is automatically reset to 500. The default limit is 20 Actions.
  A value of 0 indicates that there is no functional limit; however, the system limit of 500 Actions still applies.

1. Click the Add Action button.

2. Enter a Summary to identify the Action.

3. Add a Description with details of the action for the user.

4. (Optional) Select the Due Date. The due date will be relative to the date when the action is created (now in the menu options means the day when the action will be triggered).

5. In Assign To select to whom to assign the Action (a single 'fallback' assignee). If no one in “Assign to per Dimension” is set or no user is found based on the mapping defined there, then this fallback assignee is set for the Action.

6. In Assign to per Dimension, you can select users to whom the Action will be assigned based on the value of any dimension of the selected series from the Definition. Mapping to users is set for the values of the selected dimensions.
   The fields available for the Assign to per Dimension option are now limited to the dimensions selected in the Group Actions by configuration option. If no grouping field is selected, the assignment behavior remains unchanged.

7. (Optional) Select the Action Plan and the specific Action Group to which this Action will be connected. Action Plans allow you to group Actions created by a Agent together by their nature. Action Groups are wrappers for Actions under one Action Plan.

8. (Optional) Add a Dashboard that will be displayed in the Action detail. You can select any dashboard but only Sales Insights and Customer Insights dashboards are fully supported. Other dashboards can be used with limitations, for example, some inputs will not be recognized and values will have to be entered manually by the user. Dashboards will only work properly if their data source is the same as the data source of the Agent.
   Embedded dashboard's context (Product / Customer filters) is defined by the dimensions in the Detected Insights table. Only those dimensions which are synchronized with Customer Master of Product Master will be applied to the dashboard's filters. They will be mapped to existing fields in Product / Customer Master tables and applied as default filters.

9. Click Continue.

Impact Calculation

Define specific metrics to calculate the expected impact of actions. Use total absolute values only, as these metrics will be aggregated.

Summary

Review the full configuration of the Agent. If everything is correct, click Submit for Approval. Once approved, the Agent becomes active and begins monitoring your data according to the defined schedule.