Cycle counts for building-supply dealers.
Lunica runs the cycle-count routine your ERP never gave you, and never posts an adjustment on its own.
Purchasing & inventoryUpdated Oct 202620 ERPs
See it work.
Click through the steps. Fictional data; the real thing runs on your ERP.
Something gets counted every week, picked from usage. Monday’s list: the top 25 drywall items, handed to J. Alvarez.
The problem.
Everyone agrees the yard should count a little every week. Nobody has a way to pick what, hand it to a counter who doesn’t have a login to your ERP, and know on Friday whether it got done. The physical count screen was built for the annual physical, not for Monday’s top twenty-five.
So the counting happens once a year, over a weekend, and the variance is a surprise. In between, your ERP says sixty-one pails of joint compound are on the shelf when there are fifty-eight, the reorder never fires, and the pro desk finds out when the shelf is empty.
How it works.
- 1
Pick the SKUs
A weekly list picked from your ERP’s usage, by method: top sellers this week, randomised by usage, a bin, a category. Monday’s top-25 drywall items, if that’s what you asked for.
- 2
Hand it to a counter
A printed sheet or a phone link. Counters never sign in. Counts are blind: the quantity your ERP has on hand is hidden until review.
- 3
Review and close
Variances over your threshold get a recount. Close freezes the figures. A variance becomes an adjustment only when a person posts it in the physical count screen.
- 4
During a physical
A running variance board read from the physical count screen, so the controller sees the book moving while the yard counts, and a recount is called while the counter is still in the aisle.
How it connects to your ERP.
Lunica reads the item file, on-hand quantities by branch, bin locations, sales and receipt history, and the physical count screen through its database or data warehouse, under an account that can only read. The weekly pick is made from what moved. The blind sheet carries the item and the bin, never the quantity, and during a physical the posting is read as the yard keys it, so a variance is seen while there is still time to recount.
Nothing is posted to your ERP on its own. A closed count is a list of variances with the counter’s name and the recount beside each one; it becomes an adjustment only when a person posts it in the physical count screen, and Lunica sees the new on-hand the next morning and closes the loop. The reorder alert goes to the buyer you enrolled, and the Friday count email to the people you named.
What a week looks like.
- Something gets counted every week.
- Counters are accountable by name, in a Friday email.
- Variance stops being an annual surprise.
- The buyer gets a daily reorder alert, with an all-clear on quiet days so silence means a fault.
Questions
Does it adjust quantities in your ERP?
No. A variance becomes an adjustment only when a person posts it in the physical count screen. Lunica sees the new on-hand and closes the loop.
Do counters need a login?
No. A sheet or a link, nothing else. Nobody in the yard signs in to anything.
How does it pick what to count?
By the method you set: top sellers this week from your ERP’s sales history, randomised by usage, a bin, a category. An item doesn’t come up twice in a cycle unless its variance put it back.
Can we count in your ERP’s own physical screen instead?
Yes. Count there and review here; the variance board reads the physical count screen as it is keyed.
What’s in the Friday email?
Whether the week’s counts got done and what each counter counted, by name. It goes to the people you enrolled.
Who gets the reorder alert?
The buyer you enrolled, once a day, with every item at or under its minimum in your ERP. On a quiet day it still goes, as an all-clear, so a missing email means something broke.
Where does it run?
On one server inside your network, beside your ERP. It reads your ERP over the LAN; counters open a link or carry a sheet, and nothing comes in from outside.
Available for.
Each version is written in that system’s own terms: its screens, its files, its codes.
Own your AI. Own your software.
Thirty minutes with the people who build it. Bring your ERP.