From January 18. 2021, the Command
UPDATE for all entities is a strict update and will fail if the item is not found.
If you want to create or update an existing item, then use the
Please adjust your automated and manual import templates accordingly.
Read more about Command changes.
You can use the following “Command” column values across all entities that can be imported (Products, Collections, Customers, Discounts, Draft Orders, Orders, Pages, Blog Posts, Redirects and Files).
NEW: will try to create a new item with the provided details. If an item already exists (with the same ID or same Handle), then the result will be Failed.
MERGE: will try to find an existing item and update it with data from row. If an item cannot be found then the app will try to create a new one.
UPDATE: the app will search for an existing item and update it. If an item cannot be found then that item will fail to import.
REPLACE: at first, app will try to find an existing item and if found then the app will delete it. After that, it will create a new one only with data you have in the file.
If an existing item will not be found, then still the app will create a new one. The difference from UPDATE is that it will not keep any of columns, which were not included in the import file since the item will be deleted and re-created.
DELETE: the app will try to find and delete items. If an item cannot be found, then the result will be Failed. This command is very handy for deleting items in bulk.
IGNORE: the app will ignore this item and will skip it.
If no “Command” is specified in the import file then the app will assume
MERGE for all entities except Orders and Draft Orders where the app will assume
Tell the app, what to do with Tags:
MERGE: will add tags from the “Tags” column to existing tags for that item. It means that you don’t need to list all the tags in the import file, you can import those which you want to add. If some of the tags you are importing already exist, then the app will ignore them.
DELETE: will delete the tags that are listed in the import file. If the listed tag will not exist, then the app will ignore it.
REPLACE: will replace all existing tags with the tags from the import file. Use this method to maximize the import speed, because if you will use the
MERGEtags command, it means that the app will need first to load existing tags which takes additional time.
If Tags Command is not set, the app will assume the
REPLACE command by default.
“Image Command” can only be used for Products as only Products in Shopify can have multiple images.
Here you define the action, what to do with images:
MERGE: will keep all existing images for your product, update data of specified images from this import, and add any new images.
DELETE: if put next to the image, then this particular image will be deleted, while all other images will be kept.
REPLACE: will delete all other images, and keep only those, which are included in this import.
Images are never deleted or removed by default – only when you will give the explicit command to do so.
If “Image Command” is empty or such a column doesn’t exist, then the
MERGE value will be assumed.
Whenever variants are imported for Products, there is always one of those commands executed for each of the variant rows:
MERGE: merges new variants into existing product variants. Updates those that can be found by “Variant ID”, “Variant SKU”, “Variant Barcode” or Option Values. If Matrixify will not find such a variant to update, then it will attempt to add a new one.
UPDATE– will update variants that can be found by “Variant ID”, “Variant SKU”, “Variant Barcode” or Option Values. If a variant cannot be found to update, will fail the Product.
DELETE: will delete the listed variant. Requires “Variant ID”, “Variant SKU”, “Variant Barcode”, or Option Values – so that it can identify, which variant you want to delete.
REPLACE: will replace all existing product variants with the ones that are listed in the import. This will delete any variants that are not included in the import for that product.
If no “Variant Command” is specified, then the
MERGE value will be assumed.
See this Tutorial for more details about adding variants: How Add Variants To Existing Product.
Whenever addresses are imported for Customers, there is always one of those commands executed for each of the address rows:
MERGE: merges new addresses into existing customer addresses.
DELETE: will delete the listed address by “Address ID”, if no “Address ID” will be listed then the address will fail to delete.
REPLACE: will replace all existing customer addresses with the ones that are listed in the import. This will delete any addresses that are not included in the import for that Customer.
If no “Address Command” is specified, then the
MERGE value will be assumed.
The “Line Command” is used for Orders import to tell what to do with the Line Item rows when updating an existing Order.
DEFAULT: will create those Line Items only when creating a new Order, and will not try to add any new Line Items when updating.
MERGE: will create those Line Items when creating a new Order, and will also try to add any new Line Items to that Order if it is not already added to the Order.
Note that Shopify doesn’t allow adding Line Items to an Archived Order – that’s why we will unarchive, add, and archive your Order if it’s Archived.
See our tutorial on how to bulk add Line Items to existing Orders.
If no value is specified then
DEFAULT Line Command will be assumed.
Tell the app what to do with the Comment rows when importing Blog Post Comments.
MERGE: If a Comment with specified “Comment: ID” will be found then it will be updated. If it will not be found then it will be inserted as a new comment for that Blog Post.
UPDATE: strictly only update existing comments. If the comment with specified “Comment: ID” will not be found then this item import will fail. Using this when you update comments will allow you to make sure you are not creating any duplicate comments by accident.
DELETE: will delete that particular comment if it is found by specified “Comment: ID”. If it will not be found then it will be just skipped, assuming that it’s already deleted.
If no value is specified then the MERGE Comment Command is assumed by default.