Replenishment sessions — create, assign, archive

Session list: Replenishment → Sessions. Summary cards above it show Sessions, Task progress, Tasks in progress, and Sessions with shortages.

Step by step — from an empty list to an active shift

1. Open Warehouse and logistics → Replenishment → Sessions. Make sure you are on Active, not Archive.
2. Click Create session in the top-right corner. The New replenishment session window opens.
3. Fill in Session name; it is the only required field. Operators use the name to recognize the session on the terminal. Leaving it empty returns Enter a session name.
4. Optionally narrow Warehouse (optional) and add Notes (optional).
5. Click Create. The session appears in the To pick group.
6. Add tasks: click ⋮ at the end of the session row and choose Add tasks. The Add tasks to session window lists available tasks in Number, Product, Source, Destination, and Quantity columns. A destination marked Deferred means the operator chooses it by scanning when putting goods away.
7. Select tasks and click Add (N). If someone claimed some in the meantime, you see Skipped N tasks — they were claimed or started in the meantime. This is information, not an error.
8. Assign people: ⋮ → Assign workers. In Assign session to workers, choose names under Workers and click Save assignment. Leaving the field empty is deliberate; the session stays open to everyone.
9. Check progress with ⋮ → Open. The session view shows Total tasks, Completed, Remaining, and Quantity to move.
10. When the session is done, close it — see “Closing” below.

You can also create a session with tasks and workers already selected on the separate New replenishment session page. It additionally has Tasks (optional), Zone, Workers, and a Summary before saving.

Creating a session

Use Create session:

• Session name — required; operators identify the session by this name on the terminal.
• Warehouse (optional) — narrow it to one warehouse.
• Notes (optional).

Assigning workers

Assign workers — choose one or more people. Each sees the session on their terminal. The dialog explains: Choose one or more workers. Each will see this session in the kiosk. Leave empty = session open to everyone.

An empty assignment is not a mistake: the session is available to everyone. Assign it explicitly if a particular shift should do the work.

Adding tasks

Add tasks lists open, unassigned tasks with Number, Product, Source, Destination, and Quantity. A Deferred destination means the operator scans a shelf when putting goods away.

If someone claims some tasks in the meantime, the system reports how many: “Skipped N tasks — they were claimed or started in the meantime.” This is not an error; the list you saw has become stale.

Session detail view

The KPIs are Total tasks, Completed, Remaining, and Quantity to move.

Note: the last tile sums quantities from the current page of the task list, not the whole session. With a multi-page session, it will be lower than the total.

Closing — three different actions

All three are in the row’s ⋮ menu, but each appears only when relevant.

Delete session — only for a Scheduled session that has tasks. Confirmation: Session “NAME” has not started — deleting it will cancel the session and all its tasks. Continue?

Delete empty session — only when the session has no tasks. Confirmation: Delete empty session “NAME”?

Archive — only in the Collected group. Confirmation: Archive session “NAME”? Remaining open tasks will be closed as stale. The archive has its own tab next to Active.

A session completed without shortages archives itself. A session where someone reported a shortage waits for manual closure so the shortage does not disappear from view with the session. Manual archive requires archive_session permission.

Archiving is refused if a worker is picking a task; the server responds in English: “Cannot archive: a worker is mid-pick on one or more tasks; finish them or report a shortage first.” Finish those tasks or report the shortages first.