Mapping Shopify fields

A guide to mapping your Plytix attributes with Shopify fields

In this article, we will show you how to map Plytix attributes with Shopify fields to send data with our Shopify connector. 

 

Product fields

Variant fields

Metafields

 


Product fields

Shopify Field Description Mapping Suggestions
Handle

Required field for mapping with Plytix and unique identifier in Shopify. 

Example: "rover-14-backpack"

Create a dedicated field for your Shopify handles using a short text attribute.

If you have multiple stores, you can create a handle for each store. 

If a handle for a product is empty in Plytix, it will create a new product in Shopify and sync the new handle value automatically back to the PIM.

Handles are created automatically by Shopify from the product's "title" field.

 

Title

Required field

Example: "Rover 14 Backpack"

 

Body HTML

A product description that supports HTML

Example: "A lightweight 14L backpack perfect for the back country."

Match with an HTML or plain text attribute
Product Type

A categorization for the product used for filtering and searching products.

Example: "Sport Backpack"

Match with your categories or a multiselect or dropdown attribute type 
Status

This tells Shopify if your product is ready to sell, not ready yet or is not available to your customers anymore. 

Accepted values: 

active

draft

archived

Example: "active"

Match with a dropdown that has the accepted values. 

You can also use a Computed Attribute to transform your Plytix "Status" attribute into an acceptable format (without the archived option):

DLOOKUP($STATUS, {"Draft": "draft","Completed": "active"},"draft")

Tags

A string of comma-separated tags that are used for filtering and search.

A product can have up to 250 tags.

Each tag can have up to 255 characters.

Example: "14L,Board Bag,Hydration"

Match with your categories or a multiselect attribute type. 

Image Gallery

Images associated with the product

Match with a media attribute type
Collections

This will add products to a manual collection in Shopify.

Example: "Best Sellers"

Match with a plain text, multiselect, or dropdown attribute type
Vendor

The name of the product's vendor

Example: "Nitro"

Match with a plain text or dropdown attribute type
Template Suffix The suffix of the Liquid template used for the product page. If this property is specified, then the product page uses a template called "product.suffix.liquid", where "suffix" is the value of this property. If this property is "" or null, then the product page uses the default template "product.liquid". (default: null)

Match with a plain text or dropdown attribute type

You can also create a Computed Attribute with a string value defined

Published at

The date and time (ISO 8601 format) when the product was published.

Can be set to null to unpublish the product from the Online Store channel.

Example: "2007-12-31T19:00:00-05:00"

Match with a date attribute type.

Leave the date blank to send a null value.

Published scope

Whether the product is published to the Point of Sale channel.

Accepted values:

web

global

web: The product is published to the Online Store channel but not published to the Point of Sale channel.

global: The product is published to both the Online Store channel and the Point of Sale channel.

Example: "web"

Match with a dropdown attribute that uses the accepted values.
Option Name (1-3)

The custom product property names like Size, Color, and Material. You can add up to 3 options.

Example: "Size"

Match with a plain text or dropdown attribute. 

You can also create a Computed Attribute with a string value defined.

Option Value (1-3)

The custom product property values that match the names like Size, Color, and Material. These values can be up to 255 characters each.

Example: "M/L"

Match with a plain text, multiselect, or dropdown attribute type

Handle and Title

As mentioned in the table, this is a required field from Shopify to identify products, and how Plytix will identify products to create or update. This field is mandatory to map in order to process your channel. 

The handle tells us what to do with products based on the value provided. 

  1. Update an existing product: this requires that the handle is a valid handle
  2. Create a new product: if the value for the handle is blank, then this tells Shopify that this is a new product and it will be created in your store. The handle will be automatically generated from the title provided. Then the new handle value will be automatically synced back to Plytix.

Learn how to import information from Shopify to Plytix to get your existing handle values.

ℹ️ When creating a new product the handle value needs to be blank, and the title value is required 

⚠️ If a handle is not valid, the product will not be updated and you will see an error in the process log

 

Option name / Option value


Shopify allows you to define up to three fields to create variations using "Options". These are required fields for populating variants.

In order to identify which fields will be used to create variations these special attributes have to be used:

  • Option name: Match with a PIM attribute which stores the name of this option. This value is shown over the available options in the Shopify store. This must be defined in the parent product
  • Option value:  Match with a PIM attribute which stores the value for this variation. This must be defined in the variation product.


⚠️ If the Option name and option value are not mapped: then no variations are created in the store

Collections

Plytix will add products to manual collections using this attribute matching. Based on the values provided, Plytix will:

  1. Add a product to an existing collection if the value provided exists in Shopify
  2. Add a product to a new collection created by Plytix if the value provided does not exist in Shopify
  3. Remove a product from an existing collection if the value for that collection is not provided for a product


Variant Fields

Shopify Field Description Mapping Suggestions
Barcode

The barcode, UPC, or ISBN number for the product.

Example: "1234_pink"

Match with a plain text or the Plytix "GTIN" attribute
Compare at price

The original price of the item before an adjustment or a sale.

Example: "299.00"

Match with an integer or decimal attribute type. 

You can also create a Computed Attribute for special price configurations.

Fulfillment Service

The fulfillment service associated with the product variant.

Accepted values:

manual

or the handle of a fulfillment service.

Example:"manual"

Match with a dropdown attribute with the accepted values
Grams

The weight of the product variant in grams.

Example: 567

Match with an integer or decimal attribute type. 

You can also create a Computed Attribute to convert another weight unit into grams.

Inventory item ID

The unique identifier for the inventory item, which is used in the Inventory API to query for inventory information.

Example: 342916

Match with a plain text attribute type.
Inventory Management

The fulfillment service that tracks the number of items in stock for the product variant.

Accepted values:

shopify

null

enabled

or the handle of a fulfillment service


shopify: You are tracking inventory yourself using the admin.

null: You aren't tracking inventory on the variant.

enabled: This must be the same fulfillment service referenced by the fulfillment_service property.

Example: null

Match with a dropdown attribute that has the accepted values.
Inventory Policy

Whether customers are allowed to place an order for the product variant when it's out of stock.

Accepted values:

deny

continue


deny: Customers are not allowed to place orders for the product variant if it's out of stock. (default)


continue: Customers are allowed to place orders for the product variant if it's out of stock.

Example: "continue"

Match with a dropdown attribute that has the accepted values.
Price

The price of the product variant

Example: "199.00"

Match with an integer or decimal attribute type. 

You can also create a Computed Attribute for special price configurations.

SKU

A unique identifier for the product variant in the shop.

Required in order to connect to a FulfillmentService.

Example: "NITROROVER14"

Match with the SKU or another unique identifier in a plain text attribute
Taxable

Whether a tax is charged when the product variant is sold.

Accepted values: 

true

false

Example:"true"

Match with a dropdown or boolean attribute type
Tax Code

This field applies is only applicable to  stores that have the Avalara AvaTax app installed. This specifies the Avalara tax code for the product variant

Example: "DA040000"

Match with a plain text attribute type
Weight

The weight of the product variant in the unit system specified with weight_unit.

Example: 100

Match with an integer or decimal attribute type.
Weight Unit

The unit of measurement that applies to the product variant's weight. If you don't specify a value for weight_unit, then the shop's default unit of measurement is applied.

Accepted values: 

g

kg

oz

lb

Example: oz

Match with a dropdown attribute that has the accepted values.

Metafields

Metafields are Shopify's answer to custom attributes. They can be applied to different parts of your Shopify store including products, customers, orders, and other objects. The metafields you can create in Plytix are product metafields

You can create an unlimited amount of metafields in Plytix. Metafields not created in Plytix cannot be mapped. 

Create a new metafield: 

  1. Go to the "Mapping" section of your Shopify channel
  2. Click on "Create metafield"
  3. Choose the value type (integer, string, or JSON string)

    create-metafield-plytix
  4. Add a unique key
  5. Click "Create metafield"
  6. Now your metafield will be available for mapping

ℹ️  The namespace cannot be changed. 

 


What's next

 

If you have any questions just click on the chat box in the bottom-right corner and we'll be happy to answer them...

 

and please let us know 👇