After the first live count, on-hand numbers should match what's physically on the shelf, by location and by bin. Available quantity should already subtract what's committed to open sales orders. The count should post without a re-key into another system. You should trust the number enough to act on it that same day.
Teams often judge new inventory software by the demo, the sales call, or the training schedule. None of that tells you much. The real test lands the first time someone walks the floor with a scanner, counts a bin, and checks whether the screen agrees with what's in front of them. If it doesn't, the software hasn't earned anything yet, no matter how clean the dashboard looked in the sales deck.
Old software and old spreadsheets fail this test constantly. A sales order ships but the count doesn't drop. A transfer between buildings posts at one site and never arrives at the other. Someone enters a receipt by hand two days late because the scanner was down. By the time anyone notices, the warehouse has already delayed an order, searched for a SKU that was in a different bin the whole time, or bought more stock than the business needed because nobody trusted the number that said otherwise.
Many systems hand you a count and leave you to figure out whether it's right. That's the gap. The question isn't whether a system can produce a number. It's whether the operator can act on that number without checking it twice.
Five things a trustworthy first count should show you
These are the checks worth running before anyone calls a new count "done." Each one is something an operator can verify on the floor, not a claim to take on faith.
- On-hand quantity matches the physical shelf count, down to the bin, not just the warehouse total.
- Available quantity is on-hand minus what's already committed to open sales orders or reserved for a work order.
- The count posts into the system once, with no manual re-entry into a spreadsheet or a second tool.
- A transfer between two owned buildings shows up correctly on both ends, not just the one where it started.
- Someone on the floor can pull the number up on a phone or scanner and trust it enough to pick against it immediately.
If any one of these fails, the software hasn't closed the gap between what the business knows and what gets done with that knowledge. It's just produced another number for someone to double-check by hand, which is the exact habit the new system was supposed to break.
A two-building count, worked through
Take a distributor running SKU 4410, a gasket kit, out of a main warehouse and a satellite building twenty miles up the highway. The old system showed 340 units company-wide. Nobody could say how many of those sat in which building, so the sales team quoted a customer against the full number without checking either shelf.
The first live count split that total by location: 210 units in the main warehouse, 130 at the satellite, with 40 of the main warehouse units already committed to two open sales orders. Available at the main site dropped to 170. A picker walked the aisle with a scanner, counted bin B-14, and the screen matched what was in front of her: 210 on-hand, exactly. That's the test. Not whether the software could produce a number, but whether the number held up against a physical bin on a Tuesday afternoon.
The satellite count told a different story. On-hand read 130, but the floor had 94. Someone had shipped a will-call order out of that building the week before and logged it against the wrong site. That mismatch wasn't a failure of the new count; it caught a problem the old system had been carrying for months without anyone noticing. The team adjusted the number, noted the reason, and used the corrected 94 as the new baseline going forward.
That's what a first live count is supposed to do: not just hand over a number, but surface the gap between what the business believed and what was actually true, then give the operator something to act on the same day.
Where new inventory software usually falls short of that bar
A common failure isn't a bad count. It's a count that's right in one place and wrong somewhere else a reader actually looks. A company-wide total can be correct while one building is sitting empty. A dashboard can show healthy stock while a specific bin is out and nobody's been told. Available quantity that doesn't subtract committed orders will tell a salesperson they can promise stock that's already spoken for.
Another common gap: the count is accurate at the moment it's taken, then goes stale because the next sale, receipt, or transfer doesn't post automatically. A system that requires someone to remember to update a spreadsheet after the fact isn't really live. It's a snapshot with a short shelf life.
Fishbowl is the platform. Fishbowl Inventory, Fishbowl Advanced Manufacturing, and Fishbowl Advanced Warehouse are purpose-built parts of Fishbowl, matched to how the business runs. On Fishbowl, a count, a sale, a receipt, and a transfer all post to the same record, so the number you check on the floor is the same number everyone else in the business is looking at.
On cloud Fishbowl Inventory, the work doesn't stop at a clean count. The AI Operations Specialist uses live Fishbowl data to prepare purchase orders, sales orders, transfers, receipts, and adjustments for your approval. If the first count on a SKU comes in short, it can draft the reorder instead of waiting for someone to notice the gap and start the paperwork. Nothing is saved or changed without the operator's approval. Ask, Approve, Done.
What this looked like for one beta tester
Brian Garrett at Telluric Companies tested this early, on the purchase order workflow specifically. His result: the AI Operations Specialist saves him at least 45 minutes per purchase order. That's not a claim about every workflow in the business. It's one documented piece of the gap closing: a task that used to take checking, re-checking, and manual entry now takes an approval. See more results at case studies.
That's the standard worth holding new inventory software to. Not whether it looks clean in a demo, but whether the first real count on a real SKU holds up, and whether the system does something useful with what that count tells it.
A short buyer test before you sign off on go-live
Before calling the first count a success, run through this list with whoever did the counting:
- Pick three SKUs across two locations and compare the screen to the shelf, bin by bin.
- Check available quantity against anything already committed to an open order.
- Process one transfer between buildings and confirm it lands correctly on both ends.
- Have someone without training pull up the count on a phone and see if they trust it enough to act.
- Wait 24 hours, then recheck the same SKUs to confirm the number didn't go stale.
Many teams skip step five and regret it. A number that's right today and wrong tomorrow hasn't closed the gap; it's just delayed it.
Setup, timing, and who you can call
Paid setup and training on Fishbowl typically run 6 to 8 weeks, with expert-led guidance rather than a self-serve manual. The product is useful from the first live count, not just after the full rollout finishes. If a question comes up mid-setup, support is in-house, US-based for US customers and APAC for APAC customers, and customers can reach a person by phone, email, or chat. Smart Chat covers the quick questions; a person is still there for the rest.
None of this replaces the books. QuickBooks or Xero still keeps the accounting. Fishbowl does the operational work and syncs the result, so the count that's right on the floor is also right in the general ledger.
If you want to see what a first live count looks like on a real SKU, not a sample company, get a demo.
Fishbowl does the work. You make the call.
Frequently asked questions
How long does it take to trust a live count on new inventory software?
Paid setup and training on Fishbowl typically run 6 to 8 weeks, but the software is useful from the first live count. You don't wait for full rollout to get a number you can act on; you check that single count against the shelf and go from there.
What's the difference between on-hand and available quantity after a live count?
On-hand is what physically sits on the shelf. Available is on-hand minus what's already committed to open sales orders or earmarked for a work order. A location can show plenty on-hand and still have almost nothing available to sell.
Can the AI Operations Specialist help during the first live count?
The AI Operations Specialist uses live Fishbowl data to prepare purchase orders, sales orders, transfers, receipts, and adjustments for your approval. After a count exposes a shortage or an overage, it can draft the follow-up transaction. Nothing is saved or changed without the operator's approval.
What if the first count doesn't match the old system?
A mismatch on day one usually means the old system was already wrong, not that the new count failed. Reconcile by bin, note the adjustment and the reason, and let that corrected number become the new baseline going forward.