Six ways to assign a count

Step by step

Assign a session (planned count)

1. Open Stocktaking and click New session. The New stocktaking session page opens. It is one scrollable page, not a step-by-step wizard.
2. In the Session card, fill in Session name. This is the only required field. Optionally narrow the count by Warehouse and Zone.
3. If the count should use rules other than the defaults, choose a Stocktaking scenario and override the mode under Counting mode (session override). Leaving it empty means “inherit.”
4. In the Locations card, choose a tab—Pattern, Range, Code list, or System suggestion—and fill in its fields. The From map tab is disabled.
5. Check the Session summary card on the right: Method and Number of locations. For Pattern and Range, it says Calculated after creation because the exact number cannot be known before saving.
6. Click Create session and tasks.
7. Read the “Session created. Tasks: {n} (skipped: {m}).” message; you will be taken to the session view.
8. If anything was skipped, instead of redirecting you will get a Some tasks were skipped window with a reason for each location. Choose Stay and fix or Open session.

Assign one task

1. Open Stocktaking and click New task.
2. In the New stocktaking task window, select Location. Enter at least two characters for the list to start searching.
3. Set Priority (default: Normal). Optionally attach the count to a campaign using Session (optional) and choose a Stocktaking scenario (optional).
4. Click Save. You will see “Task created.” If the shelf already has a count in progress, the system will tell you it opened the existing task instead of creating another one. You stay on the dashboard.

Note: the “eye” flags a shelf; it does not create a count by itself

The button sets a “needs checking” flag and sends a signal. Whether that creates a count depends on an automation rule. A rule is prepared but disabled. Until an administrator enables it, the request is only a flag.

The window after clicking tells you what actually happened. If the rule opened a count, you will see its number. Otherwise, it will not promise a count that the disabled rule never created.

This flag freezes the shelf. The system will not issue goods from a flagged shelf. The request is therefore reversible: click the same button to remove the flag. Removal is rejected if a count is already in progress at the location; then the flag belongs to the task, and closing the task removes it.

Session creator — five ways to select locations

1. Pattern, for example A0-*
2. Range, from A0-01 to A0-50
3. Code list, with codes pasted on separate lines or separated by commas
4. System suggestion, a ranking of locations most worth counting, based on discrepancy history, days since the last count, and location type (picking locations before sorting locations before the rest), with an ABC class filter
5. From map, not available yet

Two limits to know

A maximum of 100 tasks per assignment. Any extras appear in the “skipped” list with the reason “limit exceeded.” The session is created; assign the remainder in a second run.

Assigning a location that already has an active task does not create a second one. You will receive the existing task and a note that a task already exists for the location. The “created by” field continues to show the creator of the first task and does not change—hence the confusion: “I created this count, but the system says it belongs to someone else.”