Skip to main content
Print

Shopify Datamap Template

The Shopify station template contains four datamaps. This page describes how they are built, what a project fills in, and what to check in a datamap that was built from the previous template.

DatamapContentNeeds version
Shopify Products, Variants, Collections V2products, variants, collections, and deleting products and collections1.22.0
Shopify Products, Variants, Collections V2 (with legacy rows)the same, plus the rows of earlier templates, deactivated (see below)1.22.0; on 1.21.19 see below
Shopify Metaobject Entries V2metaobject entries from value ranges, see Shopify Metaobject Entries1.21.20
Shopify Metaobject Entries V2 (with legacy rows)the same, plus the rows of the previous template, deactivated1.21.20

Start with the datamaps without legacy rows. Take the ones with legacy rows when you need one of those rows, or to compare with a datamap built from the previous template.

Important: the products datamaps send options and bundles with the formats of 1.22.0. On 1.21.19 and later 1.21 versions, use the products datamap with legacy rows: deactivate the rows with the formats Send Shopify product options, Send Shopify option values and Send Shopify bundle, and activate the rows noted as Alternative instead.

Node mappings

Node mappingRecordsContent
productsUpdateCreateproducts in the sales channelproduct fields, options, media, metafields, collections, sales channels, bundles; for products without variants also the simpleproduct|… rows (price, SKU, stock, …)
variantsthe variants of these productsSKU, option values, price, inventory, variant metafields, variant image
collectionsUpdateCreatestructure groupscollection fields, image, rule set, metafields, sales channels
productsDeletedeleted products (delete jobs only)PIM identifier
collectionsDeletestructure groups, deactivatedPIM identifier; see Jobs on Shopify Transmitter
Rows of the variants node mapping

Row notes and status

Every row has a note: what the row does, the value Shopify expects, the conditions, and what to look out for. Open it in the row’s settings.

Note of a datamap row

Every row has a status. In the delivered template it shows what a row is for:

StatusMeaningRows
(1) Approved, activerequiredPIM identifier, title, additionalInformation, the variant SKU, the delete rows
(2) Auto-Mapped, activerequired for products with variantsthe variants row and the option rows
(3) Draft, deactivatedoptionaleverything else: set the attribute and activate the row
(4) Disapproved, deactivated, noted as Legacy configuration or Alternativerow of an earlier templateonly in the datamaps with legacy rows, see Rows of earlier templates below
Datamap rows with their status

After the import, the statuses are yours to change as you like. They only affect an export when a job’s Mapping Status Filter is set: then only the rows with the selected statuses are exported. See Datamap Mapping Status.

Values from attributes, skipped while empty

The rows read their values per record from attributes, also for values like the status, the sales channels or the inventory policy. A product can then differ from the next, and a change made in Shopify is not undone by every export.

Optional rows are skipped while their attribute is empty. The condition refers to the row’s own source, so it follows whatever attribute you set:

Condition that skips a row while its attribute is empty

Important:

  • Keep these conditions. Without them an empty attribute is sent as an empty text, and Shopify rejects it for numbers, prices, IDs and fixed values, which fails the whole product.
  • To send one fixed value for every record, use the format Send configurable parameter value instead of an attribute.
  • Language-dependent rows have |{StoreView} in their key. Without it, the last language overwrites the others.

What a project fills in

  1. Language table: one row per Shopify language, with Language and Channel. See Languages on Shopify Transmitter.
  2. Sales channel: the channel in the node conditions and in the collections row’s loop.
  3. PIM identifier: the key of the first row (custom.pimid) must equal the transmitter setting Shopify Custom Metafeld Id.
  4. Products with variants: the SKU attribute in the variants row’s loop and in the variants row inventoryItem|sku (the same attribute). In both option rows, the attribute that lists the variant-building attributes, and the link type of the variants if your variant rows have one; linked options in the products’ option format. See Shopify Products, Variants and Options.
  5. Bundles: in the bundle format, the link type of the components or the quantity field of the reference. See Shopify Bundles.
  6. Optional rows: set the attribute and activate the row. Some rows have a second condition on another attribute that you set as well; the row note names it:
    • initial stock and gift card: the attribute with the Shopify ID (only when the product is created)
    • market prices: the compare-at amount

Important: an empty attribute in a condition counts as empty: “is empty” always holds, “is filled” never. A condition you did not set therefore never skips the row.

Rows of earlier templates

The datamaps with legacy rows hold two kinds of deactivated rows, each next to the row that replaces it:

  • Alternative: the options and bundle components from attributes per position, one row each for the options, the option values and the bundle. Use them on 1.21, see above.
  • Legacy configuration: the rows of the previous template (Shopify Products, Variants, Collections V1) that differ from the new ones. Their note says what the row does and, under Better:, why the new row is preferred.
Deactivated row of the previous template with its note

Some of the previous template’s rows do things the new rows don’t. Use them instead of the new row, never together with it:

Row of the previous templateUse it forDetails
Options from the configuration attributes (product and variants)up to 1.21: classic options from the list of variant-building attributes (from 1.22.0 the option formats do this)Products, Variants and Options
Bundle from a product reference attribute, bundle from the complex article tableup to 1.21: bundles with more than two components (from 1.22.0 the bundle format does this)Bundles
Images collected from the variantsproducts whose images are on the variants onlyMediaupload Field Plugin
Removing the collection imagecollections that should have no imageCollections
Related products (Search & Discovery)product recommendations of the Shopify app Search & DiscoveryMetafield Field Plugin
Fixed values (status ACTIVE, sales channels, inventory policy, …)one fixed value for every recordthe row note

These rows were tested with Shopify API 2026-04. Rows that only hold placeholders (e.g. country_here, insert_tax_code_here) fail until the placeholder is replaced.

Coming from the previous template

Datamaps built from the previous template keep working after an update. If your datamap uses these rows as the previous template delivered them, check them:

Previous templateEffectChange
The variants loop has Add linked products from the complex articles table to the export switched off.No variants are exported, because the variants are not in the sales channel themselves.Switch it on.
Fixed values: status ACTIVE, gift card 1, sales channels, tags your,tags,hereEvery export re-activates archived products, publishes to the same channels again, and flags every product as a gift card; the placeholder tags replace all tags.Use the new rows with attributes, or set real values.
Weight and unit price as text, compare-at price without a conditionShopify rejects text and empty values for numbers and prices: the variant or product update fails.Use the new rows.
Format numbers on the barcode and the HS code640411 becomes 640411.00, which Shopify stores as another code; leading zeros of barcodes are lost.Send them unformatted.
Initial stock only within 10 minutes of the first delivery dateIn practice no stock is ever sent.Use the new row: stock is sent while the product has no Shopify ID yet.
Image, file and price rows with |[] without a condition on the default languageEvery file and price is sent once per language.Add the condition, as in the new rows.
Handle = the title in lower caseSpaces and special characters are not valid in handles, and a new title moves the URL.Use a handle attribute, or no handle.
Market prices from the SC price table without a price typeNo prices are sent.Select the price types in the price plugin, see Markets, Sales Channels and Prices.

Important: the product’s tags row replaces all tags of the product in every export, in both templates: tags added in Shopify by hand are removed.

Was this article helpful?
How can we improve this article?
Please submit the reason for your vote so that we can improve the article.
Table of Contents