Skip to main content
All CollectionsCatalogQuick Edit
Using QuickEdit to Initiate Bulk Actions
Using QuickEdit to Initiate Bulk Actions

Combine two powerful Zentail features to make sweeping changes to your catalog easily

Juliet Bishop avatar
Written by Juliet Bishop
Updated over a week ago

QuickEdit gives you the ability to easily view your SKUs filtered according to pretty much any product data criteria you can imagine. This feature pairs extremely well with Bulk Actions, allowing you to make changes to your catalog based on specific criteria. 

It is simple to initiate a Bulk Action from QuickEdit. After you have set up your filters all you need to do is click "Create Bulk Action" and you will automatically be redirected to the Bulk Actions page with the QuickEdit filter already applied where you can label and craft your Bulk Action. 

Learn more about different types of actions here

Some ideas of filters and Bulk Action pairings to get your started:

  • If you are setting up the repricer and haven't entered in your min and max price for some of your SKUs you can filter for your Min Price is blank and your Max Price is blank. Then for the Bulk Action you can Set Value for the Min Price to be a certain percentage less than your item price (perhaps .7*price) and the max price to be a certain percentage greater than your item price (like 1.4*price). 

  • If you have recently made product data changes to some SKUs in a certain brand and want to update the product data on eBay you can update and push all those SKUs. You'll want to filter by the brand and then select Update and Push to Channel as the Action Type. 

  • If you have a lot of FBA items and have not yet set up the values for "Are Batteries Required" and "Supplier Declared Dg Hz Regulation" (a requirement for FBA products, learn more about that here) you'll want to filter the "Type" field for contains FBA, and then set the Bulk Action to set values for "Are Batteries Required" (a boolean, so true or false) and "Supplier Declared Dg Hz Regulation" (if there is no hazmat consideration you'll want to set the value to be not_applicable). 

Related Reading

Did this answer your question?