--- title: Matrixify error "Smart Collection does not exist": what causes it and how to fix it date: 2026-09-01 description: Getting "Command is UPDATE, but the Smart Collection does not exist" in Matrixify? Shopify's new collections model is hidden from apps that haven't updated. Here's what's happening and how to update those collections with Altera. url: https://www.getaltera.com/matrixify-collection-does-not-exist/ --- You export a collection with Matrixify, edit the file, change the command to `UPDATE`, and the import fails: > **Command is UPDATE, but the Smart Collection does not exist.** The collection is right there in your Shopify admin. The ID and Handle in your file are correct. You may have exported the same collection minutes earlier. Matrixify still reports that it does not exist. The error is accurate from Matrixify's point of view. In July 2026, Shopify replaced smart and manual collections with a [new collections model](/blog/2026-07-15-shopify-collection-sources/), and Shopify hides collections that use the new model from apps that have not updated to support it. Matrixify does not support the new model, so those collections are invisible to it. When it looks up the ID or Handle from your file, Shopify returns nothing. **Altera** supports the new collections model in full, reads and writes the same spreadsheet format, and can run the same `UPDATE` import that Matrixify is failing on. --- ## Why the collection "does not exist" Shopify's new model replaces the old smart/manual split. Every collection is now built from one or more **sources**, and a single collection can combine automated rules, hand-picked products or variants, other collections, and app-provided product groups. To see these collections, an app has to be updated for Shopify's 2026-07 API version. Shopify hides new-model collections from apps that have not updated, with no error and no placeholder. The app simply never sees them. That is what produces this error. A collection crosses into the new model as soon as it uses any new capability, and the new admin editor makes that easy to do without noticing. Adding hand-picked products to a rule-based collection, removing the rules and positioning products manually, adding an exclusion, or building a collection from other collections all count. From that moment, the collection is hidden from Matrixify. An `UPDATE` import that matched last week fails today because someone edited the collection in the Shopify admin in between. This also explains the confusing case where Matrixify exported the collection and then can't find it on import: the collection was edited into the new model after the export, or the export itself came from an older file. The store didn't lose the collection. Matrixify lost the ability to see it. --- ## Don't switch the command to MERGE The tempting workaround is to change `UPDATE` to `MERGE` so the import stops failing. Don't. When `MERGE` finds no matching collection, it creates a new one. Since Matrixify cannot see the real collection, you get a duplicate: the original (invisible to Matrixify, live on your storefront) plus a new legacy-model copy with the same title. `REPLACE` has the same problem in a worse form, since it deletes and recreates. The failed `UPDATE` is the safe outcome. It tells you the tool can't see the collection, without touching your store. --- ## There is no fix inside Matrixify There is no setting or workaround inside Matrixify that makes the collection visible again. Matrixify does not support the new collections model. Our [page on Matrixify and Shopify's new collections](/matrixify-collection-sources/) covers the full gap. --- ## How to run the update with Altera Altera supported the new collections model [from day one](/changelog/2026-07-15-unified-collections-data-type/) and sees every collection in your store, old model and new. It reads and writes the same Matrixify-compatible spreadsheet format, so the file you already prepared carries over. 1. **Install [Altera](https://apps.shopify.com/altera-import-export-excel)** from the Shopify App Store. There is a free plan, and your Matrixify files work as-is. 2. **Export the Collections data type.** Altera uses a single unified Collections sheet instead of separate Smart and Custom Collections sheets, and the export includes every collection, with extra columns describing each collection's sources. 3. **Make your edits and import with `UPDATE`.** The command semantics you know apply, and the lookup by ID or Handle finds the collection because Altera can see it. Beyond fixing the lookup, Altera imports and exports the full new model: rules and hand-picked products in the same collection, exclusions, subcollections, variant-level collections, and app sources. A `Source Command` column lets you update or delete a single source without touching the rest of the collection. The [collection fields reference](https://support.getaltera.com/en/articles/15945044-collection-fields) documents every column, and the help center has a full write-up of [how Altera handles Shopify's new collections](https://support.getaltera.com/en/articles/15945043-how-altera-is-handling-shopify-s-new-collections). --- ## Frequently asked questions **Why does Matrixify say my collection does not exist when it does?** The collection uses Shopify's new collections model, and Shopify hides new-model collections from apps that have not updated to the 2026-07 API version. Matrixify has not updated, so when it looks up the collection by ID or Handle, Shopify returns nothing and Matrixify reports it as not existing. **I get the error on a Custom Collections import too. Same cause?** Yes. The visibility rule applies to the collection, not the sheet type. Any collection edited into the new model is hidden from Matrixify whether your file treats it as a Smart Collection or a Custom Collection. **What made my collection switch to the new model?** Any edit that uses a new capability: hand-picking products on a rule-based collection, replacing rules with manually positioned products, adding exclusions, including another collection as a source, or selecting individual variants. Shopify's new collection editor allows all of this directly, so a routine merchandising edit is enough. **Does Matrixify support Shopify's new collections?** No. Its Smart Collections and Custom Collections sheets cover only the old model, and new-model collections are hidden from it entirely. **Will changing UPDATE to MERGE fix the error?** No, and it can damage your data. `MERGE` creates a new collection when it finds no match, so you end up with a duplicate of a collection that already exists on your storefront. **Can I use Altera for collections and keep Matrixify for everything else?** Yes. Altera uses the same Matrixify-compatible spreadsheet format. You can use Matrixify for data types it supports and Altera for the new collections, [market translations](/matrixify-translations/), [metafield definitions](/matrixify-metafield-definitions/), [metaobject definitions](/matrixify-metaobject-definitions/), [inventory transfers](/matrixify-inventory-transfers/), [linked product options](/matrixify-linked-product-options/), [sales channel publishing](/matrixify-sales-channel-publishing/), [variant sales channel publishing](/matrixify-variant-sales-channel-publishing/), and other data types Matrixify doesn't cover. --- See our full [Altera vs. Matrixify comparison](/altera-vs-matrixify/) for a breakdown of all the differences between the two tools, or check the [FAQ](/shopify-import-export-matrixify-faq/) for more common questions. {{< comparison-cta text="Update every collection in your store with Altera." >}}