Today, Toolio users often need insights that combine or transform data across multiple datasets—such as sales, inventory, receipts, and purchase orders. Because these data points live in separate tables, users frequently rely on the dev/data team to create custom fields, which leads to:
Delays in decision-making
Reduced user autonomy
Limited flexibility of Toolio as a self-serve analytics and planning platform
The Calculated Attributes feature addresses these challenges by enabling users to define their own custom attributes directly in Toolio.
Overview
Calculated Attributes allow users to create new attributes based on existing master data and transaction tables by applying filters, relationships, and aggregation logics all through a no-code UI.
Key benefits:
Self-service creation of custom attributes
Ability to combine multiple data sources
Flexible use across dashboards, exports, and planning modules
No engineering involvement needed for common analytical metrics
1. Use Cases
Examples of insights unlocked through calculated attributes:
Sales & Performance
First Sale Date
Last Sale Date
Average Sales per Week/Day/Month
Inventory & Operations
First Receipt Date
First Expected Receipt Date
Last Out-of-Stock Date (OOS)
These examples often require joining tables like Sales, Inventory, and Receipts something now possible without technical assistance.
2. Creating a Calculated Attribute
Navigate to:
Settings → Intelligence → Calculated Attributes
Define the attribute using:
1. Model
Variant
Variant + Location
Actual Choice
2. Attribute Name
The label for your new field.
3. Data Source
Sales
Inventory
Receipts
Purchase Order
4. Filters
Customize which data rows are included:
Time range
Channels
Inventory thresholds
Product attributes
Location attributes
5. Field to Aggregate
Examples:
Sales Quantity
Sales Retail
Receipt Date
On-Hand Inventory
6. Aggregation Method
Sum
Average
Min / Max
First / Last
Count / Count Distinct
Simple custom logic
3. Key Decisions & Constraints
UI-Only: No scripting or formulas, fully UI-driven.
Independent Workflow: Calculated Attributes do not interfere with imports or populate-metrics logic.
Scheduled Recalculation: Run daily in a nightly scheduled job.
Immediate Calculation: Users may trigger a manual recalculation.
Single Data-Relationship Constraint: Each calculated attribute references only one source table in V1.
4. Viewing Calculated Attributes in the Assortment Plan Module
Once you create a calculated attribute on the Actual Choice model, you can visualize and analyze it directly inside the Assortment Plan module.
Follow the steps below:
Step 1: Navigate to Assortment Plan
Go to:
New Assortment Plan
Open the relevant assortment plan view.
Step 2: Add the Calculated Attribute as a Column
Click on the Attributes menu.
Search for the name of your newly created calculated attribute.
Select it to add it as a column in your plan view.
Calculated attributes behave like standard attributes and can be:
Added as visible columns
Used in sorting
Included in exports
Step 3: Filter to Relevant Choices
To easily identify choices that contain values for the calculated attribute:
Open the Filters panel.
Add a filter:
Actual Choice ID → is not empty
This ensures the view focuses only on records where the calculated attribute is populated at the Actual Choice level.
Best Practices
If you don’t see values immediately, ensure the calculation has completed (scheduled run or manual “Trigger Now”).
Confirm the attribute was created on the correct model (Actual Choice).
Use sorting to quickly analyze high/low values.
5. FAQs
Can I use multiple tables (e.g., Sales + Inventory) in the same calculated attribute?
Not in this version. Each calculated attribute must reference a single data source. Multi-table calculations are planned for future phases.
How often do calculated attributes update?
They are recalculated automatically on a daily schedule. You can also trigger an immediate recalculation from the UI.
Will calculated attributes slow down imports or planning workflows?
No. The calculation engine is fully decoupled from import workflows, ensuring no performance impact on core data pipelines.
Can I use calculated attributes in dashboards, exports, and planning tools?
Yes. Once created, your calculated attributes behave like any other field and can be used throughout the platform anywhere attributes are supported.
Can I write formulas (e.g., Excel-style expressions)?
Not in V1. The feature is UI-only with structured filter and aggregation options. Formula-based or scripted logic may be considered for later phases.
Can I filter by product, channel, or location attributes?
Yes. Filters support product-level, location-level, inventory thresholds, time windows, and channel constraints.
What happens if I delete or rename a calculated attribute?
Deleting: The attribute will be removed from all dashboards, planning pages, and exports that reference it.
Renaming: The name will update everywhere it is used without breaking dependencies.