Cycle Counts for ECI RockSolid MAX
Weekly counts picked from RockSolid MAX’s own usage, counted blind by someone who never signs in, reviewed and closed, and a variance that becomes an adjustment only when a person posts it in a physical count.
Purchasing & inventoryUpdated Oct 202620 ERPs
See it work on RockSolid MAX.
Click through the steps. Fictional data, in RockSolid MAX’s terms; the real thing runs on RockSolid MAX.
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 RockSolid MAX.
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 RockSolid MAX, and know on Friday whether it got done. A physical count 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, RockSolid MAX 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 RockSolid MAX’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 RockSolid MAX 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 a physical count.
- 4
During a physical
A running variance board read from a physical count, 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 RockSolid MAX.
Lunica reads the item record, on-hand quantities by branch, bin locations, sales and receipt history, and a physical count through RockSolid MAX’s reporting access, under an account that can only read, confirmed at onboarding. 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 RockSolid MAX 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 a physical count, 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 RockSolid MAX?
No. A variance becomes an adjustment only when a person posts it in a physical count. 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 RockSolid MAX’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 RockSolid MAX’s own physical screen instead?
Yes. Count there and review here; the variance board reads a physical count 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 RockSolid MAX. 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 that connects out to ECI’s hosted RockSolid MAX. It reads RockSolid MAX over the LAN; counters open a link or carry a sheet, and nothing comes in from outside.
Does it need a server?
Lunica runs on one server inside your network that connects out to ECI’s hosted RockSolid MAX, set up and maintained by Lunica. It reads ECI RockSolid MAX through RockSolid MAX’s reporting access, under an account that can only read, confirmed at onboarding. There is no inbound connection from outside your network.
What does Lunica read in RockSolid MAX?
The customer account, open items and terms, purchase orders and receipts, the item record, quotes and order history, as each workflow needs them. Read-only, and only the rows a task is about.
Can it post to RockSolid MAX?
Nothing lands in RockSolid MAX without a person. What belongs in RockSolid MAX goes back as a RockSolid MAX import where one exists, or keyed by your team from what Lunica prepared.
What about our documents?
Invoice copies and scans keep living in RockSolid MAX document storage. Lunica reads them when a workflow needs one and never writes to them.
The same workflow, on another ERP.
Cycle Counts is written for every system on the list. You’re reading the RockSolid MAX version.
See it on your RockSolid MAX data.
Thirty minutes. We walk the workflow on RockSolid MAX data, then map it to yours.