Results and customer emails

Result outcomes

• Changed: the order moved to the requested status.
• Skipped: no change was needed, often because the order already had that status.
• Needs attention: the row was skipped because its order ID is invalid, the order was not found, or the target status is unknown. These rows count toward the skipped total.
• Errored: WooCommerce could not complete the change.
• Would change: validation confirms the row can be applied in a real run.

Investigate a row

Search by order number, status, or result text. Filter the table by outcome to isolate rows that need work. Open an order from its linked number when you need its history and notes.

An invalid ID such as 12abc or 12.0 is shown as entered, alongside Skipped - invalid order ID (CSV row 2). The row number counts the header and blank rows, so you can find the mistake even when the ID is empty. Invalid IDs have no order link and never change an order. They are reported in interactive mode, background mode, and validation-only runs, including files where every ID is invalid.

Export the result log

Download the result table as CSV for an audit trail or to return outcomes to the source system. Choose the delimiter so it matches the spreadsheet workflow your team already uses.

The download includes the invalid-ID results and their CSV row numbers. For large imports, the table and download contain up to the first 1,000 results; the summary counts every row.

Control customer emails

By default, the status change behaves like a manual WooCommerce edit, including any email attached to the new status.

Enable Do not send customer emails when correcting old data or when notification is handled elsewhere. This skips customer notifications for the orders being updated. Administrator notifications, such as an order cancellation email to the store, and emails for other orders continue normally. Order notes are still recorded.

The same setting applies in interactive and background mode, including when WooCommerce queues status emails for later delivery.

Decide per row

A file can carry an optional notify column when some orders should notify the customer and others should not. Use 1 to allow the normal customer notification for that row and 0 to skip it.

The row decides, and Do not send customer emails fills in the rows that leave the cell empty. An empty cell is not the same as 0: an empty cell falls back to the screen, while 0 explicitly skips the customer notification.

Apply that to every row ignores the column and skips customer notifications for every imported row. It becomes available once Do not send customer emails is enabled, so the column can always ask for silence even when the screen has not.