Skip to main content

Managing Closed Stores in Toolio: ACG, ROS & Planning Behavior

In Toolio, closed stores behave differently depending on where you're working — and how their attributes are configured.

Updated yesterday

Assortment Planning (AP)

Closed stores are not counted after their close date. However, they may still appear in cluster groups unless explicitly excluded. To remove them from planning outputs, you can:

  • Uncheck them from clusters, or

  • Filter them out using location attributes like "closed" or "inactive"


Automated Cluster Groups (ACG)

Toolio does not automatically exclude closed stores from ACGs based on their close dates. You need to:

  • Manually deselect them within the ACG editor, or

  • Use attribute filters during cluster creation/editing

This allows flexibility — for example, if you want to maintain visibility of a store that was recently closed.


Why Closed Stores May Still Appear in ACGs

Closed stores are sometimes intentionally retained in clusters:

  • To preserve historical sales context when reviewing trends or building logic

  • To ensure visibility in the Allocation module, where you may still need to report on a store’s past performance

  • Because ACGs don't auto-adjust based on close dates, maintaining this visibility allows for manual control based on your business needs


How to Manually Exclude Closed Stores

Option 1: Deselect the Store in ACG
In the Automated Cluster Group editor, uncheck the “Included” box next to the store. This removes it from calculations and planning outputs.

Option 2: Use Location Filters
Apply filters (e.g., "Status = Closed") to exclude stores from being added to the cluster.


Impact on ROS Calculations

Closed stores can still influence ROS calculations if they are included in a cluster.
To prevent closed stores from affecting ROS, either remove them from the cluster group or set IsSellingLocation = False.


Using Is Selling Location

The Is Selling Location attribute controls whether a location is included in:

  • Clustering

  • Rate of Sale (ROS) calculations

A few key points:

  • If set to False, the location is excluded from planning logic but remains visible in lists and reports.

  • It's a good way to retain a store in the system (for historical or operational context) without letting it influence cluster logic.

  • This setting can be configured in:
    Configuration > Organization Settings > Locations
    or accessed via cmd + k search.

Example:
You might set IsSellingLocation = False for a closed store that you no longer want factored into AP logic — but still want to appear in the Allocation module or sales reports.


Best Practice

  • Use IsSellingLocation = False for any location you want to exclude from clustering and ROS, while still maintaining visibility in reports.

  • Combine this with custom attributes like "Status = Closed" for flexible filtering.

  • Always create a new snapshot after making any changes, so updates reflect in your Assortment Plan.

Did this answer your question?