“We order too late, so we expedite”
Purchasing knows the supplier takes ten weeks. The item master still says four. Master planning believes the item master, so every order starts late and finishes expensive.
Planning health for Dynamics 365
Your planning system is doing exactly what you configured. That is the problem.
Lead times, safety stock, minimum order quantities and coverage groups were set once — before the supplier changed, before the volumes moved, before the product went end-of-life. Neopiq finds the settings that no longer match what actually happens, quotes the numbers that prove it, and names the change to make.
It runs inside your browser. No account, no install, nothing uploaded — you can disconnect from the network first and it still works. Why that is true.
Example finding
Configured 30 days. Received in 70. No safety stock.
- Item ITM-X123, vendor VEN-045
- Lead time in the item master: 30 days
- Actual receipts: 69.88 days on average, over 8 purchase receipts
- Safety stock: zero
- Owner on record: planner PLN-02
Master planning proposes supply too late by design, and there is no buffer between the gap and the customer. It looks like a supplier problem. It started as a parameter.
This is the worked example in the sample data that ships with the free check. The data is synthetic, not a customer. Open the tool and the same finding appears in one click.
You have heard these sentences in your own meetings
Each one has the same shape: the system is blamed for a decision that a setting made years ago.
“Full of the wrong stock, out of the right stock”
A minimum order quantity set for a product that used to sell ten times faster. A forecast that keeps consuming demand for an item you stopped selling. The stock is the symptom; the parameter is the cause.
“The planners override the system”
When planned orders stop making sense, people plan in a spreadsheet and key the answer back in. Every manual override is a vote of no confidence in a setting somebody should have changed.
What comes back is a work list, not a dashboard
Every finding is written the way a senior planner would write it, and it is addressed to somebody. There is no chat window and nothing to interpret.
What is wrong, on which item
Named item, vendor and site. Not a score, not a heat map — the specific object somebody has to open in D365 tomorrow morning.
The numbers it used
The configured value, the observed value, how many transactions it was measured over, and the threshold it crossed. You can check the arithmetic in Excel and disagree with it.
Impact, likely cause, and the fix
What this costs the business, the most likely reason the setting drifted, the change to make, and the planner or buyer on record as the owner.
What the free check looks at today
Twenty-six checks over eleven extracts a planner can pull out of D365 without help: items, vendors, purchase receipts, sales order lines, on-hand, production orders and routes, forecast, coverage groups, reduction keys and planners.
Lead time against reality
Configured lead time versus what receipts actually did — whole-horizon gaps, items drifting away from their own history, values far outside their peer group, and item lead times that contradict the vendor record.
Safety stock and service
Safety stock against demand volatility and the service target, on-time delivery that is measurably falling, service levels sitting below target, and supplier confirmations that are not worth planning on.
Order quantities and excess
Minimum order quantities that buy years of demand, and the months of cover that produced — measured per item and per site, because an item can be healthy in one plant and drowning in another.
Forecast and consumption
Forecast running above real order intake, forecast lines with no reduction key to consume them, and obsolete items still being forecast and still holding stock.
Planning policy that points nowhere
Coverage groups and reduction keys that are missing, or that reference a record which no longer exists. Manufactured items with no route; purchased items carrying one.
Ownership and sourcing gaps
Active planning items with no planner, no supplier, no site or no item group — and planner references pointing at people who have left.
The full list, area by area, and what each check actually compares
The security conversation is a short one
The free check is a web page that reads your CSV files locally. There is no upload, no account, no login, no cookie, no analytics and no server to send anything to. Nothing is stored either — closing the tab is the delete button.
You do not have to take that on trust. Open your browser's network tab while it runs, or pull the network cable first. Your item master and your vendor lead times are commercially sensitive; that is exactly why the first useful answer should not require a data-processing agreement.
No procurement step. No security review. No integration project. One person and one export.
What this is not
- Not a chatbot. There is no prompt and no model guessing at your business. The same export produces the same findings, in the same order, every time.
- Not another dashboard. A report shows you the shortage. This names the setting that caused it — including the ones nobody thought to build a report for.
- Not a data quality score. A lead time of 30 days is present, numeric and valid. It passes every completeness check ever written. It is still wrong.
- Not a robot in your ERP. Nothing is written back. Every finding is a hypothesis with the evidence attached, and a person decides.
Start free, and only pay when there is something worth paying for
One step at a time, and each step is a decision you make after the previous one has already been useful. Each step is also a pricing tier, named for the level it unlocks.
-
Available today — the free check
Unlimited local checks on your own extracts, on the Free tier. Nothing to approve, nothing to install, nothing transferred. This is the only part of the product you can use today, and it is the part that has to earn everything after it.
-
In development — findings explained and written up
The plan is that the local check keeps doing the reading and the arithmetic, and a cloud service turns the result into a written report and learns which patterns matter across customers — without your records ever being part of what is sent. That is the Trial tier, and it is not open yet.
-
Planned — the heavy work, inside your own Azure
Optimisation, simulation and repair at full data volume are intended to run in your own Azure subscription, under your own controls, with the compute on your Microsoft agreement. That is the Enterprise tier. It is a direction, not a product you can buy today.
What each tier unlocks, and what is honestly not available yet
Your own export will settle this faster than we can
Export the tables, drop them on the page, read the findings. If none of them is worth acting on, it cost you nothing. If one of them is, you already know what to do on Monday.