title | Yes Type: string | Product name Can be found on top of product’s page |
body_html | Yes Type: string | Product description |
status | No Type: string|SalesLayer Status | Product status: - V → Visible, D → Draft, I → Invisible.
- In Shopify can be found in the Product status window within a product.
- In case you want to handle different statuses for different stores in Shopify, you can add fields to your catalog to manage them separately (creating a “Status 2” field, for example).
|
sku | Yes (for internal Sales-Layer control) Type: string | Product reference In Shopify If no variants exist, the SKU is shown in the Inventory window within a product |
price | No Type: decimal | Price - Shopify allows up to two decimals in the price field. We recommend that you adopt this restriction in the mapped fields. If you need to place more than two decimal places, you can use the CONVERT_NUM() formula to convert the format.
- In Shopify If no variants exist the price is in Pricing window within the product
|
published_scope | No Type: list of values | Product availability - web
- global (default). Point of Sale
|
No | Product availability - all: all sales channel
- third-party: to ignore modifying any information about sales channels from the connector (for clients which syncronize this data from other application).
- Online Store
- global (default). Point of Sale
- social: Facebook & Instagram, Google & YouTube
- button: Buy Button
- combination of shorcuts separated with “|” (web | global)
- Online Store:2025-02-15
- persist: the connector will publish the item only in the sales channels Online Store and Point of Sale. It will not manage any other sales channel.
Example: - web|global|persist
|
vendor | No Type: string | Product organization (Vendor) - Should be created on purpose, could be one of the points of sale
- In Shopify can be found in the Product organization window within a product
|
handle | No Type: string | URL handle The last part of a specific product URL construction, can be found in Search Engine listing within a product |
product_type | Type: string | Product organization, attribtue set of the product - In Shopify can be found in the Product organization window within a product
|
template_suffix | No Type: text | Theme template Theme template Map with one of existing values, the themes must be either created or bought from Online store > Themes |
tags | No Type: string | Tags - In Shopify can be found in the Product organization window within a product
|
sort_order | No Type: string | - Configurable attribute that can include a formula to define the order of variant attributes, such as price or size.
- The field names must match those listed in Output Data > Products > Name in Shopify.
- In Shopify, this will appear within the product’s Variants or Options window.
- Examples:
- PRINT("price:desc")
- PRINT("price:asc")
- PRINT("size:custom|S|M|L|X")
- Note: in the formula PRINT("size:custom|S|M|L|X"), keep in mind that if you do not provide all variant options, the system will follow the custom order only for the specified options. Any options not included will retain their original order.
|
metafields_global_title_tag | No Type: string | Page title, SEO tab Default metafield title to map - In Shopify can be found in Search Engine Listing window within a product under the title field.
Notes: - From v1.10.1 the recommended way to synchronize this field will be mapping out the seo_title field.
- metafields_global_title_tag and seo_title should not be mapped out both together.
|
metafields_global_description_tag | No Type: string | Default metafield description to map - In Shopify can be found in Search Engine Listing window within a product under description field
Notes: - From v1.10.1 the recommended way to synchronize this field will be mapping out the seo_description field.
- metafields_global_description_tag and seo_description should not be mapped out both together.
|
seo_title | No Type: string | SEO title Notes: - Starting from v1.10.1, seo_title is the recommended field to map this data in Shopify.
- Important: Do not map both metafields_global_title_tag and seo_title together.
|
seo_description | No Type: string | SEO meta description Notes: - Starting from v1.10.1, seo_description is the recommended field to map this data in Shopify.
- Important: Do not map both metafields_global_description_tag and seo_description together.
|
inventory_quantity | No Type: int | Stock, depending on the location - If no variants exist it can be found in the Inventory window within the product
|
No Type: int | Stock, depending on the location - If no variants exist it can be found in the Inventory window within the product
|
inventory_policy | No Type: string | inventory_policy defines whether customers can place orders when the item is out of stock. This field should be mapped to a text-type field with the values: - deny: when customers can't place orders for products that are out of Stock.
- or continue: when customers can place orders for products that are in Stock.
If a product has no variants (i.e., it’s a single product), the policy is shown in the Inventory section of the Product. |
cost_per_item | No Type: float | Cost per Item field, near Price, indicating the cost of fabrication or similar - In Shopify if no variants exist can be found in the Pricing window within a product
|
country_code_of_origin | No Type: string | Configurable attribute, region or country of origin for customs control. List of possible values at https://shopify.dev/api/storefront/reference/common-objects/countrycode |
province_code_of_origin | No Type: string | The ISO 3166-2 alpha-2 province code of where the item originated from. Link: ISO 3166-2 (example: ES-V, FR-IDF, etc.) |
harmonized_system_code | No Type: string | The harmonized system code of the item. |
countryHarmonizedSystemCodes | No Type: List | Same behaviour than fields: country_code_of_origin and harmonized_system_code |
requires_shipping | No Type: boolean | True => This is a physical product, requires shipping field. Otherwise, False. In Shopify if no variants exist can be found in Shipping window within a product |
tracked | No Type: boolean / string | It defines whether an item's inventory should be tracked or not. This field should be matched with a text-type field with the values: - ‘yes’: allows connector setting value to stock quantity.
- ‘no’ | empty | null: does not allows connector setting value to stock quantity.
|
weight_unit | No Type: string | Weight unit dropdown - Unit of measurement (g, kg, pcs,...)
- g => GRAMS
- kg => KILOGRAMS
lb => POUNDS - oz => OUNCES
- In Shopify if no variants exist can be found in the Shipping window within a Product along the weight field
*Does not work if the grams field is active |
weight* | No Type: decimal | Weight, appears when the previous box is checked - In Shopify if no variants exist can be found in the Shipping window within a Product
*Does not work if the grams field is active |
images | No Type: array (string) | Product image An array is sent with the status, ID and the image link |
product_alt | No Type: string | This field is used to assign a descriptive alt attribute to each product image. It should be mapped with a field from your catalog containing the desired description. - If no value is provided, the connector will automatically generate the alt text using the product’s title.
- In Shopify, this text is visible when viewing the product image in the media gallery and is used to improve SEO and accessibility.
This field can be configured: - Using a text field with comma-separated descriptions, matching the order of the images.
- Using a table-type field, where each row corresponds to the image in the same position (i.e., the first row applies to the first image, the second to the second, and so on).
|
media_video | No Type: string | This field supports sending a video or 3D images from your SL’s file library. |
media_video_alt | No Type: string | This field can be configured: - Using a text field with comma-separated descriptions, matching the order of the images.
- Using a table-type field, where each row corresponds to the image in the same position (i.e., the first row applies to the first image, the second to the second, and so on).
|
media_external | No Type: string | It’s possible to send a URL of an external video through the connector, such as adding a video you have on YouTube to a specific product. To do this, map a field that contains the URLs of the video or videos. |
media_external_alt | No Type: string | This field can be configured: - If no value is provided, the connector will generate a value.
- By text field using comma-delimited descriptions, in the same order as the videos.
- By table type field in a column where the first row is linked to the first video, the second to the second, and so on.
|
media_order | No Type: string | Default behavior in 1.8,x 1.9.x If the media_order field is not mapped, the connector will sort the media entities using the following default order: - Media Images
- Model 3D
- Media Video
- External Video
|
Default behaviour: 1.10.x If the media_order field is not mapped, the connector will sort the media entities using the following default order: - Elements inside the media_video connector’s field.
- Elements inside the images connector’s field.
- Elements inside the media_external connector’s field.
*Remember that the order of elements within a specific field can be controlled by placing one element before another. |
taxable | No Type: string| boolean | true|yes|sí => Indicates whether a tax is applied to a product (the VAT of this product). no => Does not indicate. |
compare_at_price | No Type: float | Corresponds to the previous price of the item. Example: 100€ - 75€ - 0 → to remove the compare_at_price.
- number bigger than 0 → old price. In the example above 100€.
Compare at price value is higher than a regular price - In Shopify if no variants exist can be found in the Pricing window within a product
|
markets | No Type: table | It enables the markets for the product. It requires a table with two columns: Then, map the field. |
presentment_prices | No Type: table | - Currency and market prices for the product.
- This field can be defined in the Variants tab.
- Columns:
- currency_code
- amount
- optionall
- Price, it’s mandatory except if you don’t want to modify the price.
- Shopify supports up to two decimal places in the price field, so we recommend adhering to this constraint in the fields to be mapped.
- compare_at_price
- optional
- Previous price to the current price. This should be greater than the current price in Amount.
- market
- optional
- The market being referred to, which has been previously created in Shopify and to which the product belongs. If it's not filled in, it will apply to all the currencies of the different markets that don't have a currency assigned.
- Then, map the field presentment_prices.
|
| Type: string | In version 1.9, the field inventory_management is automatically converted to field tracked but we do recommend using tracked. Next versions will not support inventory_management. Track quantity checkbox, mapped with the Inv Management field made specifically. Values: - ‘shopify’: Synchronizes values from Sales-Layer mapped field inventory_quantity to Shopify.
- empty|null: Does not synchronize values from Sales-Layer mapped field inventory_quantity to Shopify although inventory_quantity has a valid value.
|
fulfillment_service | No Type: string | In version v1.8: Location info, previously defined in Shopify. Defines the fulfillment service associated with the item. It should be mapped with a text-type field with the words: In version 1.9, the connector does not implement fullfilment_service. |
grams * | No Type: number | In version 1.9 is automatically converted to field weight, weight_unit. It is recommended to use weight_unit and set weight instead. (Does not work if fields weight, weight_unit are enabled) Weight (if it’s a physical product checkbox is true) - In Shopify can be found in variant’s shipping window
|