CURIOUSRUBIK
Let’s talk about your next move ↗View complete sitemap
Back to the blog

Improving NetSuite Inventory Accuracy with Counts Bins and Controls

Improving NetSuite inventory accuracy starts with finding where recorded stock stops matching physical stock. Use counts to reveal the difference, then correct the receiving, movement, picking or return process that caused it. Repeated adjustments without cause analysis can make today's balance look right while preserving tomorrow's error.

The inventory manager and controller should own one shared variance process. Operations establishes what physically happened; finance confirms the valuation, posting period and evidence for any correction. This guide connects those responsibilities without replacing account-specific counting instructions.

Diagnose the type of difference

Distinguish four situations before changing stock. A location quantity may be wrong. The total location quantity may be right but split across the wrong bins. A lot or serial identity may be wrong despite a correct quantity. Finally, quantity may be accurate while inventory value is incorrect.

Each situation needs a different investigation. A missing bin movement should not automatically become a quantity write-off. A correct count does not prove that a receipt was costed correctly. Ask the warehouse to retain transaction references, not just a description such as “system error.”

Build a small cause list that employees can apply consistently: receipt timing, unit conversion, unrecorded movement, short pick, return disposition, damaged stock, duplicate interface event and unexplained difference. Leave room for a narrative because a category alone will rarely establish the correction.

Design bins around actual work

Use a bin convention that workers can recognize on a label and on the floor. Avoid near-identical names, inactive overflow locations and informal staging areas that never appear in the system. Decide who creates a new bin and what happens before it can receive stock.

NetSuite distinguishes basic bins from Advanced Bin/Numbered Inventory Management. Advanced functionality supports numbered inventory and more flexible location-level use. Bins track on-hand quantity; they do not establish separate costing per bin.

That distinction matters in an investigation. If the same item is found on the next shelf, confirm the correct bin movement rather than assuming its value changed. If the goods belong to another legal entity or physical location, stop and resolve that broader classification before treating the issue as a shelf-label problem.

Set the counting boundary

Define what will be counted, by whom and at what time. Prioritize items with high financial exposure, frequent movements, recurring differences or traceability requirements. A count schedule based only on item value can overlook inexpensive items whose shortages stop production.

For every count, record the location, item population, relevant bins, count unit and treatment of movements during the exercise. Where practical, pause movement in the selected area. Where operations must continue, retain a movement log and assign someone to reconcile it to the count boundary.

NetSuite Inventory Count uses a snapshot taken when the count starts. Its documentation explains how movements during the count affect comparison with that snapshot and identifies additional prerequisites for counting lot or serialized items. Do not interpret a snapshot as an automatic freeze on warehouse activity.

Create start and complete the count record

These are the standard Inventory Count steps; a WMS role can expose a different menu. Confirm enabled features, authorized roles and the approved variance account before testing.

  1. Open Transactions > Inventory > Enter Inventory Count. Select the location, date and variance account, add the intended items, bins and units, then save. Saving creates an Open record; it does not start or approve the count.
  2. View the record and choose Start Count to establish the snapshot. Edit the started record to enter physical count quantities and required inventory detail, accounting for documented movements during counting.
  3. After verification, choose Complete Count. The authorized reviewer investigates the variance and approves or rejects it through the configured process. Inspect resulting adjustments and retain the evidence.

Do not change fulfillment controls or force negative inventory to make a count pass.

Investigate before approving

Ask the counter to recount a material difference without being coached toward the expected number. Check the surrounding bins and staging locations. Review receipts, shipments, transfers, returns and production movements around the count time. Confirm that a carton has not been entered as one piece.

Keep the evidence concise: first count, recount, movement bridge, source documents, cause and proposed action. Establish approval thresholds based on both quantity and financial exposure. A small quantity of a high-value item may need more review than a large quantity of packaging.

Before posting, determine whether a missing operational transaction should be completed instead of creating an adjustment. If the original receipt is merely delayed, adjusting inventory upward and then posting the receipt would count the same goods twice. The controller should approve the correction method and applicable period.

Hypothetical variance reconciliation

Consider an item whose count snapshot shows 100 units. Staff physically count 93. During the counting window, a documented shipment of five units leaves the area. A recount also finds two units in an unlabeled overflow bin.

The physical population at the snapshot boundary is 93 plus the five shipped plus the two found elsewhere, or 100 units. There is no unexplained seven-unit loss. The team must still correct the overflow-bin practice and ensure the shipment was recorded through the proper transaction.

Now change the example: the two overflow units cannot be located. The supported population is 98 and an unexplained difference of two remains. Investigate that remaining difference and value it under the account's costing configuration. The example illustrates a movement bridge; it is not an instruction to enter a particular adjustment transaction.

Use a repeatable variance record

A reusable record should capture:

  • Count reference, item, location, bin and lot or serial detail
  • Snapshot quantity, physical quantity and approved movement bridge
  • Recount evidence and independent reviewer
  • Root cause and related operational transaction
  • Correction type, quantity, value, account and posting period
  • Preventive action, owner and verification date

Keep adjustment rights separate from ordinary counting responsibilities where practical. Review emergency access afterward. A controlled process should still allow operations to recover from an urgent problem without leaving an untraceable correction.

Measure the process that creates the stock figure

Track the percentage of counted lines within your defined tolerance, the value of unexplained differences, repeat causes and overdue corrective actions. Publish the denominator and tolerance. An accuracy percentage is hard to interpret if one warehouse counts pieces while another counts cartons or excludes its difficult items.

Use trend reviews to decide whether training, labels, transaction timing or interface controls need attention. When the same shelf or workflow repeatedly fails, redesign the process and test the change in the next counting cycle.

When should the bin process be redesigned

Redesign it when people routinely bypass scans, use unrecorded staging areas, cannot distinguish similar labels or need repeated manual corrections. More frequent counts can expose these issues, but they cannot remove the underlying cause.

The goal is an explained stock balance supported by reliable daily transactions. Treat counts, bins and adjustment approvals as one control loop, and inventory accuracy becomes a process the business can maintain rather than a number it repairs at month end.

Related resources

What’s on your mind?

A little context is all it takes to begin.

Please leave out passwords, payment details and confidential account data.