Mobile Inventory Capture and Device Allocations
- Stock and operations teams
- Updated
In this guide
20.1 Capture Is Not Posting
The native Inventory workspace follows the business's enabled modules and functional permissions. Synchronize the authorized catalog and location data while connected. Offline capture supports receiving, adjustment, transfer-request, and stock-count drafts. Review server quantities and pending drafts separately; a cached balance is labelled with its last synchronization time.
Uploading a draft does not change stock. An offline receipt is not added to sellable stock, an adjustment has not yet changed a balance, a transfer request has not shipped or received anything, and a count has not approved a variance. Submit explicitly online using the existing authorized workflow. Transfers retain separate create, ship, and receive stages; stock counts retain separate approval. Required batch or serial information and other unsupported controls must be handled through the supported online workflow.
20.2 Review and Submission
Use Sync Centre to upload saved drafts and see their server acknowledgement. Open the uploaded work item to check its product, location, quantity, cost, reason, and source reference before submitting. The server validates current permissions, module availability, stock policy, and fiscal controls. Resolve a stale stock count against intervening movements rather than overwrite the current balance.
If submission is interrupted, inspect the work item's status and original operation reference before trying again. A retry uses the same identity and must not duplicate a movement. Needs attention means review the stated reason. Never treat an upload success as proof that goods were received or a transfer was completed.
The app retains the server's submitted, needs-attention, or superseded status separately from upload status. A submitted count still requires approval, and a submitted transfer request still requires shipment and receipt. If access changes while connected, restricted stock quantities and locations are removed from the display without deleting saved drafts or paid receipts.
20.3 Allocations for Offline Selling
When negative stock is disabled, a prepared POS device reserves explicit quantities at its register location. These reservations cover individual products and every fixed-combo component. A component shared by a combo and a single product cannot be promised twice. Available quantities in web and mobile selling must respect these allocations; do not adjust on-hand stock to make a legitimate reservation disappear.
Allocations remain reserved after the offline grant expires until device reconciliation or audited manager-assisted recovery. Expiry prevents new offline sales but cannot prove whether the device already sold allocated stock. Managers must inspect the device's receipt and operation manifest before releasing uncertain quantities. Never release reservations automatically merely because a device is late, lost, or disconnected.
With Allow negative stock enabled, valid individual and combo sales follow that policy, while product validity, permissions, batch/serial controls, and supported tax rules remain mandatory. Uploaded warehouse drafts never increase a device's offline allocation.
20.4 Protect Pending Work
Pending drafts and paid sales are stored in an encrypted operational ledger, separate from the disposable catalog cache. Account or business switching must not carry private records into another workspace. Sign-out or an expired token must not erase pending work. Ask for authenticated recovery if access changes; do not clear app data or uninstall while records remain unsynchronized.
After reconciliation, compare submitted work items with stock movements and location balances. Where Accounting is enabled, review the configured integration; where it is disabled, Inventory continues without creating Accounting entries.