Mass Price Updater: setup and help

1. Upload and install the mprmasspriceupdate ZIP in Modules > Module Manager.
2. Click Configure. You reach Mass Price Updater under the Sell area.
3. Choose the intended single-shop context before preparing an operation.
4. Open Mass Price Updater > Settings > Configuration and confirm Enable module is on.
5. Return to Mass Price Updater to prepare a preview.

The module starts enabled. It installs update history, scheduled-job, result and snapshot tables. Keep a normal database backup before changing catalog prices. Immediate operations do not create rollback snapshots.

Product selection uses active state and available shop prices in the resolved shop context. Names use the default shop language. In all-shop or ambiguous contexts, the module can use the default shop. Select one shop explicitly rather than expecting a broadcast update.

Examples:

• Supplier cost increase: choose By Supplier, select supplier 12, choose Wholesale Price, Increase by %, and enter 7.
• Category price reduction: choose By Category, select category 8, choose Price (tax excl.), Decrease by fixed amount, and enter 5.00.
• Catalog increase: choose All Products, Price (tax excl.), Increase by %, and enter 10.

The selector stores the chosen ID in scope_entity. For example, category 8 uses {"categories":{"groups":[{"include":{"values":[8]}}]}}. Use the selector rather than editing stored JSON for routine operations.

Click Preview Changes. Review product ID, name, current price, new price and difference. The form then exposes Apply Changes and Schedule Job. Changing operation fields requires another preview in the UI.

Calculations round to six decimal places. The preview displays two decimal places. For a current value of 100:

Decreases stop at zero. Click Apply Changes and confirm the browser prompt only after reviewing the scope and field. The operation reselects matching products and reads current prices when it runs. The preview is not a locked price snapshot.

The module records successful changes with the formula, field, affected count, employee and date in the prefixed mprmasspriceupdate_log table. ps_ is only an example database prefix.

After previewing, enter a future Schedule for date and time, then click Schedule Job. Dates are parsed in the PHP server's configured timezone. Confirm the displayed scheduled time.

Open Mass Price Updater > Scheduled Jobs to review status and results. Job actions include:

• Run now: execute a pending job before its due time.
• Cancel: cancel a pending job.
• Rollback: restore recorded snapshots for an eligible executed job.

A scheduled job stores the scope and formula. Matching products and prices are resolved again at execution, so they can differ from the original preview.

The shared cron task is run_scheduled_price_updates, labelled Run scheduled mass price updates, with schedule every:300. It processes up to 20 due jobs per invocation. Configure the shop's MPR cron runner to run it. The module also provides a token-authenticated front controller:

https://example.com/index.php?fc=module&module=mprmasspriceupdate&controller=cron&token=YOUR_MODULE_CRON_TOKEN

Use the module's actual generated cron token. Do not substitute a back-office token. Check the JSON result and Scheduled Jobs status after the first scheduled run.

Scheduled jobs save old values before changing rows. Eligible jobs in done, failed or interrupted-running states can have their remaining snapshots restored. A rollback retry skips snapshots already restored.

Rollback writes the saved old values. It can overwrite later manual price edits to those same rows. Review later changes before using it. Immediate Apply Changes operations do not have these snapshots or a module rollback action. Restore those from your own backup if needed.

In multistore, updates target the selected product_shop row and do not rewrite the global product price. In single-shop operation, the module can update both base and shop rows. It updates date_upd and emits the catalog price-mutation event for base-price changes.

Only price and wholesale_price are changed. The module does not directly edit specific prices, cart rules, customer-group reductions, combination price impacts or promotion records. Existing rules can still affect the price shoppers finally pay.

There is no CSV selection or per-product deselection in the preview. Your selected scope is applied as a whole.

Test a small scope first. Compare the product's tax-exclusive or wholesale value before and after the operation. Check the storefront with its taxes and existing discounts in mind. Review history or the scheduled result.

If nothing matches, check active state, target selection, shop context and default-language records. If no prices change, check Enable module and whether the calculated value equals the current value. If a scheduled job stays pending, check the runner, due time and cron token. If a job is locked, wait for the current runner and inspect its status before retrying.

Use Settings > Integrity for missing module tables or installation problems.

Turn off Enable module to stop execution, including job execution and rollback. Cancel pending jobs you no longer want before re-enabling.

Uninstall removes module configuration, cron registration, menu and schema tables. Export history and finish any required rollback first. Uninstall does not restore prices already changed.

Requires PrestaShop 1.6 or later and PHP 7.1 or later.