Post-save metric rules let you automatically copy or transform metric values after a save. They’re designed to support cross-dimension updates, operational flows (like transfers or returns), and repeatable post-save adjustments - without requiring manual recalculation.
These rules run after data is saved. Either automatically upon saving the metric changes, or after a user manually executes a rule to run.
Please note that the automated rules only run after a manual save operation, not after functions such as merging, seeding, forecasting, or receipt generation.
What are post-save metric rules?
A post-save metric rule defines how values from one metric and dimension set (the source) are applied to another metric and dimension set (the destination) after a save.
Each rule is made up of:
Dimension mappings – Merchandise plan attribute dimensions where data is read from and written to
Metric mappings – which metrics are copied or aggregated
Execution mode – automated or user-triggered
Each rule has both Source and Destination mappings of Dimensions and Metrics.
These rules are commonly used to:
Keep related metrics in sync across dimensions
Apply operational logic consistently after every save
Support controlled, repeatable transformations of saved data
Execution modes
Post-save metric rules can be executed in one of two ways.
Automatic Rules
Run automatically after a save completes
Only execute when the save impacts the rule’s source metric
Execution is isolated to the source and destinations of the rule
Applies across all scenarios
Best for: logic that should always stay in sync with saved data
Manual Rules
Run only when explicitly triggered by a user
Applied to a selected plan, date range, scenario, and filter scope
Execution is still isolated to the source and destinations of the rule
Can execute specific rules individually or all eligible rules in scope
Best for: targeted updates, backfills, or controlled recalculations
Rule Definitions
Dimension mappings
Each rule includes one or more Merchandise Plan dimension mappings that define:
One or more source attribute values
A single destination attribute value
A dimension can be defined by up to 2 Merchandise Attributes (i.e. Region = USA, Channel = Web).
Metric mappings
Metric mappings define how values are calculated:
Source metric – where values are read from
Destination metric – where results are written
Aggregation method – used when multiple source values map to one destination, defaults to none, but can be set to SUM
Please note that Metrics can be the same for both Source & Destination - OR - Dimensions can be the same for both Source & Destination, but not both.
Currently Metric Rules cannot be directly configured within the Toolio UI, but you can reach out to your Customer Success team with a list of rules formatted in the structure outlined here and they can help you configure and enable the rules.
Rule Execution
Any automatic rules will run as long as the source metric is changed and saved. For manually executed rules, you can simply right click and access the manual rules via the function menu in MP - clicking Execute Post-Save Metric Rules will open a popup allowing you to select which manual rule(s) you'd like to trigger.
When a rule runs:
Source metric data is filtered using the configured source dimensions
Any aggregation necessary occurs, and the results are written to the destination dimensions
As mentioned above, multiple Merchandise Plan attributes can be defined together as a dimension (for example, Region and Channel).
When a rule is triggered, you will find an item in your task manager which can be used to track the progress. Upon completion, you will also be prompted to refresh the data in your view.
As a simple example configuration:
Rule Name | Source Metric | Destination Metric | Attribute 1 | Source Attribute 1 | Destination Attribute 1 | Type |
Dropship Sales > Receipts | Gross Sales Units | Receipts Units | Channel | Dropship | Dropship | Auto |
If a user updates Gross Sales Units and makes a save, this rule will run:
It will check to see if Channel = Dropship's Gross Sales Units was impacted (either directly by the changes or due to indirect spreading/distribution)
If the above criteria is met on the source attribute dimension, then the system will output (copy) the values to the Receipt Units metric, also for Channel = Dropship
This rule helps maintain parity between Gross Sales Units and Receipts Units metrics under the Channel = Dropship dimension. Please find more generalizable examples below:
Generalized examples
Example 1: One-to-one copy across dimension values
Use case: Keep two related dimension values aligned after save.
Source Dimension: Attribute A = Value 1
Destination Dimension: Attribute A = Value 2
Source metric: Metric X
Destination metric: Metric Y
Result:
After Metric X is saved for Value 1, Metric Y is automatically updated for Value 2.
Example 2: Aggregation from multiple source values
Use case: Roll up multiple source values into a consolidated destination.
Source Dimension: Attribute B = Value 1, Value 2
Destination Dimension: Attribute B = Value 3
Source Metric: Metric Z
Destination Metric: Metric Z
Method: SUM
Result:
Metric Z for Value 3 is set to the sum of Metric Z across Value 1 and Value 2.
Example 3: Multi-dimension transformation
Use case: Apply consistent logic across combinations of dimensions.
Source Dimension: Attribute A = Value 1, Attribute B = Value 2
Destination Dimension: Attribute A = Value 3, Dimension B = Value 4
Source metric: Metric X
Destination metric: Metric Y
Result:
Metric X is copied from the source combination to Metric Y of the destination combination after save.