Collections

A Collection groups products so shoppers can find them faster-think “Running Shoes” or “Summer Sale.”
DataEase lets you:

Create or rename hundreds of collections in one upload.
Add or remove products, rules, sources, and conditions in bulk.
Change sort order, images, and SEO text quickly.

Shopify’s new collections model (Admin API 2026-07). Shopify no longer splits collections into “smart” and “custom”. A collection is built from one or more sources; each source has include/exclude conditions and/or manually picked products, variants, or sub-collections. DataEase supports this model through the Sources & conditions columns (details below). Files with the classic rule and product columns keep working for collections that the classic columns can still describe.

Shopify collection guide.

Export
Import
Field reference
Filters
Sources & conditions

2. Export

Pick CSV or Excel.
Choose Collection as the entity.
Select the fields you need-title, sortOrder, ruleColumn, etc. To export collections built with the new model, enable the Sources & conditions column group.
Optional: tick Matrixify-style headers and values to write the source and condition columns with Matrixify headers and values (for example Source: Type, Include, any condition) instead of API values (sourceType, INCLUDE, ANY).
Run the task and download your file.

Collections the classic columns can’t describe. If a collection uses the new model in a way the classic rule columns can’t express (for example several sources, exclusions, variant sources, or conditions mixed with manual picks), its ruleColumn/ruleRelation/ruleCondition/appliedDisjunctively cells stay empty and the export log shows a warning asking you to enable the Sources & conditions columns. With only the classic columns enabled, such a collection is exported as its main row only.

Step-by-step: Export guide

3. Import

Supported commands in command: CREATE, UPDATE, REPLACE, DELETE, IGNORE
Line-item commands (rules or products): CREATE, MERGE, UPDATE, DELETE, IGNORE

For manual collections use product lines (productId).
For smart collections use rule lines (ruleColumn / ruleCondition…).
For collections that use the new model (several sources, exclusions, variant sources, sub-collections) use the Sources & conditions columns.

The mode is decided per collection: if any row of a collection fills a Sources & conditions column (for example sourceType or conditionField), the whole collection is imported in the new mode and its productId / productHandle / productPosition rows only set the sort position — they don’t add or remove products. Otherwise the classic behaviour applies: product lines add (CREATE, MERGE), move (UPDATE), or remove (DELETE) manually picked products.

Classic product lines on a smart collection. A classic file with product lines (productId + itemCommand CREATE) for an existing smart collection now adds those products as manual picks, so the collection becomes a mix of conditions and picked products. After that, classic rule imports for that collection (including saved scheduled imports) fail with “The collection uses the new collections model (MIXED_SELECTIONS_AND_CONDITIONS)”. Use the Sources & conditions columns for such collections.

Tip: Only collections with sortOrder = MANUAL let you set productPosition.

Download the sample file: Collection-import-sample.xlsx
Fill required fields: title and handle for CREATE; include id or handle for UPDATE/DELETE.
Map columns in DataEase, upload, and start the import.

Full steps: Import guide

4. Field reference

Basic

id — Collection ID. Needed for UPDATE, REPLACE, or DELETE.
command — Action for the collection row: CREATE, UPDATE, REPLACE, DELETE, IGNORE.
title — Name shown to shoppers.
handle — URL-friendly string. Must be unique.
descriptionHtml — Rich-text description with HTML.
templateSuffix — Alternate Liquid template (without .liquid).
sortOrder — Default product order: ALPHA_ASC, ALPHA_DESC, CREATED, CREATED_DESC, MANUAL, MOST_RELEVANT, PRICE_ASC, PRICE_DESC. Since Admin API 2026-07, Shopify returns collections sorted by best selling as MOST_RELEVANT, so exports write MOST_RELEVANT instead of BEST_SELLING. BEST_SELLING is no longer supported by DataEase — use MOST_RELEVANT in your files.
updatedAt — Last-modified date (ISO 8601). Export only.

SEO

seoTitle — Custom page-title tag.
seoDescription — Custom meta-description.

Image

imageUrl — URL of the featured image.
imageAltText — Alt text for the image.
imageHeight — Image height (px). Export only.
imageWidth — Image width (px). Export only.

Line-item (rule or product)

itemCommand — CREATE, MERGE, UPDATE, DELETE, or IGNORE for this line.

Smart-collection rule fields

These classic columns are filled on export only when the collection can still be described as one set of rules; otherwise they stay empty (see Export).

ruleColumn — Product attribute for the rule (e.g., TITLE, TAG, VENDOR).
ruleCondition — Value the rule compares to, like Shoes.
ruleConditionObjectId — Extra info for some rule types (e.g., category ID).
ruleRelation — Operator: EQUALS, CONTAINS, NOT_EQUALS, etc.
appliedDisjunctively — true = match ANY rule; false = match ALL rules.

Manual-collection product fields

productId — ID of a product to include.
productPosition — Position number (works only if sortOrder = MANUAL).
productTitle — Product title. Export only.
productHandle — Product handle. Export only.

Publication

publicationScope — Sales channels where the collection is published.

Metafields

metafields — Extra app fields. See Metafields guide.

5. Filters

CollectionType — Smart (with conditions) or Custom (manual only). Shopify’s new model has no collection type, so DataEase works it out from the collection’s sources: smart = at least one source with an include condition; custom = everything else (only manually picked products, sub-collections, or no sources). Because this filter is applied after Shopify returns the collections, the collection count in the export form may show ≤ N (at most N).
Handle — Export collections where handle contains the text you enter.
Id — Export a single collection by id.
ProductId — Export collections that include a specific productId.
ProductPublicationStatus — Filter by product publish status inside the collection.
PublishableStatus — Choose ready, scheduled, or unpublished collections.
PublishedAt — Date range when the collection became visible.
PublishedStatus — true for published, false for hidden.
Title — Export collections whose title contains your text.
UpdatedAt — Filter by last-updated date range.

Sources & conditions

Enable the Sources & conditions column group to export and import collections in Shopify’s new collections model. One row = one condition or one manually picked item of one source; the source columns repeat on every row of that source. The collection’s base columns (handle, title, …) repeat as usual.

Values are accepted in API style (INCLUDE, ALL, TAGGED_WITH, COMPARE_AT_PRICE) or Matrixify style (Include, all conditions, Includes, Compare at price), case-insensitive. Files exported from Matrixify’s Collections sheet are recognised by their headers (Source: ID, Condition: Field, …).

sourceId — ID of the source. Use the exported ID to change an existing source, or your own label (for example s1) to group the rows of a new source.
sourceCommand — MERGE (default) adds the rows to the source; REPLACE clears the source and fills it from the file; DELETE removes the source.
sourceType — PRODUCTS, VARIANTS, COLLECTIONS (sub-collections), or APP <app id> | PRODUCTS / APP <app id> | VARIANTS for a source shared by another app (read-only on import). UNKNOWN is export-only.
sourceTitle — Title of the source. If it’s empty when a source is created, DataEase generates one from the collection title.
sourceDescription — Description of the source.
inclusionType — INCLUDE (default) or EXCLUDE.
inclusionMatch — ALL or ANY: whether products must match all or any of the source’s include (or exclude) conditions. A new source defaults to ALL.
conditionCommand — MERGE (default) adds the condition if it doesn’t exist yet; DELETE removes it. To change a condition’s value, delete the old condition and add the new one, or use sourceCommand = REPLACE.
conditionField — TAG, TITLE, TYPE, VENDOR, STATUS, CATEGORY, CATEGORY_WITH_SUBCATEGORIES, PRICE, COMPARE_AT_PRICE, INVENTORY_STOCK, WEIGHT, VARIANT_TITLE, COLLECTION (exclude only), MANUAL_SELECTION, METAFIELD: namespace.key, VARIANT_METAFIELD: namespace.key. UNKNOWN is export-only (a condition DataEase can’t write; such rows are skipped on import with a warning).
conditionRelation — Operator, for example TAGGED_WITH, EQUALS, CONTAINS, DOES_NOT_CONTAIN, GREATER_THAN, IS_SET, INCLUDES. Leave empty for MANUAL_SELECTION and COLLECTION.
conditionValue — Value(s), comma-separated (\, for a literal comma). Prices accept an optional currency (12.50 EUR, default = shop currency); weights an optional unit (1.5 kg, default = shop unit). For MANUAL_SELECTION use one product handle or ID per row, product-handle | Variant Title for a variant, or a collection handle in a COLLECTIONS source. Export writes handles so files can move between stores.
conditionMatch — ANY (default) or ALL for a condition with several values; OR / AND are accepted on import.

In the new mode, productId / productHandle / productPosition rows only set the sort position (for sortOrder = MANUAL). Shopify’s limits for the new model are checked before the import calls Shopify: up to 10 sources per collection, 60 conditions per source (each value counts), 5 excluded collections, 10 sub-collections, and 1,000 manual exclusions.

Example — tag condition plus a manual pick and a manual exclusion in one source:

handle,title,sourceId,sourceType,sourceTitle,inclusionType,inclusionMatch,conditionField,conditionRelation,conditionValue,conditionMatch
vegan,Vegan picks,s1,PRODUCTS,Vegan tag,INCLUDE,ANY,TAG,TAGGED_WITH,"vegan,plant-based",ANY
vegan,Vegan picks,s1,PRODUCTS,Vegan tag,INCLUDE,,MANUAL_SELECTION,,oat-milk,
vegan,Vegan picks,s1,PRODUCTS,Vegan tag,EXCLUDE,,MANUAL_SELECTION,,leather-belt,

Re-importing the same file doesn’t create duplicate sources or conditions.

Need help? Our support team answers within 24 hours.

Additional fields

More columns DataEase supports for this entity:

productsCount — Number of products in the collection.