Docs
Open Moduvio
Supply & inventory

6. Cycle counts and offline handheld work

Govern recurring risk-based counts, then test blind execution, movement freezes, offline idempotency and human conflict handling.

Purpose

Govern recurring risk-based counts, then test blind execution, movement freezes, offline idempotency and human conflict handling.

Roles

Stores Officer, Stores Supervisor

Example

Policy CCP-2608-A for MAIN-01 every 30 days; first count 9, independent recount 10; handheld device COMRADO-HH-07.

Before you begin

  • Accountable stock exists
  • Three distinct active users cover the assigned first-count, recount and approval roles at the site and classification
  • PWA has been opened once while online

Field guide

Policy scope

Choose one controlled location or a site location-type group. The classification ceiling prevents the policy from silently scheduling stock above its authority.

Cadence and dates

Cadence is recorded in days with effective-from/effective-to bounds. Reminder and escalation windows drive DUE SOON, OVERDUE and ESCALATED status without changing stock.

Independent roles

First count, recount and variance approval require three distinct roles and, at activation, three distinct active users with the required site scope and clearance.

Policy states

A new policy is DRAFT. A different planner activates it; pause/resume affects future scheduling only, while retirement is final. Existing plans and evidence are retained.

Due scheduler

The hourly scheduler and controlled run endpoint lock each due policy, create at most one plan for each policy/location/due date, skip locations without accountable stock and leave a blocked policy due when another freeze or higher classification prevents safe scheduling.

Procedure

  1. 1

    Save the policy as a draft and confirm no count plan or freeze exists.

  2. 2

    Have a different authorised planner activate it after reviewing scope, cadence, classification and eligible-role coverage.

  3. 3

    When the policy is due, confirm one policy-linked plan snapshots and freezes the location; a repeated scheduler run must not duplicate it.

  4. 4

    Count offline in the assigned first-count role and confirm no system quantity or previous count is shown.

  5. 5

    Reconnect and sync the same intent twice.

  6. 6

    For a variance, perform a different-user recount in the assigned role and third-person approval; inspect any conflict in the queue.

  7. 7

    Pause or retire the policy and prove existing plan and audit evidence remain unchanged.

Expected result

  • Draft and activation alone create no inventory effect or freeze
  • Overlapping active policy scopes and active location freezes are rejected
  • Frozen stock cannot move
  • Duplicate scheduling and offline replay create no duplicate ledger effects
  • First counter, recount counter and approver role plus user separation is enforced
  • Only approved variance evidence posts an adjustment
  • Conflicts are never silently resolved

Documentation version 2026.09

Last reviewed August 2026