HomeSolutionsAboutDocumentation

Understand offline work and scanner recovery

Stock Scan distinguishes work saved on the phone from work applied by the server. Use the saved-work and activity views to establish what happened before repeating a receipt, count or movement after a connection problem.

A recognized barcode, a saved quantity and an applied inventory change are different results. Some work can be captured locally, but completing a count or receipt requires current server confirmation of the earlier steps. Other actions require a current connection before they can be submitted.

Read the status before acting

Open the work item and inspect its individual steps as well as the overall result.

Status Meaning and next action
Captured on this device The action is saved locally. Reconnect and let Stock Scan check and upload it; inventory posting is not yet confirmed.
Processing The server has the action and is applying it. Wait for the result rather than entering it again.
Waiting for earlier work An earlier step must finish first. Inspect that step for a connection problem or refusal.
Applied The server has confirmed this action. Check which step the label belongs to: an applied opening step is not a completed receipt or count.
Needs review The uploaded action needs attention before it can be applied. Read the reason and resolve it through the relevant workflow.
Could not apply The server refused this action. It did not apply that action; earlier actions in the same workflow may still have applied.

Showing a saved copy — reconnect to confirm means the display is not current server evidence. A previously saved Applied label cannot by itself establish the latest state of an interrupted job.

The workflow-level results Count applied and Receipt applied confirm the respective finishing actions. Afterward, use Activity and the original Zapstra Inventory Management records to inspect the recorded result.

Prepare before working in a weak-signal area

  1. Connect the phone and open Stock Scan Home.
  2. Select the warehouse where you will work. Check that the expected materials, bins and available work can be read.
  3. Open Stock and review Offline readiness. Use Preload declared stock scope when available, and wait for its result.
  4. Read that result literally. Cache warmed means data has been saved; it is not the same as Offline ready. An incomplete or failed preload does not prove the warehouse is ready for every offline task.
  5. Open the intended work while connected and check its instructions and availability before moving to the floor.

Saved data may cover only part of a warehouse. Not available offline or incomplete barcode coverage does not mean the item is unknown to Zapstra Inventory Management. Reconnect to check it. A missing stock row also does not mean there is zero stock.

Do not assume preloading removes an action's online requirements. Count and receipt completion wait for fresh confirmation of earlier saved actions. Movement submission can be unavailable while its data is stale. A new receiving work list or barcode check may also require a connection.

Recover an interrupted workflow

  1. Restore connectivity and keep Stock Scan open long enough to read its current status.
  2. On Home, find the original job under the available continuation or parked-work sections. Alternatively, open Activity, then Pending on this device, and select Open saved-work recovery for the matching item.
  3. Match the warehouse, document or count reference, and saved quantities. Open the original work instead of starting an equivalent new job.
  4. If the status is Checking saved work, allow the check to finish. If the screen offers Try again for an unreadable view, use it to refresh that view.
  5. Follow the offered continuation. If earlier steps are still processing, wait. If the job needs attention, read the specific reason before taking further action.
  6. Confirm the final outcome in the workflow and Activity. For receiving or transfers, also inspect the original order or transfer in Zapstra Inventory Management before reporting completion.

For example, if you captured receipt of 48 each of Kraft mailer (MAILER-KR6) and the connection dropped, do not enter another 48 each merely because the completion screen did not load. First inspect the saved receipt and the purchase order's receipt history. Continue only the unfinished step of that delivery.

Resume, set aside or remove saved work

Use Suspend and keep my place when leaving a workflow that you intend to continue. When recovery offers Set this job aside, it releases the scanner for other work and keeps the saved evidence. Setting aside is not a cancellation or an inventory reversal.

A count interrupted by a changed scanner session may offer Resume this count. Review the displayed count reference and number of saved lines. Send and finish count sends those reviewed totals and finishes that count; it does not ask you to count the goods again. If the message says the count was sent but the old job is still held, set the old job aside rather than sending it again.

Read every abandonment or removal confirmation. Depending on the workflow and its state, Abandon… can cancel an unfinished count or receipt, discard unsent staged work, or close the local view while retaining captured evidence. Remove from this scanner can permanently discard observations that exist only on that phone. Clear this item clears saved attention after reconciliation; it does not undo recorded inventory work.

When to return to Zapstra Inventory Management

Ask an owner or admin to check scanner access and the shop connection if access, session or warehouse warnings persist. Fix blocked or retired barcodes and missing unit or pack information in units and barcodes.

For an unresolved refusal, a count that needs review, or inconsistent results, preserve the saved job and use Support. Include the workflow reference, warehouse, time, expected quantity and visible message. Do not include activation QR codes or activation links.

See counting stock for count-specific completion and cancellation, or Stock Scan workflows for receiving and movements.