Office decision — four buttons and one pitfall
Accept and close, Reject, Skip, Cancel task. There is no separate adjustment button: enter corrected quantities and accept.
The task appears on the Stocktaking review screen with the Counted status. You can see the location, counting mode, and scenario; a summary bar (Expected, Counted, Difference, Difference value, Items with discrepancies); and a single Items table where shortages and overages appear together. The -n and +n chips in the card header show how many items are affected.
Step by step
- Open a task with the Verified status from the Stocktaking dashboard using Open in the row menu. The Stocktaking review screen opens.
- Read the summary bar and check that the difference is in the range you expect.
- Scroll to the Office notes card. Warnings that someone moved goods at this location after the count appear here; read them before deciding.
- Review the Items table. The WMS stock column counts only the warehouse that contains the counted location; clicking the number expands a list of other locations where the product is still stored.
- Need to correct a quantity? Enter it directly in the Counted column. There is no save confirmation—the card header shows Saving…, then Saved.
- To exclude an item from the adjustment, clear its WMS adjustment checkbox. To exclude it only from ERP documents, clear ERP adjustment.
- Make a decision with a button at the bottom of the screen: Accept and close, Reject, Skip, or Cancel task. Each opens a dialog that you confirm with Confirm.
- Reject and Cancel task require a reason. Until the field is filled, Confirm stays disabled.
- If the decision saved but the task did not close, a Close task button remains at the bottom. Click it; it acts immediately without a dialog and issues the documents.
- Do not trust this count? Instead of deciding, click Request recount. A new task is created for the same location, and the screen opens it immediately.
Buttons on the decision bar
| Button | What it does | Effect on stock |
|---|---|---|
| Accept and close | accepts the count and immediately closes the task | creates an adjustment; stock is brought in line with the count |
| Reject | “this count is no good” | no documents, stock remains untouched, location does not get a last-counted date |
| Skip | closes without resolving the discrepancy | no documents; task disappears from the queue |
| Cancel task | withdraws the task; requires a reason | no documents; an audit log entry is created |
When discrepancies exist, Request recount is also available. If a decision has already been saved, Close task appears too.
There is no “Adjust” button on this screen, although it was mentioned for a long time in articles and process documentation. An adjustment is not a separate decision: enter corrected values in Counted and confirm with Accept and close. The system records the decision as adjusted.
You cannot undo a decision by editing it
A second decision on the same task is rejected. There are three ways forward: request a recount, cancel the task, or reverse adjustments (currently only through the API; there is no button in the interface).
WMS stock counts only the warehouse for the location being counted
This is a common source of confusion. The WMS stock column shows only the warehouse containing the counted location. If one unit is in the main warehouse and another is in defects, the main warehouse count will not show “2”—correctly, because that would look like an overage.
The Show stock from all warehouses checkbox switches back to the aggregated view; the selection is remembered.
Clicking a number in this column shows the locations where the product is still stored, with quantities and a Flag for checking button next to each. A role without the warehouse module sees a permission message here, not an empty list.
This control is not available in blind counting. While a task is in progress in blind mode, stock is disabled and cannot be expanded. The cell shows a dash with an explanation.
Two checkboxes on each item
- With WMS adjustment cleared, the item is excluded from the adjustment and ERP documents.
- With ERP adjustment cleared, the item is included in the warehouse adjustment but excluded from ERP documents.
ERP is a subset of WMS: clearing the first checkbox removes the item from both. The ERP adjustment column appears only when the company generates ERP documents.
Batch for an overage
This applies only to warehouses using Full batch mode. The table then has a Batch column.
- Batch chip — the overage is assigned to this batch, or a shortage is deducted from it.
- Suggested — exactly one batch of this product is on the shelf. Unless you change it, the overage is assigned to that batch.
- Enter batch / Change batch — choose a batch already on the shelf, or enter details for a new batch: batch number, expiry date, and production date. Fields marked with an asterisk are required for this warehouse.
If you do not select or enter a batch and the shelf does not have exactly one batch, the overage is assigned to an unknown batch.
Decision rejected. If the adjustment cannot post the batch, Accept or Close task will fail. You will see a banner and the affected rows will be selected:
- “Fill in required batch fields in the selected rows” — enter the missing fields.
- “The adjustment cannot post the batch in the selected rows” — another batch of this product is on the shelf, and the warehouse does not mix batches. Choose the batch from the shelf.
The task stays where it was. After changing the batch, click the button again. After a decision (the task is waiting for closure), you can change only the batch, not quantities. After Reject, you cannot change the batch.
Auto-acceptance stops in this case too: the task waits for the office, and the notes include “Auto-acceptance paused.”
Two warnings worth reading
Movement during the count. If someone moves goods at the location between counting and closure, a warning is added to the notes. Read it before accepting an old count.
Request recount creates a new task for the same location, linked to the original. By default it must be done by a different operator. After it is finished, the task is marked matching / not matching compared with the original count. A recount does not refresh the “last counted” date.
Want to see this with your orders? We’ll show you NOXTI with your sales channels and warehouse.
Book a demo