Inventory Agent
Enter the counts, trace the variances, suggest the reorders, just like your inventory controller.
Works using
+
+
No new system.No integrations.
counted today, posted today ↗
- Bins counted120
- Matches116
- Variances4
- Value at risk$2,310
- B-14 · move RCV-8812 to bin (no adjustment)0.00
- B-22 · V-belt A42 · reason: damaged-36.40
- B-31 · hose clamp kit · pending recount0.00
Do we need to reorder the bearings?
Yes. After today's count we're at 140 against a minimum of 150. A purchase suggestion for 200 is waiting for the buyer.
- 01Count
- 02Enter
- 03Compare
- 04Explain
- 05Reorder
Variances explained the day they're counted
A variance found a week later can't be traced. Your agent posts counts and explains differences the same day.
- Count sheets wait on a desk
- Posted to the ERP Next week
- Deal lost. The stockout was found when a customer order couldn't ship.
- Picked up the moment it lands
- Entered, compared, explained same day
- Accurate stock. No surprise stockouts.
Inventory is messy
- Phantom stock. On the screen, not the shelf
- Stockouts. Orders that can't ship
- Unexplained variances. Written off, not traced
- Paper counts. Keyed days later
An agent that handles the messy parts your way.
- 01Any count formatScanner, sheet, photo
- 02Bin-level compareNot just totals
- 03Traced variancesBefore write-offs
- 04Reason codesEvery adjustment
- 05Reorder suggestionsBelow minimum, flagged
Every count, by hand. Agents should!
- ManualAgent Print count sheet
- ManualAgent Count bins
- ManualAgent Key counts
- ManualAgent Compare to ERP
- ManualAgent Check receipts
- ManualAgent Check shipments
- ManualAgent Recount
- ManualAgent Post adjustment
- ManualAgent Review min/max
- ManualAgent Suggest reorder
No new system. No integrations.
You're not buying software. You're adding an agent that uses the software you have.
- Your screens It uses your CAD, quoting system and inbox with keyboard, mouse and screen.
- Nothing to connect No API projects, no new software, no data migration. Your systems stay as they are.
- Built by talking Explain your process like you'd train a new hire. It learns by doing a real quote.
- You approve Drawings, prices, discounts, sends. Wherever you want a person, it stops and asks.
- Every run on record Screenshots, values read, prices used and who approved, for every quote.
Hand the whole count to an agent
- Enters the counts
- Compares to ERP
- Traces variances
- Asks for recounts
- You approve adjustments
- Posts adjustments
- Checks min / max
- You approve reorders
Agent does itYou decide
Five steps. One count.
One job, start to finish: Main warehouse, cycle count zone B, 120 bins.
- 01
It enters the counts
From the scanner file, the photo of the sheet or the spreadsheet.
Excel · zoneB-count.csv- Bins counted120
- Matches116
- Variances4
- Value at risk$2,310
Cycle count · Zone B · 120 bins
- 02
It compares to your ERP
Bin by bin, item by item, with your tolerance.
Epicor Kinetic · Part transactionsItem From Price 6205-2RS bearing · B-14 ERP 140 · counted 100 −40 ea Receipt RCV-8812Explains the B-14 variance Received, not put away +40 ea V-belt A42 · B-22 ERP 60 · counted 58 −2 ea Hose clamp kit · B-31No transaction explains it: recount ERP 12 · counted 0 −12 kit - 03
It traces the variance
Open receipts, unposted shipments, wrong units. Before writing anything off.
Epicor Kinetic · Inventory adjustmentNo. ADJ-1107Main warehouseDraftDescription Qty Unit Amount B-14 · move RCV-8812 to bin (no adjustment) 40 ea 0.00 B-22 · V-belt A42 · reason: damaged -2 ea -36.40 B-31 · hose clamp kit · pending recount 0 kit 0.00 1 recount requested · 1 reorder suggestedAdjustment −$36.40 - 04
It posts the adjustment
After you approve, with the reason code and evidence.
Outlook · New messageToWarehouse lead
SubjectZone B: one recount needed
Zone B is posted. B-14 was a receipt not yet put away, so no adjustment. Please recount B-31 hose clamp kits: the ERP says 12 and nothing explains the gap.
Zone B variance report.pdf
Send - 05
It suggests reorders
Below minimum? A purchase suggestion for your buyer.
Teams · Main warehouseDo we need to reorder the bearings?
Yes. After today's count we're at 140 against a minimum of 150. A purchase suggestion for 200 is waiting for the buyer.
Answered from: Min/max settings, count results
Inventory & cycle counts: every step
What the agent does, where you decide, and the rules it checks.
you decide every green box
- Count file in
- Enter counts
- Compare to ERP by bin
- Within tolerance?No → trace variance
- Check receipts & shipments
- Variance explained?No → request recount
- Draft adjustment & reason
- Over $500?Yes → controller approves
- Inventory lead approves
- Post adjustment
- Below minimum?Yes → suggest reorder
- Buyer approves reorder
- Send variance report
- Counts posted
Agent does it You decide Rule check
Built around how you work
Not a template. Your steps, your rules, your approvals.
- 01
Explain it once
Talk or type, like training a new hire. Hand over your SOP, price book and a few past quotes.
When a request comes in, first check: within tolerance? If not, trace variance.
Quoting SOP.pdf Price book 2026.xlsx 3 past quotes - 02
Watch it work
It works a real job on your screen. You correct it the way you'd correct a person.
Use the 2026 price book, not last year's.
Got it. Switched to 2026 and re-priced 4 lines.
Read requestDrawingPricing - 03
Save your process
A written procedure and a flowchart. Every run follows the version you approved.
- Enter counts
- Compare to ERP by bin
- Within tolerance?
- Check receipts & shipments
- Variance explained?
- Draft adjustment & reason
Change anything. Any time.
Any step, any rule, any approval. Say what changed. Approve the new version.
- Check receipts & shipments
- Check this customer's historyAdded
- Variance over 5%?Changed
- Draft adjustment & reason
- Buyer approves reorderRepeat customers: skip
- Over $500?
Add a step after “Check receipts & shipments”: check this customer's history and flag anything unusual.
Step added
New rule: Variance over 5% → trace it first.
Rule changed
Repeat customers under the limit don't need my approval anymore.
Approval changed
Saved as version 4. You approved it. The next run follows it. The last runs keep the version they ran on.
Your rules. Exactly.
Written once in plain English. Followed every time.
- Variance over 5%? Trace it first
- Still unexplained? Recount
- Adjustment over $500? Controller approves
Never, on any run
- Write off without approval
- Post without a reason code
- Place a purchase order
- Change min / max levels
Approvals, where you want them
It stops and asks you.
What it built, what it checked, what looks off and what it suggests. Approve, edit, reject, or take the wheel.
from your desk or your phone ↘
Post Zone B adjustments?
The inventory lead approves every adjustment.
Agent suggests: Approve and recount B-31One item needs a look. Everything else checked out.
ZONE B · Cycle count · 11/07
B-14 bearingsReceipt not put away · no adj
B-22 V-belts−2 · damaged
B-31 clamp kits−12 · unexplained
Matches116 of 120 bins
ReorderBearings below minimum
Adjustment−$36.40
Review notes
- B-14 explained by receipt RCV-8812
- B-31 needs a recount before any write-off
- Reason codes from your list
Your team, before and after
| Today | With your agent | |
|---|---|---|
| Count to posted | Next week | Same day |
| Inventory team | Keying counts | Fixing causes |
| Variances | Written off | Traced |
| Stockouts | Found at shipping | Flagged at count |
How many hours can you get back?
Your volume, your times, your labor cost. Estimates, not results.
Bin counteds × (minutes today − minutes with the agent) ÷ 60 × hourly cost
These are example assumptions, not results. Example for a distribution warehouse: minutes per bin cover keying, comparing and tracing. Use your own numbers.
Questions owners ask us
Do we have to buy new software or connect anything?
No. The agent works in the software you already use, with the same screens, keyboard and mouse your team uses, under logins you give it. Nothing to replace and nothing to integrate.
How is the agent built?
You explain the job the way you'd train a new hire: talk or type, and hand over your SOP and a few real examples. Then it does a real one live while you watch and correct it. Your process is saved as a flowchart and a written procedure, and every run follows the version you approved.
Will it write off inventory?
No. It explains what it can, asks for recounts on the rest, and drafts adjustments with reason codes. A person approves before anything posts.
Can we change the process later?
Any time. Add a step, change a rule, move an approval or drop one. Tell the agent what changed, review the new flowchart and save it as a new version.
Where does it run, and is it safe?
On your computers, in your signed-in sessions. Logins are kept in a vault and never shown to the AI. Every run is recorded with screenshots, values read and approvals given.
Which zone should we count first?
Bring last month's count files.
no new system. no integrations. ↗