User Manual
Help Center/User Manual/Task Rules: configure how WMS tasks are created and assigned

Task Rules: configure how WMS tasks are created and assigned

Last updated 2026-10-18

One page for all WMS task rules: a tab per task type (pick / putaway / move / replenishment / count / SLA / cross dock), per-client configuration, and L1/L2/L3 rule tiers from everyday to expert.

Task Rules is the single home for every WMS task rule. Open WMS → Task Rules. The top tabs switch task types — Replenishment (补货), Move (移库), Putaway (上架), Picking (拣选), Cycle Count (盘点), SLA, and Cross dock. A tab can also be deep-linked, e.g. share /wms/task-rules?tab=replenishment and the page opens straight on Replenishment.

Task Rules page: seven tabs for task types, client selector at the top right, rule sections with toggles and sliders
Tabs on top switch the task type; the client selector on the right scopes every rule below.

Pick the client first, then tune the rules#

The client selector sits at the top right. Leave it on "All (tenant default)" and your changes become the default for everyone. Pick one client and the page switches to per-client mode — that client gets its own rule values. Switching tabs reloads the client list for the new domain, so a rule set that only exists for replenishment never shows up under picking.

Three sections inside each tab#

  • Hard constraints: candidates that violate these are out, no discussion (e.g. a location type that cannot store the goods).
  • Soft preferences: scoring rules with a weight slider — the higher the weight, the more this preference matters.
  • Auto-assign: rules that decide who gets the task once it is created (codes starting W-R-A / W-M-A / W-P-A / W-K-A).
  • Picking has one extra section: Zone Picking rules (W-K-Z1..Z4) that limit picking to specific zones.

Client strategy exceptions (Putaway & Picking tabs)#

Below the rule list, the Putaway and Picking tabs each carry a "Client strategy exceptions" table — one row per client. The client exception applies to all warehouses; if a client needs something different in just one warehouse, set the exception for the warehouse selected at the top of the page instead. Priority: this-warehouse exception > client exception > the global rules above. Clients left on "Follow global rules" simply use the rules above (on the Picking tab, that is the allocation strategy rule). One difference on the Putaway tab: if the global rules above already name a putaway strategy, the rule wins — the exception only applies when the rules do not specify one. The last column always shows which strategy is effective for that client in the current warehouse, and where it comes from.

The client (merchant) detail page no longer edits strategies — it shows a read-only summary of what is effective for that client, with buttons that jump straight to the right Task Rules tab.

Rule tiers: L1 / L2 / L3#

  • L1 — Everyday: the rules business users actually touch. On/off switches, weight sliders, and simple parameters.
  • L2 — Advanced: more parameters, subtler effects. Adjust them only if you understand what they do.
  • L3 — System: gray rows with a lock icon. Visible so you know they exist, but read-only — you cannot edit them.
Rule tiers: a pyramid with L1 everyday rules at the bottom, L2 advanced in the middle, L3 locked system rules at the top
Wider at the bottom: most of what you touch day to day is L1. L3 is locked for a reason.
L3 system rules affect the whole flow — changing one the wrong way can break task creation or assignment for everyone. They are read-only on purpose. If a business need really requires changing one, talk to your admin or support instead of working around it.

Three recipes: scenario → where to click → what to change → scope#

Recipe 1: one client wants faster replenishment

  • Scenario: Client A ships a lot; its picking locations keep running dry.
  • Where to click: Task Rules → Replenishment tab → client selector → Client A.
  • What to change: raise the weight of the trigger/priority soft rules so shortages at A’s locations score higher.
  • Scope: only Client A’s replenishment tasks. Everyone else keeps the tenant default.

Recipe 2: picking only from the picking zone

  • Scenario: pickers keep wandering into bulk storage to grab stock.
  • Where to click: Task Rules → Picking tab → the Zone Picking section.
  • What to change: the zone rules (W-K-Z1..Z4) — restrict the pick range to the picking zone.
  • Scope: picking tasks of the selected client (or the tenant default).

Recipe 3: auto-assign move tasks to the shift

  • Scenario: move tasks sit unassigned until someone claims them.
  • Where to click: Task Rules → Move tab → the Auto-assign section.
  • What to change: the auto-assign rules — turn on automatic assignment to on-shift staff.
  • Scope: all clients (tenant default) or one selected client — your choice at the top right.
After changing rules, use the built-in test mode on the page: it shows which rules a sample case would hit before anything goes live. Change → test → save, not change → save → pray.