Configuration

A configuration is a saved set of decisions. You can run it on a schedule, or run it once with its own settings without touching what is saved.

Which orders are reviewed

Only reviewed orders become part of the run. Their demand is the number the run works from.

Statuses decide which open orders are candidates: unfulfilled, in progress, and on hold.
One exclusion tag keeps orders out of every run. An order carrying it is never reviewed — usually preorder or wholesale.

An excluded order still spends its stock. See How a run works for why that matters.

Which locations count

Choose the locations the run may use, or use all active locations. Each location is judged on its own stock, and an order ships only when every location it needs can cover its share.

What to do with each verdict

Every reviewed order gets one verdict — can ship or cannot ship — and each verdict can carry actions:

Tag the order. Optionally, the app adds a tag you choose, such as ready-to-ship, to orders that can ship. It is the simplest way to hand the answer to your team.
Place or release a hold. Holds become the lock if you prefer not to write tags to orders.
Do nothing. Useful while you are still judging the verdicts in Preview.

Locking an order once it can ship

Optionally, the app can stop reviewing orders it tagged as shippable. On later runs those orders are skipped, so a verdict that has become true stays true without anyone watching.

The exclusion tag is a different mechanism and does a different job: it keeps an order out of every run from the start. The lock applies only to orders the app itself tagged as shippable.

The exit is a person. Remove the tag — or release the hold — and the order returns to the run.

A lock holds back one tag’s worth of orders. A shop that reviews two distinct order groups — usually split by tag — needs a configuration for each, and each configuration’s own tag is what holds its orders.

Schedule or one-off

A schedule reviews the shop at chosen times, intervals, and days, in the shop’s own time zone. It follows that zone: if the shop’s time zone changes, the run times move with it, so 09:00 stays 09:00 where the work happens. Pausing keeps the schedule and stops the runs.
A one-off run uses its own settings and changes no saved configuration. It does not replace a schedule.

A late run still happens once rather than replaying the missed hours.

Preview and Live

Preview mode makes every run record what it would do and do nothing. The one-off modal’s own Preview/Live choice is disabled while it is on, and the form says so.

A preview run and a live run write the same record; only the outcomes differ (would_be versus applied). That is what makes a preview evidence rather than a rehearsal.