FastOps for WooCommerce
Sign in Book a demo

Chapter 07 · User guide

Bulk operations

Change many records at once: choose the scope, let FastOps snapshot the targets, follow the progress, cancel if needed and review the error ledger.

01 · Start a bulk update

Two ways in

The Bulk update products dialog open over the product list, with three rows ticked.
Starting a bulk update from ticked rows. The dialog opens over the list.
  1. Tick the rows you want to change; three are ticked here.
  2. The selection bar counts them.
  3. Edit selected starts a bulk update for exactly those rows.
  4. Bulk update starts one for the current list or the whole store.
  5. Scope: Selected records here; the current list or the whole store are the other choices.
  6. Field to change. Only fields that are safe to change in bulk are offered.
  7. The new value for that field.
  8. Include variations applies the same change to a variable product's variations.
  9. The confirmation states how many records will be changed.
  10. Start bulk update.
  1. Tick rows and choose Edit selected, or choose Bulk update at the top of the list.
  2. Pick the field or fields to change and their new values. Only fields that are safe to change in bulk are offered.
  3. Review the confirmation, which states how many records will be changed, and choose Start bulk update.

02 · Choose the scope

Selected, current list, or all

ScopeWhat it changes
SelectedOnly the rows you ticked.
CurrentEvery record matching the search, status tab and filters currently applied, including rows on pages you have not scrolled to.
AllEvery record of that type in the store.
Check the countThe confirmation always shows the number of records the job will touch. If it is larger than you expected, cancel and narrow the list first.

03 · The snapshot

The job cannot drift

When you start a job, FastOps first snapshots the list of target records. A product that stops matching the filter while the job runs is still changed; one that starts matching afterwards is not. What you confirmed is what gets changed.

For very large scopes the snapshot itself is built in the background: the job is accepted immediately and progress shows "snapshotting" until the targets are fixed.

04 · Progress and cancelling

Watch it run, stop it if needed

A progress panel shows how many records are done, how many remain and how many failed. You can leave the page; the job continues in the background worker.

Choose Cancel remaining to stop. Records already changed stay changed; the rest are left untouched and the job is marked Cancelled.

05 · The error ledger

Every failure is listed, with the reason

Each record in a job is version-checked individually. If a record was edited by someone else since the snapshot, or an extension rejected the change, that record is skipped and the reason is written to the job's error ledger. The rest of the job continues.

When the job finishes, the panel says how many records could not be changed. Open the ledger to see each one with its message, fix the cause, and run the job again for just those records.

If processing stopsRepeated failures stop the job rather than ploughing on. Review the errors before retrying.

06 · How long it takes

Set expectations

Everyday single-record actions complete in a second or less on a correctly configured store. A bulk job is different: each record is written through WooCommerce so that every hook and extension runs, which takes as long as those records and your plugins require.

  • Progress is always visible: the panel shows how many records remain, so you can judge the rest from the pace so far.
  • If the background worker is not running, the job waits and the workspace shows a notice. See Troubleshooting.
  • Schedule very large jobs for a quiet period; they share the server with the storefront.