How does a parts store count inventory without closing? Cycle counting, every day.

Every parts store has two inventories: the one on the shelves and the one in the system. Counting keeps them the same. Closing for a day once a year does not, and this is the method that does.

Why do on-hand numbers drift at a parts counter?

On-hand drifts because the counter is busy, not because of theft and rarely because of the software. These are the leaks, in the order we see them at heavy-duty counters:

• Warranty. A part fails, the customer brings it back, a new one goes out. If the swap isn’t rung as a warranty, the new part leaves without a ticket and the old one sits in a pile. Nothing moved on paper.
• Cores. The old starter comes back a week after the sale. Was it entered as a core return, or did it go in the core pile and get credited later from memory?
• Received without a purchase order. A vendor drops off, the box goes on the shelf, the paperwork goes in a drawer. On hand never moved.
• Duplicates. The same part under two numbers, each with its own count, neither one right.
• Special orders. Ordered for one customer, arrived, and put on a shelf under the counter. It’s in the building. It’s not stock.
• Taken now, billed later. A good customer on terms grabs two filters on his way out. The ticket gets written up at the end of the day, or not.
• The wrong bin. The part is in the building and the count is right, but it’s on rack G instead of rack C, so the counter sells out, orders more, and the store ends up with twice what it needs.

Every one of those is a process problem that a count reveals and a system can then prevent. The count comes first.

Why doesn’t an annual physical inventory fix it?

An annual physical gives one accurate snapshot a year, costs a day of sales, and explains nothing. Close for a day, count every shelf, enter the totals: for a week the inventory is right. By spring it has drifted again, and because the mistakes are months old by the time anyone counts, nobody can say what caused them.

What is cycle counting?

Cycle counting is counting a slice of the store every day, while the store is open, so that over a few weeks everything that matters has been counted. Each count is small enough to do between customers. Because the mistakes are days old instead of months, you can usually see what caused them. Cycle counting is how every warehouse that can’t close runs its inventory, and a parts store can’t close either.

How does a daily cycle count work at a parts store?

A daily cycle count is ten or twenty minutes of counting one rack or a handful of fast movers, in walk order, by whoever is free. Which parts come up, and how often, is decided by how fast they move: that is the ABC method. The count itself goes like this:

In walk order. Go down the aisle the way the racks stand, so nobody gets skipped. The count sheet should already be in that order; if it isn’t, the store layout isn’t set up, and that comes before counting.

By exception, the same day. Some events say a number is wrong before anyone counts: a pick comes up short, a part shows a negative on hand, a bin reads zero but the counter just sold one. Count that item that day, while the cause is fresh.

A daily count never needs the store closed, and it never needs a Saturday.

What is a blind count, and why count blind?

A blind count is one where the person counting cannot see what the system expects. If the screen says 38 and you see roughly 38, you write 38; if it says nothing, you count. A blind count takes slightly longer and is worth it every time, because it is the difference between confirming the number and checking it.

What should you do with a count difference?

A count that finds 34 where the system said 38 has done its job only if someone asks why. Post the adjustment with a reason, and review the reasons together once a month. The patterns tell you what to fix:

• Shortages that match warranty swaps: the replacement went out without a ticket.
• Overages on reman parts: cores going out as sales, or coming back without a core return.
• A pattern of shortages on one rack: wrong-bin problem, or that rack is near the back door.
• Shortages that match special-order parts: they’re being sold off the shelf instead of to the customer who ordered them.
• Differences right after a big delivery: receiving.

One difference in twenty parts is a store being a store. More than that on one rack means something upstream is broken, usually receiving, warranty or cores, and it is worth fixing that before counting more. The adjustment fixes the number; the reason fixes the next number.

Where do cores and warranty parts go in a count?

Cores and warranty returns get their own bins and get counted like any other part. A core charge is a deposit, not a part, but the rebuildable core itself is stock, and it drifts if it’s left in a pile. Warranty returns waiting to go back to the vendor get a bin, a count, and a line on the vendor return so the credit doesn’t get forgotten. The part the core came with keeps its own count; the core pile must not inflate it.

How does AxleTap handle cycle counts?

AxleTap counts by rack, department, bin range or the whole store, on a handheld that never shows the expected quantity. The detail is on the product page.

• Today’s count can be one rack.
• The handheld runs in the browser on a phone or a Zebra scanner. Nothing to install. Every count is blind.
• Count sheets, pick lists and put-away lists follow the walk order. The store layout is a map you draw once from above; the map creates the bins and shows which racks are due.
• Differences post as one adjustment, with a reason.
• A part received without a bin gets a suggested one.
• Short picks get a reason at the point they happen, so the exception count has a trigger.
• The register’s Taken now choice on a charge account is for the customer on terms walking out with two filters: the part leaves, the ticket is written, the account is charged, in one step.
• Warranty returns and vendor returns are tracked until the vendor’s credit arrives.

If you’re moving off QuickBooks POS, the count in the weeks before go-live is the one that matters most. Start the daily cycle the first week after.