Mass Product Actions for Magento 2

On Catalog > Products: tick the products, open Actions and then More actions. Each action opens a short form in a pop-up. Magento's own actions (Delete, Change status, Update attributes) are not changed.

Yes. In Catalog > Products tick one or more products and choose Actions > Edit in grid to edit them in place. By default clicking a row still opens the product page, as in Magento; to start editing with a click, set Stores > Configuration > CommerceGears > Mass Product Actions > Product Grid Editor > Clicking a Product Row to "Starts editing in the grid". Names, SKUs, prices, special prices and dates, cost, quantity, stock status, status, visibility, URL keys, meta fields and other text, number, date, dropdown and multiple select attributes can be edited. Press Enter or Save to save, Esc to cancel.

Yes. Every save from the grid is a job in the job log, with the old and new value of every changed cell, and Undo Job puts the old values back (including SKUs, stock and URL keys with their URL rewrites). The product page has a Change History button that lists the jobs that changed the product.

Choose a store view in the grid's Store View filter to edit that store view. Cells with a value of their own on the store view are marked. Typing the default value creates no store view value, and clearing a cell goes back to the default value. With All Store Views you edit the default values and store views keep their own values.

Yes. Open the rows with Edit in grid, click the first cell and paste a copied column (or block of columns): the values fill the rows downwards in the order shown. Dropdown cells accept the option label or its ID. Nothing is saved until you press Save, and invalid values are marked on their cell.

Yes. Type +10%, -10%, +5 or -5 in a price, special price or cost cell, and +5 or -5 for quantities. The result can be rounded to an ending such as .99 (setting Rounding for Relative Price Changes).

The grid sends the value each cell had when you loaded it. If the value has changed since, that cell is refused with the current value instead of overwriting the other change. Nothing is saved until every changed cell is valid.

Fifteen: update price, special price and cost; add, remove or replace categories; add to or remove from websites; change status by store view; change visibility; update stock; assign attribute value; change attribute set; related, up-sell and cross-sell links; copy custom options from a product; copy images from a product; duplicate products; append or replace text.

Yes, for update price, update special price, update cost and append or replace text. The Preview button shows the current and the new value for the first 10 selected products, or why a product would be skipped. Nothing is saved until you press Apply.

Yes, for 12 of the 15 actions: everything except copying custom options, copying images and duplicating. The module keeps the values from before the job for every changed product, and Undo Job on the job page puts them back. Undo overwrites later changes to the same fields of those products; the job page lists later jobs that touched the same fields, and the confirmation names them. Undo data is kept as long as the job (60 days by default).

Selections up to Run Immediately Up To (Products) (default 50) are updated straight away. Larger ones are queued and processed by cron in batches, in their own cron group so that other cron jobs are not held up. The job page shows the progress, and an interrupted job continues where it stopped.

Yes. Attribute changes go through Magento's own updateAttributes() (the same path as the native "Update attributes"), then the price, EAV, category, stock, flat, search and catalogue rule indexers are run for the changed products, or left to Magento when indexers are set to "Update by Schedule". The page cache is cleaned for those products.

Status, visibility and attribute values can be set for all store views or for one. Global attributes (for example the price with catalogue price scope "Global") are always written to all store views, and website-scope attributes apply to all store views of that website, as in Magento itself. You can also remove store-view values so the default value applies again.

Yes. Every action has its own permission under CommerceGears > Mass Product Actions > Run Mass Actions, plus permissions for the job log, cancelling and deleting jobs, undo and the settings. The More actions menu only lists what the user may run. Assigning price attributes also needs the matching price permission, and design attributes need Magento's "Edit Product Design" permission. Editing in the grid has its own permission, with separate permissions for prices, for quantity and stock status, and for SKU and URL key; other columns stay read-only.

Only with the default stock. Update stock and the Quantity and Stock Status cells of the grid change the default stock quantity and status; quantities per source are not supported.

Adobe Commerce content staging (scheduled updates with row versions) is not supported, so the module is meant for Magento Open Source 2.4.6 to 2.4.9.

No. It only adds admin features. Products you change behave on Luma, Hyvä or any other theme exactly as if you had edited them in the product form.

Yes: bin/magento commercegears:mass-actions:process processes queued jobs straight away (also one job with --job), and bin/magento commercegears:mass-actions:jobs lists recent jobs.