Raise 340 Magento prices by 5%. Know how to undo it first.

Your supplier raises costs by 5%. You filter 340 products in Magento, ready to adjust their prices. One mistake in scope or rounding will reach all 340.

Those figures are an example, but the decision is familiar: use a temporary promotion, a CSV import or a repeatable bulk action? Choose based on what must change, and establish the restore path before writing new values.

A sale isn't always a price edit

If the change is a temporary discount, a catalogue price rule may leave the underlying prices intact and end on the specified date. If the regular price needs a permanent increase, you need a price update.

Magento's native Update Attributes action is useful when the selected products should receive the same value. A CSV import is useful for externally calculated, SKU-specific prices. Neither is the same as applying arithmetic to every current price with a preview and job-level undo.

Preview the awkward products, not just the first easy one

Our Mass Product Actions module adds percentage and amount-based changes with rounding options to the product grid. Preview shows current and proposed values for the first ten selected products, including skip reasons.

The first ten are a sample, not proof about the entire selection. Filter deliberately and test representative product types and price scopes. Configurable products and dynamic-price bundles are skipped because their prices come from their children or components. Check that the priced simple products you intend to change are in scope.

Check what the storefront will charge

A hypothetical product at £40 becomes £42 after a 5% increase, before any rounding. Customer-group prices, special prices and catalogue rules may change the amount a customer sees. Tax display and website scope matter too.

Test a representative product on the correct website as the relevant customer group. With scheduled indexers or background jobs, allow the supported processing to complete before judging the result. Check failures and skipped items rather than relying on the submitted job count.

Undo restores a snapshot

The module records pre-change values and can restore them as a new, logged job. It does not simply subtract the original percentage. That matters if someone edited a product after the bulk job: restoring the snapshot can overwrite their later work.

Review later changes before undoing, and unwind overlapping jobs in reverse order where appropriate. Job retention governs how long undo data remains available; the documented default is 60 days, not permanent history.

Also note the limits: copying images or custom options and duplicating products are not undoable. Adobe Commerce content staging and per-source MSI stock changes are unsupported. An interrupted batch can affect the reliability of its recorded pre-change values when replayed, so inspect failed jobs before assuming a clean restore.

Keep CSV where it earns its place

Use an import when a supplier provides a different explicit price for every SKU or when many attributes change together. Keep the original export, validate the file and test a small representative selection first.

Use a bulk action when the same rule recurs and your team benefits from preview, processing status and a recorded restore action. For accountability across separate admin changes, read who changed this price? or keep a Magento 2 admin log with Admin Activity Log.

Open the Mass Product Actions demo and preview your intended rule. Before applying it, open the undo flow and inspect what it will restore.