Illustrative photo: Indian supervisor crouching at a shrink-wrapped pallet, counting the cartons by hand with a phone in the other hand, headline Stock short? Recount, then approve, with the fictional example book 100, counted 94, recount.
AI-generated illustrative photo of an Indian supervisor physically rechecking a wrapped pallet, with Inveck headline and label graphics added. Not an Inveck customer site or product screen.

When to Send a Stock Variance Back for Recount, and When to Approve It

A variance in a stock count is a question, not a verdict. The book says one quantity and the floor says another. Before anyone changes the books, the team has to decide whether the physical count is right, the record is wrong, or the count itself needs to be repeated.

This article gives a practical way to make that decision, and describes how recounts and approvals fit into a count. The product details come from Inveck’s public Recount and Approvals page.[1]

Start by reading the variance, not the total

A single net figure can hide a lot. A shortage in one bin and an excess in the next may cancel out, so the total looks calm while two locations are wrong. Look at variances by item, category and location, and look at the value impact, not only the quantity. Inveck’s page describes shortages, excess and value impact shown by item, category and location, so approvers decide with the full picture.[1]

It also describes counters seeing excess and shortage quantities and values on the device before they submit, so that anything that does not look right can go back for a recount while the team is still on the floor.[1] Timing matters. A recount done the same day, with the team in the aisle, is far cheaper than one requested after everyone has gone home.

When to send it back for a recount

Not every variance needs a recount. Some are small and low in value, and recounting them costs more than the difference. A useful rule is to set thresholds before the count starts, and to decide them by value and item type, not only by percentage.

Send a line back for recount when:

  • the value impact is above the threshold the team agreed;
  • the item is high in value, or known for losses;
  • the difference looks like a unit mistake, such as pieces against cartons;
  • the counter says the count was rushed or interrupted;
  • the same location shows several variances;
  • the result is far from the book quantity with no obvious reason.

Send the recount to a different person where possible. A second count by the same person often repeats the first mistake.

What to check before approving

When a recount agrees with the first count, or when the difference is small enough to accept, the next step is approval. Before approving, a reviewer can ask:

  1. Are both quantities in the same unit and for the same item and location?
  2. Did stock move during the count? Check receipts, issues and transfers around the count time.
  3. Is the explanation in the remarks specific enough to act on?
  4. Is there a photo or other evidence where the item or label was unclear?
  5. Is the person approving independent of the person who counted?

Inveck’s page describes supervisors approving or rejecting with remarks that stay with the entry, and an audit trail where every entry is stamped with user, date and time.[1] That record is what lets someone else understand later why a variance was accepted.

A fictional example

The numbers here are made up. A counter records 94 units of an item with a book quantity of 100 in one bin. The value impact is above the team’s threshold, so the line goes back for a recount.

On the recount, a second person counts 94 again, but notes that a pallet of the same item sits in the next bay. The supervisor checks the movement records and finds a transfer that was not posted to the book. The supervisor approves with a remark such as "transfer not posted, correct the book". The remark stays with the entry.

The recount did not change the count. It changed how confident everyone was in it, and it pointed to the real cause.

Keep the reasons

A variance report that carries only numbers invites questions later. A report that carries remarks and approvers answers them. Inveck’s page frames the goal as a final report that carries only numbers your team has stood behind.[1] It also lists sign-off and lock, where the Incharge signs and the count is locked after final submit, and export of the signed-off variance report so adjustments can be posted to your ERP.[1]

The public page does not describe every setting. Confirm in a walkthrough how recount requests, approval levels and locking are configured for your own count.

Checklist

  • Thresholds agreed before the count starts.
  • Variances reviewed by item, category and location, with value.
  • High-value or doubtful lines recounted by a different person.
  • Movement records checked before approval.
  • Approval with a remark, by someone who did not count.
  • Final report signed off and locked before adjustments are posted.

For more on variances and recounts, see Inveck’s recount and approvals page, the inventory variance report guide and the article on variance and shrinkage.

Sources and scope

[1] Inveck, Recount and Approvals page, checked 3 November 2026. https://inveck.com/recount-approvals/

This is a first-party product description, not a fresh account-backed test of the app or a customer’s configuration. The example is fictional. The article makes no performance, compliance or customer-result claim.