Skip to content

Count Completion Goals screen ​

The Count Completion Goals dialog defines item lists by condition (count scopes) for a branch, so you can count part of the catalog and track in real time what has been counted and what is still missing.

Who sees it: Primary User · Co-Manager (scope management) · every counter sees the progress card

Used by modules: Counting

TL;DR

A scope = a name + filter conditions on catalog fields. Define scopes per branch from Branches, and the count page shows a progress card with coverage, missing items and variances against the ERP. Scopes never block scanning – they only track.

How to get here ​

  • On the phone: ☰ menu → Setup → Branches → in the branch row, the Count Completion Targets button (list icon)
  • On the computer: side menu → Setup → Branches → Count Completion Targets in the branch row
  • Also: the Edit Count Goals button on the progress card (managers only) on the Recent Counts screen and on the count page

The dialog opens with the title Count Completion Goals - «branch name». Each branch is managed separately.

What's on the screen ​

Count goals dialog for a branch with Add New Count Goal (1), Add Bulk Count Goals (2), the conditions badge on a row (3) and the edit and delete icons (4)

(1) Add New Count Goal ​

Opens the Create New Count Goal form.

(2) Add Bulk Count Goals ​

Opens Create Bulk Count Goals – one scope per unique value of a field.

(3) Scope list ​

ColumnWhat it shows
Count Goal NameThe name, with a dot in the scope's color
Filter ConditionsA N conditions badge, or All catalog items for a scope with no conditions
Creation DateWhen it was created
ActionsEdit Count Goal · Delete Count Goal

(4) Delete All Count Goals in Store ​

Deletes every scope in the branch after confirmation. See Dangerous actions.

Create New Count Goal ​

  1. Enter a Count Goal Name (required; the form's guideline is up to 80 characters).
  2. Pick a Count Goal Color. The color identifies the scope on the progress card.
  3. Under Filter Conditions, set each condition's Field, Operator and Value. The is empty and is not empty operators take no value.
  4. Optional: click Add Condition to Group for another condition in the same group, or Add Condition Group for a new group.
  5. Optional: click Test Conditions to see which items match before saving.
  6. Click Save Count Goal.

Inside a group every condition must hold (AND). Between groups you choose AND or OR. A scope with no conditions includes the entire catalog.

Fields and operators ​

FieldTypeOperators
Item Code, Item Description, Barcode, Supplier Name, Category, Sort Code, Color, Size, Model, Unit of MeasureTextequals · not equals · contains · not contains · starts with · ends with · is empty · is not empty
Cost Price, Selling PriceNumberequals · not equals · greater than · less than · greater or equal · less or equal · is empty · is not empty
Manually AddedYes/noequals · not equals
Quantity by ERPPer-branch quantityis not empty · is empty · equals · not equals · greater than · less than · greater or equal · less or equal

Test Conditions opens Condition Test Results – a table with item code, description, barcode, supplier, category and prices of the matching items. With no conditions, every item in the store is listed.

Create Bulk Count Goals ​

  1. Click Add Bulk Count Goals.
  2. Under Select Field to Create Count Goals By, pick Supplier Name, Category, Sort Code, Color or Size.
  3. Click Create Count Goals by Selected Field. One scope is created per unique value of the field in the catalog.

The message N count scopes created successfully also states how many values were skipped because of a duplicate name or an empty value.

The progress card ​

Once scopes exist for the branch, the card appears on the count page (in regular counting mode only) and on the Recent Counts screen.

Expanded scope progress card on the counting page: scope select (1), coverage gauge with the three counters (2), the tabs row (3) and the Close After Scan checkbox (4)

  • Select Count Goal (1) – the branch's scopes.
  • Metrics (2): Coverage in percent, Counted from Goal, Total in Goal, Out of Goal.
  • Tabs (3):
TabWhat it shows
Not Counted YetItems in the scope not scanned yet. Clicking an item puts it in the search field of the count page
Partially Counted - Variance ReportItems whose counted quantity differs from Quantity by ERP. Shown to managers and to users with the permission to view ERP quantity
Out of ScopeScans of items that are not in the selected scope
  • Close After Scan (4) – collapses the card to slim mode after every scan. Slim mode keeps the scope name and the coverage bar; Expand Details opens it again.
  • Refresh Data – reloads. The card also refreshes after every successful scan.

Export by scope ​

In the Download Inventory Count Summary File dialog (the Export Count Summary Data File button on Recent Counts), the Count Scope: field appears after you pick a store. Choose a scope so the file includes only its items; the default is All - No Scope Filter.

Good to know ​

  • Scopes do not restrict scanning. A counter can scan any item; the card only reports.
  • An item added to the catalog after the scope was created joins it automatically if it matches the conditions.
  • When scopes exist, Overview shows the Counting Scope group with Scope coverage, Out of scope and Progress by scope.

Dangerous actions ​

Irreversible

Delete All Count Goals in Store removes every scope in the branch after confirmation. Delete Count Goal removes one scope. The scans themselves are not deleted.