Cycle Counts for Epicor Eagle
Weekly counts picked from Eagle’s item file and usage, counted blind by people who never sign in, reviewed and closed, with a live variance dashboard over Eagle’s physical-inventory posting during the annual count.
Purchasing & inventoryUpdated Oct 202620 ERPs
See it work on Eagle.
Click through the steps. Fictional data, in Eagle’s terms; the real thing runs on Eagle.
Something gets counted every week, picked from usage. Monday’s list: the top 25 drywall items, handed to J. Alvarez.
The problem, as it happens in Eagle.
Eagle has PIP for the physical and an adjustment screen for the rest. What it doesn’t have is the routine: pick twenty-five SKUs on Monday, hand them to someone in the yard who has no Eagle login, count without seeing the system quantity, and know by Friday whether it happened.
So counting waits for the weekend the whole yard shuts down, and the variance is a number the controller learns about once a year.
How it works.
- 1
Pick the SKUs
A weekly list picked from Eagle’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 Eagle 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 Physical Inventory Posting.
- 4
During a physical
A running variance board read from Physical Inventory Posting, 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 Eagle.
Lunica reads Eagle’s item file, usage, adjustment history and the physical-inventory posting through the Eagle data warehouse, read-only. Counts are picked by method, top sellers this week, randomised by usage, a bin, a category, and the system quantity is hidden from the counter until review.
Nothing lands in Eagle without a person. A variance becomes an adjustment only when a person keys it in Eagle; the nightly sync notices the adjustment and closes the loop. During a physical, the dashboard reads PIP live so the controller sees the frozen book against the count as it posts. The Friday email and the buyer’s daily reorder alert go to the people you enroll.
What a week looks like.
- Twenty-five SKUs counted every week, picked for you.
- Counters accountable by name in the Friday email.
- Recounts triggered over your threshold, closed with frozen figures.
- The buyer’s reorder alert every morning, with an all-clear on quiet days so silence means a fault.
Questions
Does it post adjustments in Eagle?
Never. A person keys the adjustment in Eagle; Lunica sees it on the next sync.
Can we keep counting in PIP?
Yes. Count in PIP and review here. The variance dashboard reads the posting live.
Do counters need an Eagle login?
No. A printed sheet or a phone link. Counters never sign in.
How are SKUs picked?
By the method you choose per schedule: this week’s top sellers, random by usage, a bin, a category.
What’s the reorder alert?
A daily email to the buyer listing what’s at or under minimum, read from Eagle. It always sends, so a quiet day gets an all-clear.
The same workflow, on another ERP.
Cycle Counts is written for every system on the list. You’re reading the Eagle version.
See it on your Eagle data.
Thirty minutes. We walk the workflow on Eagle data, then map it to yours.