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. The import still reports that it does not exist.
The collection uses Shopify’s new collections model, and your file is a Smart Collections or Custom Collections sheet. Matrixify has deprecated both sheets, and they do not work with multi-source collections. The fix is to use a sheet that does: Matrixify’s unified Collections sheet, or Altera’s Collections data type.
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.
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 legacy Smart Collections and Custom Collections sheets cannot address it. An UPDATE import that matched last week fails today because someone edited the collection in the Shopify admin in between.
Before September 2026 there was a second cause. Matrixify had not yet updated to Shopify’s 2026-07 API version, and Shopify hides new-model collections from apps on older versions, with no error and no placeholder. Every new-model collection was invisible to Matrixify, whichever sheet you used. Matrixify has since updated. If you see this error today, the cause is the sheet.
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 the import cannot find the real collection, you get a duplicate: the original (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 sheet can’t address the collection, without touching your store.
How to fix it#
In Matrixify: export the collection again using the unified Collections sheet, make your edits there, and import with UPDATE. The legacy sheets still run for now, but Matrixify says they will be removed, so it is worth moving any saved templates or scheduled jobs to the new sheet at the same time.
In Altera: Altera has supported the new collections model since the day Shopify shipped it and sees every collection in your store, old model and new. It reads and writes the same Matrixify-compatible spreadsheet format, and it still accepts the old Smart and Custom Collections files, so the file you already prepared carries over.
- Install Altera from the Shopify App Store. There is a free plan, and your Matrixify files work as-is.
- Export the Collections data type. Altera uses a single unified Collections sheet, and the export includes every collection, with extra columns describing each collection’s sources.
- Make your edits and import with
UPDATE. The command semantics you know apply, and the lookup by ID or Handle finds the collection.
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 documents every column, and the help center has a full write-up of how Altera handles Shopify’s new collections.
Frequently asked questions#
Why does my import say the collection does not exist when it does? Your file is a Smart Collections or Custom Collections sheet, and the collection uses Shopify’s new multi-source model. Those sheets do not handle it. Use the unified Collections sheet instead.
I get the error on a Custom Collections import too. Same cause? Yes. Both legacy sheets have the same limit. Any collection using the new model needs the unified Collections sheet, 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.
I hit this error in August, before the Collections sheet existed. Was that the same thing? Close to it. Until September 2026, Matrixify had not updated to Shopify’s 2026-07 API version, so Shopify hid every new-model collection from it, whichever sheet you used. That part is fixed. Today the error comes from the legacy sheet, and the fix is the same: use the unified Collections sheet.
Does Matrixify support Shopify’s new collections?
Yes, since September 2026, through a unified Collections sheet. See Matrixify and Shopify’s new collections for what changed.
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 market translations, metafield definitions, metaobject definitions, inventory transfers, linked product options, variant sales channel publishing, multiple barcodes per variant, and other data types Matrixify doesn’t cover.
See our full Altera vs. Matrixify comparison for a breakdown of all the differences between the two tools, or check the FAQ for more common questions.
