A manufacturing unit never holds just one inventory. Raw material sits in stores, work-in-progress moves across the shop floor, and finished goods wait near dispatch. Verifying all three against the books is a different exercise from counting trading stock, and it needs its own plan.
This guide walks through how a manufacturing team can run physical stock verification across raw material, WIP and finished goods: how to prepare, how to count each stage, and how to close the count with evidence that stands up to review. It is a practical workflow guide, not a customer case study.
Why manufacturing counts need their own plan
A trading business mostly counts what it bought and has not sold. A manufacturer counts three states of the same material, and each state behaves differently during a count.
Raw material leaves stores the moment it is issued to production, and an issue that is not booked makes the stores count look short. Work-in-progress rarely exists in neat, countable units. Finished goods can include stock under quality hold that should not be mixed with dispatch-ready quantities.
None of this means the records are wrong. It means the count has to be organised around how material actually moves, or the team will manufacture variances that never existed.
Choose the count type and freeze movement
Decide the count type before anything else. A complete wall-to-wall count covers every item once, usually at year-end or before an audit. Cycle counts spread the effort across the year and suit fast-moving raw material. Blind counts, where the team counts without seeing book quantities, keep the count honest by removing the option to match the system.
Then freeze movement for the count window. Pick a period when goods receipt, production issue and dispatch can pause. Where a full pause is not possible, mark the moving stock clearly and record what moved during the count. A count taken against a moving target produces differences that are scheduling artefacts, not real losses.
Counting raw material in stores
Stores are the most structured part of a manufacturing count, and the easiest place to lose accuracy through unit-of-measure mistakes. A component counted in pieces may be booked in kilograms or metres. Agree the counting unit per item before the count starts and write it on the count instruction.
Where bins and racks carry QR labels, the team can scan the label with a phone, see the item they are counting, and enter the quantity against it. QR tagging also keeps the count tied to a location, which matters when the same item sits in two stores or in both stores and the floor.
Lot or batch references deserve the same discipline as quantities. Counting "enough" of a material without noting which lot it came from weakens traceability later, especially where suppliers or customers ask for it.
Counting work-in-progress
WIP is where most manufacturing counts struggle, because the material is mid-transformation. Two practical conventions help.
First, count WIP by production stage, not by final product. A half-machined component is counted as that component at that stage, with a stated completion estimate if the books need one. Second, fix a cut-off rule: decide whether material issued to the floor but not yet worked on counts as stores stock or WIP, and apply that rule everywhere.
The goal is consistency, not perfection. A WIP figure produced the same way every period is far more useful for reconciliation than a precise-looking number produced differently each time.
Counting finished goods
Finished goods look simple but hide two traps. Stock under quality hold must be counted and recorded separately from dispatch-ready stock, because treating them as one quantity inflates what can actually be shipped or sold. And packed goods need a stated counting basis: count sealed cartons by carton where packing lists are trusted, and open a sample where they are not.
Record condition alongside quantity. Damaged or returned finished goods that are counted at full value create problems that surface only at valuation time.
Capture evidence where the item stands
Paper sheets and memory do not survive an audit query raised months later. A phone-based counting app lets the team scan, enter quantities, and attach photo and signature evidence at the exact rack or machine where the item was counted.
Shop floors and godowns are also where networks fail, so the counting app must work offline and sync when connectivity returns. A count that depends on signal strength stops at the wrong rack.
Reconcile, recount and close
The count is not finished when the last item is counted. Physical quantities are matched against book stock, and each variance is reviewed while the team still remembers the floor. Genuine mismatches go back for a recount rather than being adjusted away, and a clear recount and approvals trail records who counted, who approved, what changed and when.
Verified figures then need to reach the systems finance already uses. ERP or Excel integration keeps the reconciled numbers moving into valuation and reporting, instead of sitting in a parallel spreadsheet that drifts from the books.
How Inveck fits this workflow
Inveck is built for organisations with a lot of physical things, including manufacturing units handling raw material, WIP and finished goods. Teams count on the Inveck mobile app with QR tagging, reconcile against books on a real-time dashboard, and close each verification with photo evidence and digital sign-off.
Sources and scope
[1] Inveck, Inventory Verification product page, checked 6 November 2026. https://inveck.com/inventory-verification/ [2] Inveck, Inventory Verification for Manufacturing, checked 6 November 2026. https://inveck.com/industries/manufacturing/ [3] Inveck, Photo & Signature Evidence, checked 6 November 2026. https://inveck.com/photo-signature-evidence/ [4] Inveck, Offline Data Sync, checked 6 November 2026. https://inveck.com/offline-data-sync/ [5] Inveck, Recount & Approvals, checked 6 November 2026. https://inveck.com/recount-approvals/
These are first-party product descriptions, not a fresh account-backed test of the mobile application or a customer’s configuration. Counting conventions described here are general practice, not a certification requirement. The article makes no quantified performance claim, compliance certification claim or customer-result claim.

