Freshroots Reorder Planner
Reorder, rethought.
Weekly SAP sales and stock in. One approval from Raghav. Purchase orders in Zoho.
Sign in to see the latest run's numbers.
How it works
Ten components. Six steps. One approval.
Step 1 of 6 · Components 1 · 2 · SAP · Database
Data.
Twice a week the Analyst runs the plan on the latest SAP data, or uploads new SAP files. Each run stores them with a file hash, so every number traces back to its source.
5 files · 12 checks
- Data: Twice a week the Analyst runs the plan on the latest SAP data, or uploads new SAP files. Each run stores them with a file hash, so every number traces back to its source.
- Rules: The rule book, config.yaml and the festival calendar load with every run, version-stamped. Raghav's thresholds live in config, never in code.
- Predict: A deterministic engine, not a model, works out cover, trend and festival uplift, then applies the decision table. Same inputs, same plan, byte for byte.
- Reasoning: Gemini explains each SKU in plain language. It never sets a number. Any figure it writes that the engine didn't compute is thrown out.
- Raghav approves: Raghav sees the plan with every flagged SKU called out, then does one thing: approve or reject. Nothing is ordered without that approval.
- PO: The moment Raghav approves, one purchase order per supplier is created in Zoho Inventory. PDF and Excel copies stay available for procurement.
The principle
AI vs Expert → Expert wins.
The engine recommends and Gemini explains. Nothing reaches Zoho until Raghav approves the plan, and a rejected plan orders nothing.
Guardrails
No invented numbers.
- Every threshold comes from config.yaml.
- No prices, lead times or stock on order are guessed.
- No PO exists until Raghav approves.
- Zoho gets exactly the approved quantities.