Get Excelify now
Get Excelify now

List of Commands across Excelify Sheets

Products

Command

When importing Product row – tell the app, what to do with it:

  • NEW: will try to create a new Product with the provided details. If such Product will already exist (with the same ID or same Handle), then the result will be Failed.
  • UPDATE: will try to find existing Product, and update it with data from the row. If such product will not be found, then it will create new.
  • REPLACE: at first, if such Product with provided ID or Handle exists, then the app will delete it. After that, it will create a new one. If an existing Product 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 Product will be deleted and re-created.
  • DELETE: the app will delete the existing Product, which is found by ID or Handle. If such Product will not be found, then the result will be Failed. This DELETE command is very handy for deleting Products in bulk.

If no Command is specified, then the app will assume the UPDATE command.

Tags Command

Tell the app, what to do with Tags:

  • MERGE: will add Tags to existing tags. 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 it.
  • 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 MERGE, 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

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 column don’t exist, then the MERGE command will be assumed.

Variant Command

Whenever variants are imported, there is always one of those commands executed for each of 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 it will not find such variant to update, then it will add new.
  • 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 will be assumed.

See this Tutorial for more details about adding variants: How Add Variants To Existing Product.

Smart Collections

Command

When importing Smart Collection row – tell the app, what to do with it:

  • NEW: will try to create a new Smart Collection with the provided details. If such Smart Collection will already exist (with the same ID or same Handle), then the result will be Failed.
  • UPDATE: will try to find existing Smart Collection, and update it with data from the row. If such Smart Collection will not be found, then it will create new.
  • REPLACE: at first, if such Smart Collection with provided ID or Handle exists, then the app will delete it. After that, it will create a new one. If an existing Smart Collection 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 Smart Collection will be deleted and re-created.
  • DELETE: the app will delete the existing Smart Collection, which is found by ID or Handle. If such Smart Collection will not be found, then the result will be Failed. This DELETE command is very handy for deleting Smart Collections in bulk.

If no Command is specified, then the app will assume the UPDATE command.

Custom Collections

Command

When importing Custom Collection row – tell the app, what to do with it:

  • NEW: will try to create a new Custom Collection with the provided details. If such Custom Collection will already exist (with the same ID or same Handle), then the result will be Failed.
  • UPDATE: will try to find existing Custom Collection, and update it with data from the row. If such Custom Collection will not be found, then it will create new.
  • REPLACE: at first, if such Custom Collection with provided ID or Handle exists, then the app will delete it. After that, it will create a new one. If an existing Custom Collection 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 Custom Collection will be deleted and re-created.
  • DELETE: the app will delete the existing Custom Collection, which is found by ID or Handle. If such Custom Collection will not be found, then the result will be Failed. This DELETE command is very handy for deleting Custom Collections in bulk.

If no Command is specified, then the app will assume the UPDATE command.

Customers

Command

When importing Customer row – tell the app, what to do with it:

  • NEW: will try to create a new Customer with the provided details. If such Customer will already exist (with the same ID or same Email), then the result will be Failed.
  • UPDATE: will try to find existing Customer, and update it with data from the row. If such Customer will not be found, then it will create new.
  • REPLACE: at first, if such Customer with provided ID or Email exists, then the app will delete it. After that, it will create a new one. If an existing Customer 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 Customer will be deleted and re-created.
  • DELETE: the app will delete the existing Customer, which is found by ID or Email. If such Customer will not be found, then the result will be Failed. This DELETE command is very handy for deleting Customers in bulk.

If no Command is specified, then the app will assume the UPDATE command.

Tags Command

Tell the app, what to do with Tags:

  • MERGE: will add Tags to existing tags. 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 it.
  • 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 MERGE, 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.

Address Command

Whenever addresses are imported, 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 “Variant ID”, if no “Variant ID” will be listed 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 will be assumed.

Discounts

Command

When importing Discount row – tell the app, what to do with it:

  • NEW: will try to create a new Discount with the provided details. If such Discount will already exist (with the same ID or same Code), then the result will be Failed.
  • UPDATE: will try to find existing Discount, and update it with data from the row. If such Discount will not be found, then it will create new.
  • REPLACE: at first, if such Discount with provided ID or Code exists, then the app will delete it. After that, it will create a new one. If an existing Discount 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 the columns, which were not included in the import file since the Discount will be deleted and re-created.
  • DELETE: the app will delete the existing Discount, which is found by ID or Code. If such Discount will not be found, then the result will be Failed. This DELETE command is very handy for deleting Discounts in bulk.

If no Command is specified, then the app will assume the UPDATE command.

Draft Orders

Command

When importing Draft Order, it tells the app, what to do with it.

  • NEW: will try to create a new Draft Order with the provided details. If such Draft Order will already exist (with the same ID or same Name), the Draft Order creation will fail.
  • UPDATE: Allows to update some of the existing Draft Order attributes. Here is the list of what can be updated.
  • REPLACE: at first, if such Draft Order with provided ID or Name exists, then the app will delete it. After that, it will create a new one. If an existing Draft Order will not be found, then still the app will create a new Draft Order.
  • DELETE: the app will delete the existing Draft Order, which is found by ID or Name. If such Draft Order will not be found, then this item import will fail. This DELETE command can be very handy when Draft Orders need to be deleted in bulk, or when such Draft Orders need to be deleted, which cannot be deleted through the Shopify Admin.

Orders

Command

When importing Order, it tells the app, what to do with it.

  • NEW: will try to create a new Order with the provided details. If such Order will already exist (with the same ID or same Name), then Order creation will fail.
  • UPDATE: Allows to update some of the existing Order attributes. Here is the list of what can be updated.
  • REPLACE: at first, if such Order with provided ID or Name exists, then the app will delete it. After that, it will create a new one. If an existing Order will not be found, then still the app will create a new Order.
  • DELETE: the app will delete the existing Order, which is found by ID or Name. If such order will not be found, then this order import will fail. This DELETE command can be very handy, when Orders need to be deleted in bulk, or when such orders need to be deleted, which cannot be deleted through the Shopify Admin.

Pages

Command

When importing Page row – tell the app, what to do with it:

  • NEW: will try to create a new Page with the provided details. If such Page will already exist (with the same ID or same Handle), then the result will be Failed.
  • UPDATE: will try to find existing Page, and update it with data from the row. If such Page will not be found, then it will create new.
  • REPLACE: at first, if such Page with provided ID or Handle exists, then the app will delete it. After that, it will create a new one. If an existing Page 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 the columns, which were not included in the import file since the Page will be deleted and re-created.
  • DELETE: the app will delete the existing Page, which is found by ID or Handle. If such Page will not be found, then the result will be Failed. This DELETE command is very handy for deleting Pages in bulk.

If no Command is specified, then the app will assume the UPDATE command.

Blog Posts

Command

When importing Blog Post row – tell the app, what to do with it:

  • NEW: will try to create a new Blog Post with the provided details. If such Blog Post will already exist (with the same ID or same Handle), then the result will be Failed.
  • UPDATE: will try to find existing Blog Post, and update it with data from the row. If such Blog Post will not be found, then it will create new. All the existing Blog Comments will be kept.
  • REPLACE: at first, if such Blog Post with provided ID or Handle exists, then the app will delete it. After that, it will create a new one. If an existing Blog Post 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 the columns, which were not included in the import file since the Blog Post will be deleted and re-created. All the existing related Comments will be lost.
  • DELETE: the app will delete the existing Blog Post, which is found by ID or Handle. If such Blog Post will not be found, then the result will be Failed. This DELETE command is very handy for deleting Blog Posts in bulk.

If no Command is specified, then the app will assume the UPDATE command.

Comment Command

Tell the app what to do with the Comment row:

  • UPSERT: it means “insert or update”. If the 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.
  • UPDATE: strictly only update existing comment. 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 UPSERT is assumed by default.

Redirects

Command

When importing Redirect row – tell the app, what to do with it:

    • NEW: will try to create a new Redirect with the provided details. If such Redirect will already exist (with the same ID or same Path), then the result will be Failed.
    • UPDATE: will try to find existing Redirect, and update it with data from the row. If such a Redirect will not be found, then it will create new.
    • REPLACE: at first, if such Redirect with provided ID or Path exists, then the app will delete it. After that, it will create a new one. If an existing Redirect 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 the columns, which were not included in the import file since the Redirect will be deleted and re-created.
    • DELETE: the app will delete the existing Redirect, which is found by ID or by Path. If such a Redirect will not be found, then the result will be Failed. This DELETE command is very handy for deleting Redirects in bulk.

If no Command is specified, then the app will assume the UPDATE command.