---
title: Collection imports now warn on typos instead of guessing
date: 2026-09-01
description: Collections imports report unrecognized Must Match, Rule: Mode, and exclude-rule values, and skipped source blocks on REPLACE, instead of applying a silent default.
tags: ["Smart Collections","Imports"]
categories: ["Changelog"]
url: https://www.getaltera.com/changelog/2026-09-01-collection-import-warnings-for-typos/
---


A typo in a collection rule used to be applied silently as the default value, which could quietly change which products a collection holds. The Collections import now tells you when it can't read a value and leaves your existing rules alone.

### Fixes

- **Must Match typos** - an unrecognized value such as `anyy conditions` no longer silently means all conditions. The import warns and keeps the source's current matching logic. Short forms like `any` and `all` are accepted (see [Must Match](../reference/collections.md#sources-must-match)).
- **Rule: Mode typos** - a value such as `Exclud` no longer lands the rule in the include set. The row is skipped with a warning so an exclude rule can't invert into an include rule.
- **Unsupported exclude rules** - an exclude rule on a column such as `Title` now reports a warning, matching how include rules already behave, instead of vanishing without a trace.
- **Skipped source blocks on REPLACE** - a stray `Source Command` of DELETE or IGNORE on a collection REPLACE (or a new collection) now reports which source was skipped, so a REPLACE can no longer complete as a silent no-op.

