Run actions on orders (Operations)
Operations is a terminal for running actions across many orders at once. You filter and select the orders you want, build a short pipeline of actions, and run it. Every run is logged with a per-order, per-step result so you can see exactly what happened and retry anything that failed - all on one screen. There is no "operation" to create or manage.
Open Operations
1. Target the orders
The left pane is a live, filterable order list.
- Use the filter builder to narrow by any order field - order number, customer, status, fulfillment status, payment status, lifecycle state, tags, order total, or created date - with contains / equals / greater-than and other operators.
- Check the orders you want, or click add all N matching to select every order the current filter returns.
- You can also paste order numbers or IDs directly.
2. Build the pipeline
In the right pane, choose an action from add action and set its inputs. Add more to run them in order on each targeted order.
| Action | Does |
|---|---|
| Rate & assign | Rate every carrier and assign the best service (cheapest / fastest, optional preferred carrier) |
| Assign location | Set the fulfillment location |
| Set ship date | Set the requested ship date |
| Set priority | Set order priority (low / normal / high / urgent) |
| Bulk edit order field | Set a chosen order field (priority, status, fulfillment status, ship date) to a value |
| Bulk edit SKU quantity | Set the quantity for a SKU across the order's line items |
| Apply tag / Remove tag | Add or remove a tag |
| Add note | Attach an internal note |
| Mark fulfilled | Mark orders fulfilled |
| Mark shipped | Mark a purchased label physically shipped |
| Release | Release the order to its dispatch destination |
| Void label | Void or refund the active purchased label (destructive) |
| Cancel order | Cancel the order (destructive) |
For each order the steps run top to bottom and stop at the first failed step, so a broken order never runs its dependent later steps. A pipeline that includes a destructive action asks you to confirm before it runs.
3. Run and review
Click run to execute the pipeline against the selected orders. The run output console shows each order with a tick or cross per step and the failure reason inline. The run is saved to run history below - click any past run to reopen its results.
If some orders failed (for example a rate came back empty, or a label was already voided), fix the underlying issue and click retry N failed on the run. That re-runs only the failed orders as a new, linked run.