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 Operations1. Target the orders
The left pane is a live, filterable order list.
- Use the filter builder to narrow by order number, customer, status,
fulfillment status, payment status, lifecycle state, priority, tags, location,
ship-to city / state / country / postal code, SKU, order total, assigned carrier
or service, label status, order date, or requested ship date. The same filters
are available on
GET /api/v1/orders. - 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.
The 24 actions are grouped by category.
Routing
| Action | Does |
|---|---|
| Assign location | Set the fulfillment location |
| Assign default location | Fill the location from the release routing default, optionally overwriting an existing one |
| Override dispatcher | Route the order to a chosen dispatcher destination |
| Rate and assign | Rate carriers and assign a service (cheapest, fastest, or cheapest on a chosen carrier account, with an optional price ceiling in minor units of your billing currency, for example 1500 = 15.00) |
| Assign specific service | Assign one exact carrier service on a carrier account |
| Override carrier | Assign the cheapest service from one carrier account |
| Clear assigned service | Remove the assigned service so the order can be re-rated |
Fulfillment
| Action | Does |
|---|---|
| Release | Release the order to fulfillment; optionally acknowledge release warnings |
| Un-release | Pull the order back to awaiting release |
| Mark fulfilled | Set fulfillment status to fulfilled |
| Mark shipped | Mark the latest label-created shipment as shipped |
| Cancel orders | Cancel the order, release inventory, and record a reason (destructive) |
Labels
| Action | Does |
|---|---|
| Void label | Void or refund the active purchased label (destructive) |
| Reprint label and slip | Regenerate the label PDF, with the packing slip when requested |
Inventory
| Action | Does |
|---|---|
| Allocate inventory | Advance reserved lines to allocated |
| Mark picked | Advance reserved or allocated lines to picked |
Data
| Action | Does |
|---|---|
| Apply tag / Remove tag / Clear tags | Add a tag, remove a tag, or remove every tag |
| Add note | Append a note to the order activity |
| Set priority | Set order priority (low / normal / high / urgent) |
| Set ship date | Set the requested ship date |
| Bulk edit order field | Set one order field, such as priority, status, tags, customer or ship-to details, or a custom metadata key. Leave the value empty to clear a field that can be cleared |
| Edit line items | Set a quantity, add, remove, or re-SKU a line and recompute totals. Not available once the order is fulfilled, has a purchased label, or holds reserved inventory |
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. Each step's changes are saved before the next step runs, so a location assigned in one step is the location the next step rates from or releases from. The routing actions are not available for a cancelled order or one that already has a purchased label. A step that succeeds but hit a non-fatal problem (for example, inventory reservations could not be released during a cancel) shows a warning on that step. A pipeline that includes a destructive action asks you to confirm before it runs.
Before you run, the console checks every selected order against the pipeline and shows which steps would be blocked and why. The check follows the pipeline order, so assigning a location in an earlier step clears a "no fulfilment location" blocker on a later release or rating step.
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. Each order picks up at the step that failed: the steps that already succeeded are shown as skipped and are not run again, so a retry never adds a second note or line.