By Louis Balla, Chief Revenue Officer, Nuage.
NetSuite inventory counts drift because of receiving mistakes, unconfirmed transfers, production consumption that does not match the bill of materials, and late-posting returns and write-downs. A cycle count program with ABC grouping, variance tolerances and approved adjustments catches those errors during the year and leaves the evidence an auditor wants to test.
This article covers why NetSuite counts drift and how a cycle count program finds the gaps a single physical count misses.
Why Your Inventory Count Is Already Wrong
Inventory discrepancies accumulate through small daily process breakdowns that go unnoticed until reconciliation.
Common Root Causes of NetSuite Inventory Errors
Receiving mistakes are a common cause. When inbound shipments aren’t verified against purchase orders at the dock, phantom inventory enters the system immediately. A warehouse team that scans one case but keys in a quantity of ten creates a variance that carries into later transactions, such as transfers, picks and work-in-progress consumption.
Unposted inventory transfers between locations are another cause. If a warehouse associate physically moves stock but the corresponding transfer record in NetSuite isn’t confirmed, one location shows a surplus while another shows a shortage, and neither triggers an alert until someone counts.
Production variances add to the problem for manufacturers. When bill-of-materials records don’t reflect actual component consumption on the floor, finished goods appear without the corresponding raw material deductions. Returns, damaged-goods write-downs and consignment stock cause variances too when they post late.
Inventory work also stays open longer than other work. Inventory, warehouse and fulfillment requests made up 167 of the 3,241 client requests Nuage classified (5.2%), covering counts, adjustments, bins, mobile picking, lot handling and returns to stock. Only 40 of those 167 had closed when we measured (24.0%), the lowest closing rate of any category, and the ones that closed took a median of 23.9 calendar days, including time spent waiting on the client.
Inventory Visibility and Setup Gaps
A 2025 supply chain integrity survey of the food and grocery sector by Impinj, reported by Food Industry Executive, found that only one-third of food and grocery operations consistently achieve 360-degree, real-time inventory visibility.
Our own assessments found gaps in inventory setup and data. Between July and September 2026 our team logged assessment findings for 15 client accounts, and at least six included a finding about inventory setup or inventory data. A robotics company had 19 items sitting at negative on-hand quantity, and transfers dated that month were still creating new ones. An industrial gas and dry ice supplier had lot tracking switched off, so shelf life for dry ice and certification dates for cylinders had no place in the system. At an industrial technology company, 88% of 9,956 inventory and assembly items carried no recorded cost, which affects margin and cost-of-goods reporting. These accounts were assessed because they were onboarding or under review, so they are not a random sample.
A NetSuite Cycle Count Strategy for Audit-Ready Inventory
An annual physical count shows quantities on one day and says little about the process failures that caused errors during the year. A cycle count program checks groups of items on a schedule through the year, and if your auditor accepts the program, you may not need to shut down for a full physical inventory.
How ABC Classification Drives Inventory Accuracy
ABC segmentation sets how often each item is counted by its value and movement. “A” items, your highest-value or highest-velocity products, get the most frequent counts. “B” items are counted less often, and slow-moving “C” items can be counted least often with little added risk.
Assign items to groups based on criteria like annual dollar volume, transaction frequency, or criticality to production, then schedule each group’s counts with whichever NetSuite count tool you use. The schedule spreads the counting across your team and the year.
Counting needs to account for stock committed to open jobs. An inventory lead at a commercial truck equipment company described the problem with counting while jobs are open: “if I have 10 of an item sitting on a shelf, and 2 of the same item also sitting committed on an active job … when I go to count and put ’10’ in the cycle count it will change the QOH to 10.” Our consultant walked through how quantity on hand and quantity available relate to committed stock, and the client has since added work-in-process and routing to its account, which our team is setting up in a refreshed sandbox before production at the client’s request.
Setting Variance Thresholds and Triggers
Set a tolerance for each count group, tighter for high-value items, and configure NetSuite workflows to escalate exceptions automatically. When a count falls outside tolerance, the system should trigger a recount. If the variance holds, flag it for root-cause review and route the adjustment through an approval workflow before it posts to the general ledger.
With tolerances and approvals in place, counting runs all year as a control on your inventory. Besides accurate numbers, auditors want evidence that errors are caught and corrected during the year.
What Inaccurate Counts Cost Finance and Operations
When your NetSuite records don’t match the shelf, finance and operations plan from the wrong numbers.
Finance teams rely on inventory valuations for cost-of-goods-sold calculations, margin analysis, and balance sheet reporting. As an illustration, a 3% variance on $20 million of stock is $600,000 of misstated assets, and an auditor will want to know how your counts are controlled. Operations teams run into stockouts and emergency expedites.
For food and CPG companies, lot and batch records add a further requirement. If your lot records show 500 units of a recalled lot shipped to 12 customers and the real number is 800 units across 20 customers, a recall notice misses 8 of the 20 customers who received the lot. Our guide to lot tracking in NetSuite for food and beverage covers how to configure lot records and test a trace.
Our team helps mid-market manufacturers and distributors get more out of NetSuite through continuous NetSuite support and ongoing optimization. Our guide to NetSuite inventory control goes further on counts, bins and replenishment.
Build Audit-Ready NetSuite Inventory Accuracy Before the Auditor Arrives
An auditor will ask you to explain each discrepancy found. Start by mapping your highest-risk processes: receiving, transfers, production consumption, and returns. Run NetSuite’s inventory activity reports and saved searches to identify items with frequent adjustments, since those usually point to a process failure. Use barcode scanning at transaction points to reduce manual keying errors, and enforce segregation of duties so the person counting inventory isn’t the same person approving adjustments.
Your inventory accuracy program should produce the audit trail itself: count schedules, variance reports, root-cause analyses, and corrective action logs that demonstrate control.
For a conversation about a cycle count strategy for your operation, schedule a discovery call with a NetSuite expert.
Frequently Asked Questions
How should I document cycle counts so auditors can easily test my controls?
Use a consistent template that captures who counted, when it was counted, the bin or location, the item identifier, the expected quantity, the counted quantity, and the reason code for any adjustment. Store recount evidence and approvals in a centralized repository, and tie each exception to a corrective action so the trail is complete and easy to sample.
What is the best way to separate true inventory issues from data setup problems in NetSuite?
Start by validating item master data, unit of measure conversions, bin assignments, and location settings before assuming the warehouse count is wrong. If discrepancies cluster around specific items or transaction types, the cause is more often configuration or training than shrinkage or picking errors.
What KPIs should I track to prove inventory accuracy is improving over time?
Monitor adjustment rate by item and location, recount frequency, average time to resolve exceptions, and the percentage of counts completed on schedule. Also track order exceptions tied to inventory errors, such as shorts and backorders, to connect accuracy to customer impact.
How do I handle inventory items that are hard to count, like liquids, bulk goods, or partial pallets?
Define standard measurement methods (weight, volume, or calibrated container counts) and train teams to use the same approach every time. Where possible, use lot-level labeling and pre-defined pack configurations so partial quantities are recorded consistently. Write the method into the count instructions so a second counter gets the same result.
What roles should be involved in reviewing inventory adjustments to prevent fraud and mistakes?
Involve operations for context on what happened, finance for valuation impact, and a separate approver who does not perform the count or execute the transaction. Clear role-based access and periodic review of adjustment logs help confirm that each change was justified and approved.
About the author
Louis Balla is Chief Revenue Officer at Nuage, a NetSuite optimization partner that has served 250+ clients since 2011 and holds a 4.9 out of 5 rating on Clutch. The client work in this article is our team’s.
