Where counting rules come from

Rules cascade from top to bottom, and the later setting wins:

default settings
  → company settings
    → warehouse default scenario
      → session scenario
        → task scenario
          → session mode override
            → task mode override

An empty value at a higher level means “inherit,” not “off.” This is the most common configuration misunderstanding.

Step by step

Set rules for the whole company

1. Go to Settings → Warehouse → Stocktaking.
2. Go through the sections: Counting mode, Lock location during stocktaking, Automatic discrepancy acceptance, Multi-level approval, Recurring counting (ABC), Price source for discrepancy values, ERP document generation, and Task numbering.
3. Under Counting mode, choose With quantity preview or Blind (no preview).
4. Under Lock location during stocktaking, choose Full lock or Warning only.
5. Under Automatic discrepancy acceptance, set Difference threshold (units), Difference value threshold, and Difference threshold (%). An empty field means that threshold is inactive.
6. If you use the value threshold or choose 2 levels (office + manager), set the Price source first. Without it, discrepancy values are always zero and the threshold never applies.
7. Click Save and confirm with a fresh 2FA code. Without this step, nothing is saved.

Create a warehouse scenario

1. Go to Settings → Warehouse → Stocktaking scenarios. The list shows the warehouse, counting mode, manual-quantity threshold, auto-approval, and number of custom rules (fields set in the scenario instead of inherited). Search by name, filter by warehouse, or use the flag icon to show defaults only.
2. Click New scenario (or click a row). The editor fills the screen, and a sentence at the top summarizes the scenario — click an underlined phrase to jump to its field. The page address identifies the scenario and tab, so you can share the link.
3. On Where it applies, choose a Warehouse and enable Default for warehouse if operators should receive it automatically. There can be only one default per warehouse — if one already exists, the toggle is disabled and shows which scenario is the default, with a link. The inheritance steps show where the rules come from, and Check warehouse tells you which scenario a count will receive in the selected warehouse when no one specifies one.
4. On Counting, configure counting mode (the With quantity preview / Blind cards), Quantity keypad from (or no limit), Undo scan, Mark location empty, Task after location scan, Location lock, and Tasks at once.
5. On Approval, configure Automatically approve when matched, Skip summary screen, and the three discrepancy thresholds (units and currency and percentage — a task auto-approves only if it stays within every threshold set). The example beneath the thresholds updates live: for expected 40 and counted 38, will the task auto-approve or go to the office?
6. Company-inherited rules appear as a grey locked toggle or an empty field with a building icon (hover to see the company value). A change gets a custom badge; the arrow beside it returns to the company setting. Note: a non-default scenario assigned to a warehouse that has a default scenario inherits empty fields from that warehouse default first — a blue box above the tabs explains this.
7. Click Save and confirm with a fresh 2FA code.

Override the mode for one session or task

1. For a session, go to Warehouse and logistics → Stocktaking → New session, then use Counting mode (session override) to choose Inherit from scenario, Informed (with hints), or Blind (no hints).
2. For a task, open Stocktaking review. The header shows Mode: Informed, Mode: Blind, or Mode: inherit from session; next to it is a scenario selector with the Scenario (inherit from session) hint.
3. Change the value. Confirmation says Counting mode updated or Scenario updated. Without permission, you will see Could not change the counting mode for this task.

Operator says a control is missing

1. “I can’t enter a quantity” → check Quantity keypad from in the scenario’s Counting tab. The pencil by an item appears only from this quantity.
2. “There is no Empty button” → check Mark location empty.
3. “I can’t undo a scan” → check Undo scan.
4. “Scanning a shelf does not create a task” → check Task after location scan.
5. Check settings in this order: task scenario → session scenario → warehouse default scenario. The lowest applicable one wins.

What you configure at company level

Saving settings requires a fresh 2FA confirmation.

Blind counting

In blind mode, the operator cannot see expected quantities and counts what is actually there. This is more reliable when manipulation is suspected because the operator cannot “adjust” the count to match the expected figure.

Scenarios — controls unavailable at company level

A scenario can be assigned to a warehouse as its default (one per warehouse; an operator scanning a location receives it automatically) or left unassigned for manual selection.

In addition to mode and threshold overrides, a scenario contains four settings available only here:

Location lock on a scenario is also saved, but currently only the company setting enforces a lock.

If an operator says “I can’t enter a quantity” or “there’s no Empty button,” this is where the setting was configured.