---
title: Collection imports catch typos in rules
date: 2026-09-02
description: Collection imports now warn about unrecognized Must Match, Rule: Mode, and exclude-rule values instead of quietly applying a default.
tags: ["Smart Collections","Imports"]
categories: ["Changelog"]
url: https://www.getaltera.com/changelog/2026-09-02-collection-import-warnings-for-typos/
---


A small typo in a collection import file, such as `anyy conditions` or `Exclud`, used to be read as the default value. Nothing in the import results told you, but the products in the collection could change. Collection imports now report these values as warnings and leave the affected rule alone.

### Fixes

- **Must Match** - an unrecognized value no longer switches a source to all conditions; the import warns and keeps the current matching logic (see [Must Match](https://support.getaltera.com/en/articles/15945044-collection-fields#sources-must-match)).
- **Short forms** - `any`, `all`, `any conditions`, and `all condition` are accepted for Must Match, and the value is no longer case sensitive.
- **Rule: Mode** - a value other than Include or Exclude skips the row with a warning, so a typo can't turn an exclude rule into an include rule.
- **Exclude rules** - an exclude rule on an unsupported column such as Title now reports a warning, the same as include rules already do.
- **Stray source commands** - on a REPLACE or a new collection, a source block marked DELETE or IGNORE is reported by name instead of dropped without a trace.

All of these warnings use code CLTN009 (see [error codes](https://support.getaltera.com/en/articles/11490216-error-and-warning-codes#CLTN009)). The Must Match check also applies to the legacy Smart Collections import.