Managing Cycle Count as a Store Manager

If you are a store manager, you can use manager-specific views in Point of Sale CMS to oversee store associate counts, manage and edit batches, and view product statuses to efficiently monitor and maintain accurate inventory.

Manager View

As a store manger, you are expected to oversee associate counts and batches. You have access to the Manager View, which allows you to see all open or created batches and view products and their statuses. You can flag items for recounts and also complete cycle counts.

Batches are the first selection under Batches, To view products, tap Batches on the top right, then turni on Products at the bottom of the screen.

Product View

If a cycle count is started, all items are under the tab Uncounted with the expected amount. This amount is the QTYOH (quantity on hand) of the item at the initial start of the cycle count.

Warning
Warning

Don’t start Cycle counts if the store is open (open till) or if there are any inventory transactions (for example, Store to Store, Return to Vendor, or Advanced Shipping Notice).

Excluding Items from the Cycle Count

As a store manager, you can review the items in the cycle count and exclude any items that shouldn’t be counted (for example items not yet received or carried by the store). This revision won’t affect the cycle count. By selecting the delete icon, you can mark an item as an excluded product, selecting a reason code for the exclusion. You can bring excluded items back into the cycle count by selecting Put Back for the item.

Product Tab Information

The product page contains three tabs:

  • Uncounted: Displays products in the cycle count that haven’t been counted yet, along with their expected quantities.
  • Unmatched: Displays products that have been scanned at least once but have a discrepancy between the scanned count and the expected quantity; as well as unit difference and cost variance (cost = retail price).
  • Matched: Displays products that have been scanned, and the scanned quantity matches the expected quantity (excluding items with a quantity of zero).

Recounts

In case of large discrepancies, you can initiate a recount for an item by selecting Recount on the unmatched item line

Confirming the recount zeros out the item’s quantity and moves it back to the Uncounted tab. The number before the recount isn’t recorded. Recounted items accumulate the number of recounts and show them in the unmatched or matched tab for that item.

Batches

As a store manager, you can create, open, and close batches on the app. Associates can always resume a batch even if closed by a manager. You can also monitor batch status (In Progress or Closed) as well as view batch items and quantities. If the batch is Closed (batch closed by user), you can view the items, including their quantities, and scan other items if needed.

Editing Batches

As a store manager, you can edit batches with an approval configuration set for Cycle Count Batches Actions. Associates with manager credentials can edit batches. In Edit mode, you can adjust the counted quantity of a nonserialized item and delete any serialized items.

Batches - In Progress

Starting in app build 9.4.1, as a store manager, you can access and close a batch that is In Progress (batch is active or scanning) that was initiated by other managers or associates. You can’t edit a batch (for example by adding items, or making alterationsn) other than your own.

Associates must have their approval configuration set for:

  • Cycle Count Batches (governs ability for user to have permission to close the batch)
  • Cycle Count Batches Actions (governs whether the user can see other users’ batches)

As a store manager, you don’t need the approvals, since you have the ability to use this functionality out-of-the-box.

In the app, UI enhancements (app build 9.4.1) allow you to distinguish between you own batches and those belonging to others. If you intend to close a batch that is currently In Progress, wait for a confirmation prompt before proceeding.

Known Issues & Restrictions

If a manager closes a batch that an associate had opened, any scanned items in that batch that weren’t saved to the database are lost.

For example, if an associate reopens a closed batch with five units, and then scans two more units for a total of seven, only the five units are saved after the manager closes the batch. However, if the associate closes the batch after adding the extra items, all the items, including the newly scanned ones, are saved to the database. This results in seven units for the batch.

Pausing the batch also saves the items to the database, and you have the option to close a paused batch. If an associate resumes a paused batch and adds more items to it before closing, those additional items are included in the batch.