Define the movement before adding the scan.

Item identity

• What distinguishes a product quantity from an individual asset?
• Which identifier remains stable if its description changes?
• How are damaged labels or unknown items handled?

Movement and custody

• Which actions change quantity, location or responsibility?
• Is a transfer complete at dispatch or confirmed receipt?
• Who resolves an item that is still in transit?

Counts and corrections

• Who performs a physical count and approves a difference?
• What reason and history accompany an adjustment?
• How are damaged or unavailable items distinguished from missing stock?

A fictional acceptance example

Transfer tool T-12 from store A to crew B. Check that dispatch and receipt remain distinguishable, a repeated scan does not repeat the movement, and a failed save gives a clear result. Confirm that authorized staff can find its current custody and history.

Can the system work offline?

That needs a specific design. Agree which actions may be recorded without a connection and how conflicts are resolved later. A cached screen alone does not establish that a movement was stored.