Skip to main content

Counting on the Mobile App

Count locations and SKUs in the Logiwa IO mobile app, handle prompts and damaged products, and complete the count or update inventory on the device.

Overview

Operators do the physical count in the Count module of the Logiwa IO mobile app.

In a Location Count you count all inventory in a location. In a SKU Count you count one SKU in every location where it is stored. The job type decides how you enter quantities and which details the app asks for.

Jobs are created from a count plan (see Creating and Cancelling Count Jobs). After the count, a supervisor reviews the results and updates inventory (see Reviewing Counts and Updating Inventory). For the full process, see A Guide to Managing and Executing Cycle Counts. For Instant Count, see Using Instant Count on the Mobile App.

When to use it

  • Count a job assigned to you or picked from the Job Pool.

  • Count all inventory in a location (Location Count) or one SKU in every location where it is stored (SKU Count).

  • Report damaged products you find during the count.

  • Update inventory for a location right after counting it, if your role allows it.

Prerequisites

  • A count job, assigned to you or in the Job Pool (see Creating and Cancelling Count Jobs).

  • To update inventory on mobile, the Complete Count & Update Inventory permission under Mobile - Count.

  • Damage reasons set up in the Data Setup screen, if operators report damaged products.

  • Optional: One by One Count or Attribute Auto-Fill turned on in the job type, if you want those counting options (see Create a Job Type for a Cycle Count).


Select a count job

  1. On the home screen, tap Count.

  2. Find the job under Your Jobs (assigned to you) or Job Pool (unassigned).

  3. Tap the job to start counting.


Location Count

In a Location Count job, the app sends you to a location and you count all inventory in it.

  1. At the location, scan its barcode. The Location Detail screen opens.

  2. Choose Count Products on an LP for items in a container with an LP (license plate) barcode, such as a pallet or tote, or Count Products without LP for items stored loose on a shelf or bin.

On an LP:

  1. Scan the LP barcode.

  2. Scan the product barcode on that LP.

  3. Enter the counted quantity and confirm.

  4. Repeat for the other products on the LP.

  5. Tap Complete LP. You must do this to finalize the LP's count.

Without LP:

  1. Scan the product barcode.

  2. Enter the counted quantity and confirm.

When all items and LPs in the location are counted, tap Complete Location Count. The task for this location is finished and the app moves to the next location. If your role allows it, you can tap Complete Count & Update Inventory instead (see "Complete the count and update inventory on mobile").

A completed location can't receive more counts in the same job. To start over before completing it, tap Reset Location Count. In a Cycle Count, reset doesn't reopen a location that is already in Count Completed; create a recount instead (see Creating and Managing a Recount). In an Instant Count, reset also reverts completed locations whose inventory hasn't been updated yet (see Using Instant Count on the Mobile App).

💡 Scanning an LP you already counted in this location opens a bottom sheet. In a Location Count, Reset Count for This LP clears the LP's counts so you can count it again. In a SKU Count, the sheet "This LP has already been counted in this job" offers Reset LP Count (clears all counted data for the LP and restarts from zero) or Continue Counting (keeps the previous counts so you can add more products to the LP). Tapping outside the sheet or going back closes it without changing the LP's counts.

Some LPs can't be counted in a location. See "Rules that can block a count" below.


SKU Count

In a SKU Count job, the app sends you to count one SKU in every location where it is stored.

  1. Check the SKU and the first Location shown by the app.

  2. Scan the location barcode. You can't scan a location that isn't part of the task.

  3. Scan the product barcode. If the product isn't part of the task, the app shows "Scan the product in task".

  4. Choose Count Products on an LP or Count Products without LP and count as in a Location Count.

  5. When the SKU is counted in this location, the app sends you to the next location, until the SKU is counted everywhere.

Each SKU is completed separately in each location: when several SKUs of the plan share a location, completing SKU-A there doesn't close SKU-B. If you enter a quantity for the same SKU and location more than once before completing it, the last value replaces the earlier one.

LPs with several products. After you confirm a product on an LP, Complete LP completes only that product. The other products keep their status, and the LP counts as fully counted only when every product on it is completed. Reset LP Count clears the counts of all products on the LP, including completed ones. Any error is shown on the product screen so you can retry.


Prompts after scanning a product

After a product scan, the app may ask for more details before you enter the quantity.

Several products share the barcode (for the same or different clients). Select the product in the bottom sheet. Each entry shows SKU - Client Name, and you can search the list by SKU. If only one product matches, it is selected automatically.

Several pack types share the barcode. Select the pack type, for example Each or Case. If a barcode matches several products and several pack types, you always select the product first, then the pack type.

Lot, expiry or production date. For a product tracked by these attributes, you must provide them before you enter the quantity. Counts are blind, so Logiwa IO needs to know exactly which inventory you are counting. You don't always have to type them:

  • Attribute Auto-Fill: if the job type has it on and the product's inventory at the location or LP has a single combination of attributes, the values are pre-filled. Check them and edit only if needed. See Auto-Fill Tracking Attributes During Count.

  • Barcode parsing: with an active barcode template, scanning the product barcode can fill in the lot, expiry date and production date. A value read from the barcode takes priority over an auto-filled value. LP barcodes are not parsed. See GS1 and Custom Barcode Parsing.

  • Lot numbers are matched to existing inventory regardless of upper or lower case ("abc-123" matches "ABC-123"), so the existing inventory row keeps its PO Number and Receiving Date.


Report damaged products

  1. After scanning the product, tap the three-dots menu.

  2. Tap Report Damaged Product.

  3. Enter the damaged quantity and select a Damage Reason. Damage reasons are set up in the Data Setup screen.

  4. Confirm. The damage is recorded and the supervisor sees it during review.

In One by One Count: use the Mark as Damaged option on the counting screen. A bottom sheet opens with an empty Product field (scan or enter the barcode or SKU), Quantity, Damage Reason and a Report button. Scanning a product in this sheet doesn't add to the one-by-one count. When counting on an LP, scan the LP first. In a SKU Count, you can't report damage for a product that isn't part of the plan.


Quantity entry: Standard vs. One-by-One

The job type decides how you enter the quantity.

Mode

How you enter the quantity

Standard Count

After the product, pack type and attributes are selected, enter the total counted quantity.

One-by-One Count (One by One Count on in the job type)

Scan each unit. Every scan adds one to the Scanning Counter; scanning a case barcode counts one case.

In One-by-One Count, an attribute-tracked product shows a Confirm Attributes sheet after each scan. With Attribute Auto-Fill on and unique attributes, you can lock the pre-filled attributes so later scans of the same product skip the sheet, until you scan a different product or tap Ask for Attributes on Next Scan. The lock is kept on the device only and is cleared when you leave the job. See Auto-Fill Tracking Attributes During Count.


Complete the count and update inventory on mobile

In a Location Count, an authorized operator can update inventory for a location right after counting it, without waiting for a supervisor.

  1. Count the location.

  2. Tap Complete Count & Update Inventory (shown on some devices as Complete Loc. Count & Update Inv.).

  3. Confirm in the attention bottom sheet. Optional: check Don't show this message again until this count job is complete to skip it for the rest of the current job; it appears again in the next job.

  4. If Mandatory Adjustment Reason for Cycle Count Updates is on and there is a quantity difference, select a reason. If you skip the reason selection, only the count is completed and inventory is not updated. See Mandatory Adjustment Reason for Inventory Operations.

Only the location you just counted is updated; other locations in the plan are not affected. Results are visible on the Location Details screen.

Permission. The Complete Count & Update Inventory permission is under Mobile - Count on the role access screen. Users with both permissions see both buttons; users with only one permission see only that button.

⚠️ If the counted quantity is lower than the quantity allocated in the location, the count is completed but the inventory update fails. The line stays in Count Completed for a supervisor to review.

When

What you see

More locations are left in the job

A green toast confirms the result and the Scan or Enter Location screen opens. If the count succeeded but the inventory update failed, the green toast is followed by a red toast: "Inventory update failed. Please contact your supervisor."

It was the last location in the job

The job is completed and a Congratulations sheet opens: "<Job code> and <Count plan code> completed successfully." Below it, one status box shows the inventory result: "Inventory updated successfully.", "Inventory update failed. Please contact your supervisor." or "Inventory records were not updated as the adjustment reason was skipped." Tap Select Another Job to continue with another count job, or Homepage to return to the home screen.


Rules that can block a count

Rule

What happens

LP has inventory in another location

"Scanned LP Number contains inventory in another location." The message tells you to count the LP in its registered location, or to transfer it to the location you are counting first.

Empty LP registered to another location

It can be counted, and it is moved to the counted location.

LP already counted in another location of the same plan

An LP can be counted in only one location per plan: "This License Plate {LP} has already been counted in {Location} for this count plan. Please scan a different LP." The same LP can be counted again in a different count plan.

Product not in the SKU Count task

"Scan the product in task". Only products in the task can be counted.

SKU already completed in the location

Counting it again in that location is rejected.

Location already completed in the job

It can't receive more counts in the same job (see "Location Count").

Task cancelled on the web

The task is removed from the mobile job and can't be submitted.


Common questions

Why was the LP I scanned rejected? Either the LP has inventory in another location, or it was already counted in another location of the same count plan. See "Rules that can block a count" above.

An operator says a task disappeared or can't be submitted. Why? The line was cancelled on the web, or a supervisor used Update Inv. on the Count Plan screen, which cancels lines that were not counted. Cancelled tasks are removed from the mobile job and can't be submitted.

The count was completed on mobile but inventory wasn't updated. What now? The line stays in Count Completed. A common cause is a counted quantity below the allocated quantity in the location. A supervisor can review the line on the Location Details screen and decide how to proceed, for example create a recount (see Creating and Managing a Recount).

Can I count a completed location again? Not in the same job, and in a Cycle Count Reset Location Count doesn't reopen it. Create a recount instead: see Creating and Managing a Recount.

Did this answer your question?