Your ERP stays the system of record. Narada reads a copy of it, every night.
One export to start, then it runs itself. Nothing is installed on your machines, and nothing is ever written back into your ERP.
Every night, the same five steps. Your part is step one, once.
Zip your export folder and drop it. Narada works out what is inside.
Not nine uploads. One file. CSV, Excel or XML, in whatever columns your ERP happens to produce.
What to put in it
Sales history, a stock snapshot and your product list. That is enough to start. Purchase orders, suppliers, customers, receivables, receipts, returns and batch data each switch on more. Narada tells you on your own screen exactly what each one unlocks.
How far back
Twelve to twenty-four months of sales. Six is the floor. Under ninety days the machine-learning checks stay switched off. Under two years, seasonality cannot confirm a repeating peak. It has to see the same December twice. We would rather say that than let you find out later.
Why size is not a problem
A folder of exports compresses to a fraction of itself, so three years of history travels as a small file. Above that, Narada slices a large upload in your browser and reassembles it on our side.
You approve the reading
Narada reads whatever columns come out and works out which is the SKU, the quantity, the cost. It shows you that reading before it uses a single number. You approve it. You never bend your data into our template.
There is no manual tier, and that is on purpose.
Narada runs at night. A file uploaded in the morning is already a day old before it is read. A board that is always a day behind is not a board anyone trusts.
Most ERPs send it themselves
They already know how to email a scheduled report. It goes to a private address, one per data type, that only accepts mail from people on your account. Odoo skips even that: one read-only key and Narada pulls it.
And if yours cannot
We build the automation that does, on your always-on ERP server, before you go live, at no charge. Your laptop plays no part in this and can be switched off. This is the one door we will not leave to a person's morning routine.
Every ERP has one of those two doors, which is the whole reason every ERP is supported. See yours in the finder above, or ask us and we will tell you which door is yours on the spot.
Seven things a spreadsheet cannot do at three thousand products.
Every product, every branch, every night. Named here, with what each one buys you. The full working prints on the row itself.
A slow-moving spare and a fast consumable stop being forecast the same way.
The clever model only wins where it beats a plain average. Where it does not, it does not get used.
Running out once stops teaching the system to order less next time.
A supplier who promises ten days and takes fourteen gets planned at fourteen.
Your fat, fast lines get protected, and you stop paying to protect thin, slow ones. A floor per class stops anything going thinner than your policy allows.
Demand swings and deliveries swing, and both are covered. The buy is sized to last until your next review, not until tomorrow.
A quantity you can actually place, without an hour in Excel.
Your buyer checks the disagreements, not the whole book.
The order book still goes through a person. It just stops costing them a morning.
Only what differs
Every line where the recommended quantity differs from what you normally order for that product is marked. The three thousand rows that agree with you need no attention, and do not get any.
Every row shows its working
The forecast, the lead time and whether that is measured, stated or assumed, and it says which. The service level and why that one. Your buyer can argue with it, which is the point.
Ask it why, in plain English
Ask how a quantity was reached and it walks you through that row's own numbers, step by step. It can only narrate the working it was handed. It cannot invent a reason it was not given, which is why the answer is worth reading.
It is graded on last month
Each forecast carries a range, and that range is scored against what actually arrived. The engine is judged on the promises it already made, not the ones it is making now.
Nothing moves without you
No order is drafted into your ERP, sent to a supplier, or acted on until you click. Narada proposes. You approve.
The order returns as a file your ERP imports. No Excel in between.
Read-only runs in both directions. Narada never writes into your ERP. It hands your ERP a file.
Set the format once
Your column names, your order, your date format, as CSV or Excel. Build it by hand, or upload your ERP's own import template and Narada maps to it. More than one layout, if you import to more than one place.
Then import it
One upload into your ERP, the way you already import anything else. Or send the supplier a PDF from your own address instead.
Or close the loop
That import can be automated too, the same way the data comes in. The file lands where your ERP's import job already looks, on a schedule, and your ERP picks it up on its own. We build that for your ERP at no charge. Narada still never writes into it.
Where the edges are
The limits we would rather you heard from us.
Emailed exports have a ceiling. Keep an attachment under about 30 MB, which most nightly exports comfortably are. Zip it if it is not, or use the upload door, which has no such ceiling.
Weekly is weekly. Zoho's scheduler cannot go below a weekly export. We say so on the table above rather than letting you assume nightly.
A file can still be wrong. If one fails validation we repair it on our side. You will never be asked to re-send it.