Raises purchase orders against min/max levels and lead times, and holds anything above your budget threshold for a buyer to sign off.
Someone runs a report, eyeballs it against gut feel, and raises POs for whatever looks low.
Your buyer only sees the ones above threshold, or the ones that look wrong.
On-hand and on-order quantity are checked against min/max for every item.
Each supplier's actual recent lead time is used, not a static default.
Quantity, supplier, and delivery date are calculated and filled in.
Below threshold, it releases; above it, a buyer signs off first.
The PO is monitored against the promised date, ready for the receiving agent.
It's priced per engagement, based on SKU count and location count, plus the Copilot Credits it consumes at runtime. We size both before you commit.
A demand spike, a lead time that's drifted a lot, or a spend above your threshold all route to a buyer rather than being released automatically.
Yes, it works from the suppliers, min/max levels, and lead times already configured in Business Central or F&O, it doesn't invent its own supplier list.
Most replenishment agents go live within two to three weeks once your min/max levels and supplier lead times are in reasonable shape, that data quality is the real variable.
The demand planning agent reruns the forecast itself; this one executes purchase orders off whatever forecast and stocking levels are current. Most sites run both together.
Tell us how your stocking levels are set today. We will tell you honestly what a realistic setup looks like.
Talk through whether this fits your process as it actually runs.
Four minutes, no email required.