How to run a barcode stock count

Use barcodes to count faster and reduce errors, but decide the no-read route before counters leave for the floor.

Use this workflow when items already have 1D, GS1 2D, Digital Link, or SSCC labels, and keep a manual-count exception path ready for damaged, missing, duplicate, or mismatched labels.

Issue a device-readiness release roster

Local-only review CSV

Import one row per phone or scanner. Every unique device stays on hold until its counter assignment and six release checks pass.

Choose a device roster CSV or load the sample.

Ready
0
Hold
0
Duplicates
0
Rejected
0
Over limit
0

Roster decision

Release holds remain

Load a roster to prove which devices may be released.

Device release preview

0

Accepted device rows will appear here.

Need item and label checks too?Open the barcode CSV readiness checker.

Barcode check

Check your barcode list

Paste or upload a CSV to catch missing IDs, duplicate barcodes, GTIN errors, bad locations, print-readiness gaps, and GS1 2D or SSCC mismatches before counters scan. Keep clean rows moving and send proof exports to owners when needed.

Delimiter: , GTIN checked: 0 Readiness score: 0/100

80+ is ready; below 80 needs review. GTIN, location, collision, quantity, GS1 2D syntax, row-match, and SSCC checks stay in the exports.

Import requirements

Keep count-pack columns in the import

Run the barcode check before scanning, but do not strip fields that supervisors need after the count.

Batch and scope
Keep the assignment batch or count scope so the variance reviewer can group follow-up work.
Counter and location
Keep assigned counter, location, bin, or aisle fields so rows trace back to the person and place counted.
Label durability
Replace worn rack or bin labels. Keep one full-height, high-contrast scanner-readable label with quiet zones, edge clearance, and a smooth glare-free scan surface.
Cycle handoff
Keep bin-first scan proof, count attempt policy, reason-code prompt, pending-review owner, and release status with the scan-proof export.
Quantity and evidence
Keep expected quantity, reason, location confirmation, counter sign-off, and supervisor review columns for the count pack.
2D barcode data
Keep lot, date, serial, count, weight, element-string, scanner-output, and Digital Link fields when labels need QR, Data Matrix, or SSCC data; the 2D audit checks decoded values before label work.

The import CSV keeps source values exact. Use the spreadsheet-safe CSV when people will open clean rows in spreadsheet software.

Spreadsheet, audit, proof, print, and SSCC exports

Preview (0 rows)

    0 rows loaded

    What to prepare

    Confirm your item list before the count window opens. Missing, duplicate, damaged, or mismatched barcode data is easier to fix before people are standing in aisles.

    • SKU and expected quantity when available
    • 1D barcode, GS1 2D, Digital Link, or SSCC for scannable rows
    • Location or bin label
    • Quiet zone and human-readable text checked on sample labels
    • Manual-count route for no-read rows
    • Repair ticket or reprint owner

    Count workflow

    Lock or pause inventory transactions, count one location at a time, scan each item on the target device, then confirm quantity before moving on.

    • Prepare devices and count sheets
    • Test one location, one item, and one 2D or SSCC sample when used
    • Scan the item, not the shelf label
    • Stop after a failed scan instead of typing from memory
    • Enter quantity from the physical count
    • Submit and review variances

    No-read fallback

    When a barcode is damaged, missing, duplicated, mismatched, or rejected by the device, keep the row out of normal scanner release until the fallback is documented.

    • Capture the label photo or failed device result
    • Use the approved manual-count exception row
    • Attach label source data, 2D audit, SSCC packet, or repair ticket
    • Print the replacement label or accept the manual route
    • Record the re-scan pass or fail result

    Variance review

    Focus on differences first. Recount the rows with variance, then research receipts, issues, transfers, damages, no-read exceptions, and location errors.

    • Positive variance means found stock
    • Negative variance means missing stock
    • Reason codes help later analysis
    • No-read, 2D, and SSCC proof should travel with the count pack

    Printable scanner rollout SOP checklist

    Print this checklist before releasing barcode scanners to counters. It keeps device fit, label readiness, 2D or SSCC samples, offline fallback, pilot metrics, exception handling, and sign-off evidence together.

    Before counters start

    • Record each zone device ID or friendly name. Confirm its OS and count app are supported and current, then test battery, case, camera, and login at the shelf.
    • Test one item barcode, one location label, one GS1 2D or SSCC sample when used, one damaged label, and one duplicate/no-read row on the target device.
    • Confirm the barcode readiness checker issue CSV has owners for missing SKUs, duplicate barcodes, label damage, Digital Link mismatches, SSCC packet gaps, and repair tickets.
    • Check quiet zones, human-readable text, label placement, scanner position, and warehouse lighting on the sample labels.
    • Document the offline fallback rule before counters leave for bins with weak connectivity.

    Pilot and go-live

    • Run a small pilot batch and record first-scan success, average scan time, duplicate warnings, no-read exceptions, and offline sync result.
    • Train counters to stop after failed scans instead of typing from memory, then use the approved manual-count exception route.
    • Release scanners only after pilot blockers, 2D row mismatches, SSCC packet gaps, and no-read rows have an owner, repair ticket, or supervisor acceptance.
    • Keep a printed or downloaded scan-proof packet with the count pack.

    After the count

    • Export clean counts, issue rows, scan-proof evidence, and variance review results before posting adjustments.
    • Close replacement-label, Digital Link, SSCC packet, repair-ticket, and re-scan proof rows before the next scanner session.
    • Review repeated no-read, duplicate, device, and location failures by zone so the next count starts cleaner.
    • File the signed SOP with the variance review CSV and any barcode readiness audit.

    Scanner rollout sign-off

    Count zone Device owner Pilot batch Offline fallback No-read route 2D/SSCC sample Supervisor

    Use this checklist with the barcode readiness checker exports so scanner release, 2D or SSCC samples, no-read exceptions, offline fallback, pilot metrics, and variance handoff are documented before inventory adjustments are posted.

    Continue mobile counts with Mobile Inventory.

    Workflow

    Step Action Details
    Step1 ActionPrepare DetailsLock transactions, print lists, charge devices, verify sample 2D or SSCC labels when used, and name the no-read route.
    Step2 ActionScan DetailsScan the location and item, then stop failed scans or 2D mismatches before manual entry.
    Step3 ActionConfirm DetailsReview the on-screen quantity or save the approved manual exception.
    Step4 ActionMove DetailsProceed to the next location on your list.
    Step5 ActionSubmit DetailsSubmit the count, repair proof, 2D or SSCC audit rows, and no-read rows for variance review.

    Stock count glossary

    SKU

    A stock keeping unit: the internal item code used to identify one product or variant.

    Barcode

    A scannable code such as UPC, EAN, or GTIN that should point to one item or package.

    Variance

    The difference between expected quantity and counted quantity after a stock count.

    Cycle count

    A recurring count of selected items, locations, or categories instead of the whole inventory.

    Blind count

    A count where counters do not see the expected quantity while entering the physical quantity.

    Cutoff time

    The point when stock movements are paused or controlled so the count matches system data.

    Download tools

    Stock count template Editable worksheet for counts and variances. Barcode readiness checker Check whether your item list is ready to scan. Variance reviewer Classify recount and approval rows after counting.

    FAQ

    Do I need barcodes to run a stock count?

    No. You can count with SKU or product name, but barcodes usually reduce lookup and typing errors.

    What should I do with duplicate barcodes?

    Fix duplicates before the count. A barcode should identify one item or one package configuration, and duplicate rows should stay out of scanner release until the correct label or pack-size rule is documented.

    What if a barcode is damaged or missing during the count?

    Use the manual-count exception route instead of typing from memory. Capture the failed scan or label photo, assign a repair ticket, print a replacement label when possible, and record the re-scan result before closing the count pack.

    Do I need to test GS1 2D or SSCC labels before release?

    Yes, when those labels will be scanned. Test at least one printed 2D or SSCC sample on the target device, confirm the Digital Link or SSCC row matches the CSV, and keep quiet-zone, lighting, and re-scan proof with the count pack.

    Can I use a phone for barcode stock counts?

    Yes. Mobile Inventory supports phone-based scanning for practical stock count workflows. Test one item, one location, one no-read exception, and any 2D or SSCC sample on the target device before releasing the session.

    Related stock count tools

    Barcode readiness checker Find scan blockers and hand row-level fixes to the right owner. Stock count variance reviewer Prioritize recount, approval, evidence, and posting-hold actions. Free stock count template for Excel, CSV, and print Build a count-ready CSV, Excel worksheet, or printable sheet. Stock count app with barcode scanning Move prepared stock lists into phone-based barcode and offline counting. Cycle counting template and workflow Plan repeatable location or item counts with review-ready assignments.