Bulk order actions

Karl Falconer · Updated

To take the same action on many orders at once, select them in the orders list and use the bulk action bar.

Select orders

  1. From Sales Orders > Orders, search and filter the list to the orders you want to act on.
  2. Click the checkbox at the left of each row, or click the header checkbox to select every order on the current page.

A selection bar appears at the top of the table once at least one row is selected, showing the count and a Clear selection link.

Bulk action selection bar

Available bulk actions

The selection bar has the primary action (Retry Processing) on its own button, and the rest under a More Actions dropdown.

More Actions dropdown showing Reset, Archive, Delete

Retry Processing

The primary action — retries the most recent processing step for every selected order. Use this after fixing an underlying issue (warehouse outage, missing field on a store, rules error) to push a backlog of stuck orders forward at once.

Reset

Reverts all DropStream processing on the selected orders and starts each one over from import. This is destructive — any manual edits or rule mutations are lost. Reset is most useful when a store or rules change means a batch of orders needs to be re-evaluated from scratch.

Archive

Stops further processing on the selected orders without deleting them. Archived orders aren’t sent to the warehouse and aren’t re-imported from the source. To resume an archived order, open it and choose Reprocess or Reset from the Actions menu.

Delete

Permanently removes the selected orders from DropStream. Delete requires typing a confirmation phrase before it runs.

Important: Deleted orders are not removed from the source sales channel. If they’re still eligible for import there, DropStream will re-import them on the next sync, which can result in duplicate fulfillment. If you want to halt processing without that risk, use Archive instead.

Bulk action limits

Bulk actions are dispatched to the backend in batches of 250 orders. You can select more than 250 — DropStream queues the work and processes it asynchronously. The orders’ statuses update as each batch completes.

What happened to the separate Reprocess / Reset / Archive / Delete how-to articles?

Those four actions are now documented together because they share the same workflow. The previous standalone articles redirect here.

Was this article helpful?
0 out of 0 found this helpful

Comments

0 comments

Please sign in to leave a comment.