Skip to content

Bulk actions

Changing many products at once: choosing the scope, previewing the impact, and what can be undone.

Available to roles Admin, EditorOpen in the app (Opens in a new tab)
On this page

"Bulk action" means two different things in Monokaido, and it is worth separating them at the outset:

WhatWhere it startsWhen it runs
A one-off bulk actionThe Bulk actions button in the product list, over a selection.Now, once.
A bulk-action ruleThis screen.Repeatedly — the action is applied automatically to whatever matches a saved filter.

This chapter is about the second one.

Bulk actions: the Rules and Execution history tabs, with an empty rule list
Fig. 1 Bulk actions. Rules are not created here — they come from saving a filter in the product list.

Controls on this screen

  1. RulesSaved prescriptions: a filter, plus the action to apply to it.
  2. Execution historyWhen each rule ran and how many products it touched. This is where you come to check the impact.
  3. What a rule doesApplies an action to the products matching a filter — not to a selection you ticked once.
  4. Where rules come fromFilter the product list and use "Save as rule". The empty screen says so outright.
  5. How it worksA summary of the procedure, on the screen.

How a bulk-action rule is made

  1. Filter the set in Products

    The filter is the definition of who the action applies to. It is worth eyeballing first — the number of matches is in the floating bar.

  2. Choose the action

    Through the Bulk actions button.

  3. Save as a rule

    Instead of running once, a prescription is stored. From then on the action applies to every product that matches the filter — including the ones that arrive tomorrow.

What can be undone

Individual changes, yes, through Changes to review — each carries its source, so what a given action did can be filtered out. But while the rule is enabled the next run makes the change again; disable the rule first.

Execution history says how many products each run touched. It is the first place to look when "something went wrong across the board".

The screen is empty. Where is a rule created?

In the product list: filter a set and use "Save as rule". This screen is a list and a history, not an editor.

How is this different from Rules?

Rules work from a condition on an individual product and run inside a flow. Bulk-action rules work from a filter over a set and apply an action that is otherwise available in the product list.

How many products can one run handle?

Large sets are processed in the background; you can watch them in Background processes.