Shopify has unified all Collection types into a single entity. A Collection gets its Products from one or more Sources, and each Source holds Conditions that decide which Products are included or excluded. One Collection can mix automated rules and manually selected Products.
This sheet replaces the Smart Collections and Custom Collections sheets, which are now deprecated. Those sheets can each represent only one kind of Collection and cannot read or write a Collection that has more than one Source.
Fields marked as “Export Only” cannot be imported/set in Shopify but can be exported with Matrixify export.
Excel Sheet Name
Collections
When importing a file, to tell the app that you are importing Collections, you can set the sheet/tab name to “Collection” or “Collections”.
Even if the sheet/tab name is not set correctly, you will be able to manually change and set the entity you are importing after uploading file in the app.
Need a quick start?
Columns Available for Export & Import
Basic Columns
| Column | Description / Example Value |
|---|---|
| ID | ID is an automatically generated number by Shopify to identify the item.
It is filled in by an Export. Allowed ValuesNumber Example102473039939 |
| Handle | This is what your store visitors will see in the Collection URL as unique collections Handle.
You can leave it empty when creating new Collections – in that case, the app will generate it for you from Title. When updating the Handle the app will by default also create a Redirect from old Handle to the new one. You can turn this off in the Import options with importing a file. In Shopify, all Handles have a limitation of 255 characters, so any Handle longer than that will get truncated to 255 characters. Examplecool-looking-tshirts |
| Command | When importing a Collection, tell the app what to do with it:
If no Command is specified, then the app will assume the Allowed ValuesNEW MERGE UPDATE REPLACE DELETE IGNORE ExampleMERGE |
| Title | Title of the Collection.
Allowed ValuesText ExampleCool Looking T-shirts |
| Body HTML | This is a long description of the Collection.
You can write here just plain text or format that text using HTML code. Allowed ValuesText, HTML ExampleThose all are nice T-shirts, and this is their <b>description</b>. |
| Sort Order | Set how the Products will be sorted inside that Collection.
To set the Product order yourself with Linked Product columns, this must be set to “ Allowed ValuesAlphabet Alphabet Descending Best Selling Created Created Descending Manual Most Relevant Price Price Descending ExampleManual |
| Template Suffix | Template Suffix allows you to specify which Template from your Theme to use for the specific Collection.
If the new Template file name is “collection.women.liquid”, then – to activate this Template for this Collection, write “women” as the Template Suffix. Allowed ValuesText Examplewomen |
| Updated At
Export Only |
It will be automatically updated, whenever you change the Collection data.
Example2026-06-02 02:53:44 +0300 |
| Image Src | Link to the image.
This link must be publicly available. Once an image is imported, it doesn’t need to be hosted anymore with this link, because Shopify will download this image and store on their own servers. Allowed ValuesURL Examplehttps://images.com/image.jpg |
| Image Width
Export Only |
The width of the image, in pixels.
Example1062 |
| Image Height
Export Only |
The height of the image, in pixels.
Example527 |
| Image Alt Text | Alt Text for the Collections image. Great for SEO, because then search engines will know what is inside the image.
Allowed ValuesText ExampleSome descriptive name of the image |
| Products Count
Export Only |
Number of Products in the Collection, as calculated by Shopify from all of the Collection Sources.
Example5 |
| Row #
Export Only |
Will have row number from 1 till the end for each row. So that if you change the sorting in your exported file to easier update your data, you can sort it back by “Row #” and return it to the original sorting. |
| Top Row
Export Only |
It will have value “TRUE” for each “top row” of the item. That can help you filter in Excel to get only the base rows, in case you need to get rid of repeated rows for each item. |
Sales Channels
Each Collection can be published to the Sales Channels that your store has installed. These columns tell you where the Collection is published, and let you publish or unpublish it.
These are dynamic columns – there is one pair of columns for each Sales Channel, and you write the name of the Sales Channel after the colon. For example, Published: Online Store and Published At: Online Store.
The Sales Channels available to you depend on which ones are installed in your store. Some of the possible ones are “Online Store”, “Point of Sale”, “Shop”, “Facebook & Instagram”, “Google & YouTube”, “Snapchat Ads” and “TikTok”. Do the Export first to see the exact column names for your store.
| Column | Description / Example Value |
|---|---|
| Published: … | Tells whether this Collection is published to the given Sales Channel. If you leave this cell empty, or set it to FALSE, then it will unpublish that Collection from that Sales Channel and clear its “Published At” date. Allowed ValuesTRUE FALSE ExampleTRUE |
| Published At: … | The date and time when the Collection becomes available on the given Sales Channel. You can set it in the past, and on some Sales Channels you can set it in the future to schedule the publication. Can also be left empty when publishing a collection, which means it will be marked as published at the time of the Import. Scheduled publishingIn Shopify, scheduled publications are only supported by a few Sales Channels such as “Online Store” and “Google & YouTube”. For those Sales Channels, you can set this field to a future date to schedule automatic future publication. If importing future publish date for a Sales Channel that does not support it, the app will return a warning, and the Collection will not be published at all to ensure that it is not published immediately by mistake – so use an empty “Published At” for those, or a date in the past. Allowed ValuesDate & Time Example2026-12-25 10:00:00 +0200 |
Sources & Conditions
Each Collection gets its Products from one or more Sources. A Source has a Type, and it holds Conditions which are grouped into an “Include” and “Exclude” conditions.
A Collection can have up to 10 Sources.
The best way to understand how to fill those in, is to build one Collection through the Shopify Admin manually, and then do the Export. In the exported spreadsheet file, you will see the overall structure and will be able to repeat that same principle when creating many Collections to import in bulk.
When you update an existing Collection, the app identifies each of its Sources by:
-
- By the numeric Source: ID, as it comes from an Export. This is the reliable way to point at one specific Source.
- If there is no numeric Source: ID, then by the Source: Title and Source: Description. So you can update a Source by its name, without knowing its ID – which is what you need when moving Collections between stores.
- If you write your own text in the Source: ID – like “s1” or “my-source” – then that text is used only to group the rows within your file. It is not stored in Shopify, so it cannot point at an existing Source.
- If no other identification is specified, the app will update the first matching source with the same Source: Type before creating a new Source.
| Column | Description / Example Value |
|---|---|
| Source: ID | The ID of the Source, filled in by an Export. When creating new Sources, you can leave this empty, or you can write any number of your own to group the rows of multiple conditions into specific set of Sources. Allowed ValuesNumber Example22918103107 |
| Source: Command | Tell the app, what to do with this Source:
If no Allowed ValuesMERGE DELETE REPLACE ExampleMERGE |
| Source: Type | Defines what the Source draws its Products from:
An App Source is identified by the app ID in this column together with the Source: Title, so it is not mandatory to fill in the Source: ID for it. The Source: Type of an existing Source cannot be changed. Delete the Source and create a new one to change it. Allowed ValuesProducts Variants Collections App app-id | Type ExampleApp 2315872 | Products |
| Source: Title | Your own name for the Source, so that you can tell your Sources apart. It is one of the columns used to group the rows into Sources.
Shopify stores a maximum of 255 characters in this field. If you write a longer value, the app will cut it to 255 characters and give you a warning about it. Allowed ValuesText ExampleProducts on sale |
| Source: Description | Your own description for the Source. It is one of the columns used to group the rows into Sources.
Allowed ValuesText ExampleAll the E90 body panels |
| Inclusion: Type | Tells, whether the Conditions on this row add Products to the Source, or take them away:
Allowed ValuesInclude Exclude ExampleInclude |
| Inclusion: Match | Here you define how the Conditions of the Exclude or Include inclusion are joined together:
Leave this empty for rows where you manually select Products, Variants or Collections by using Condition: Field with value Allowed Valuesall conditions any condition Exampleall conditions |
| Condition: Command | Tell the app, what to do with Condition in this row:
If no Allowed ValuesMERGE DELETE ExampleMERGE |
| Condition: Field | The attribute field that the Condition is checking to validate Products for the Collection.
Use Allowed ValuesTag Title Type Vendor Status Category Category with Subcategories Price Compare at price Inventory stock Weight Variant title Collection Manual Selection Metafield: namespace.key ExampleTitle |
| Condition: Relation | Here you define what relation should be applied for that field and the value.
Leave this empty when the “Condition: Field” is “Manual Selection”. Allowed ValuesWhich Relations are available depends on the Condition: Field and on the Inclusion: Type (note that this list might change and not be 100% up to date, check Shopify Admin for exact supported relation values):
ExampleEquals |
| Condition: Value | Here you write the condition value you want to set.
To write several values in one Condition, separate them with a comma. If you need a comma as part of the value itself, escape it with a backslash as “\,”. Allowed ValuesThe value and format of this column’s value depend on the Condition: Field for this condition.
ExampleE90 |
| Condition: Match | Define how multiple values within one Condition are joined together:
For example, if you set the “Condition: Field” to “Tag” and the “Condition: Value” to “sale,clearance”, then:
Allowed ValuesAND OR ExampleOR |
Linked Products
These columns set the order of the Products inside the Collection. In Import they are used only when the Sort Order is set to Manual.
The Products you sort must already be in the Collection. To add a Product to the Collection, add a “Manual Selection” Condition for it.
| Column | Description / Example Value |
|---|---|
| Sort: Position | The position of the Product in that Collection.
The positions are used as a sort key, not as absolute slots. Matrixify app sorts the Products by the numbers you give and then renumbers them from 1 to the count of Products. So you can use gaps such as 10, 20, 30, and you can use a decimal such as 1.5 to place a Product between two others without renumbering everything. If several Products have the same number, they keep the order in which they appear in the file. When updating an existing Collection, an empty Allowed ValuesNumber Example5 |
| Sort: Product ID | Shopify Product ID. It is used to identify the product whose position you want to set.
Allowed ValuesNumber Example6760502034499 |
| Sort: Product Handle | The Handle of the Product. It functions as an alternative way to identify the Product if it cannot be found by the Product ID. Especially useful when sorting Products among different shops where you don’t know the ID of the Product.
Allowed ValuesText Examplebmw-wheel-style-18 |
Metafields
Read the description on the Metafields page.
Collection Metafields can be exported and imported as “Metafield: namespace.key” columns on this sheet, or separately through the Metafields sheet with the “Owner” of “Collection”.
SEO Fields
SEO fields are actually Metafields with the following names:
- SEO Title Metafield name is “Metafield: title_tag”
- SEO Description Metafield name is “Metafield: description_tag”
Export Filters
In the Matrixify app, you can apply filters to Export only specific items from your Shopify Store. When creating new export, select what you wish to export, and under that entity click on the “Filters” button.
Note: total displayed item count and estimated time won’t be affected by the filters applied.
| Filter | Description |
|---|---|
| ID | Filters Collections that have specific Shopify IDs.
Possible Conditions
Example102473039939,102473072707 |
| Handle | Allows you to export specific Collections by their Handles, separated by a comma.
Possible Conditions
Examplemy-collection-handle, other-collection-handle |
| Title | Allows you to export Collections whose Title contains specific text.
Possible Conditions
ExamplePart of Title, other title |
| Updated At | Allows exporting Collections which were last updated in the Shopify within a specific date range. “Relative date” condition allows you to export Collections that have been updated in the last full amount of time. For example – “Last 1 Days”, would export Collections from last full day, so yesterday.
Possible Conditions
|
| Published At | Allows exporting Collections that were published in Shopify within a specific date range.
Possible Conditions
|
| Products Count | With the “Products Count” filter you can export Collections that have a specific amount of Products in it based on your set condition.
Possible Conditions
Example5 |
| Metafield | Filters the Collections export by Collection Metafields. Specify Metafield by Namespace, Key and Value.
Possible Conditions for Text value
Possible Conditions for Number value
|