| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Inventory (stock)
• Purchase (purchase) • Sales (sale_management) • Discuss (mail) • Invoicing (account) |
| Lines of code | 3911 |
| Technical Name |
niyu_smart_stock |
| License | OPL-1 |
| Website | https://niyulabs.com |
| Versions | 16.0 17.0 18.0 19.0 |
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Inventory (stock)
• Purchase (purchase) • Sales (sale_management) • Discuss (mail) • Invoicing (account) |
| Lines of code | 3911 |
| Technical Name |
niyu_smart_stock |
| License | OPL-1 |
| Website | https://niyulabs.com |
| Versions | 16.0 17.0 18.0 19.0 |
Niyu Forecast
for Odoo
Know what to buy, what to move, and when to receive it — before stock becomes a problem.
Niyu Forecast reads your Odoo sales, stock, purchase, and warehouse data. Then it turns that into clear planning actions: buy this quantity, transfer from this warehouse, split transfer and purchase, plan cargo-ready and receipt dates, and create RFQs from the recommendation.
Not just a demand number. A planning decision.
Most tools stop after showing a forecast. Niyu Forecast goes further. It answers what to buy, how much to buy, whether stock can be moved first, when goods should arrive, and why the recommendation exists.
The old way: check
everything manually.
Stockouts become lost sales
One missed item can stop a sale. Manual guessing means the team is always one demand spike away from an empty shelf.
Overbuying blocks cash
Dead stock is money sitting on shelves. If the team overestimates slow-moving products, cash gets trapped.
Excel cannot scale
Exporting sales, checking stock by warehouse, checking POs, guessing demand, and repeating it for thousands of products is slow and risky.
You do not need another forecast table. You need one planning view that tells your team what to fix first.
Open one planning view.
Know the next action.
Niyu Forecast gives inventory teams one practical place to see products that need buying, stock that should be moved internally, setup blockers, warehouse pressure, scheduled receipts, and forecast reasons.
Buy only what needs buying
The module checks demand, stock, incoming supply, safety stock, lead time, MOQ, and order multiples before suggesting a practical buy quantity.
Move stock before buying more
If one warehouse is short and another has spare stock, Niyu Forecast can suggest an internal transfer before creating a purchase recommendation.
Split transfer and purchase
Real inventory issues are rarely one action. The right answer can be: move what you already have, then buy only the remaining gap.
Questions inventory teams ask.
Answers Niyu gives.
| Question | Niyu Forecast answers | Practical result |
|---|---|---|
| What should I buy? | Buy recommendation | Clear purchase action |
| How much should I buy? | Suggested quantity | Less overbuying |
| Can I move stock instead? | Internal transfer suggestion | Use existing stock first |
| Do I need both transfer and purchase? | Split action | Transfer available stock, buy the gap |
| When should I expect it? | Lead time and receipt date | Earlier, cleaner replenishment |
| Why is this recommendation here? | Forecast model and reason | Higher buyer trust |
Connect Niyu Forecast
inside Odoo.
Install the module, open Inventory Settings, enter your API key, save, and run the initial sync. The module then appears under the Niyu AI menu for planning, actions, rules, runs, and lead-time analysis.
Use this screen to connect your database to the forecasting server, review plan limits, set forecast horizon, exclude archived products, and control lead-time learning behavior.
Your inventory
control room.
See urgent actions, buy budget needed, warehouse pressure, internal rebalance opportunities, setup blockers, and the latest forecast run status in one place.
Every product gets
a clear next step.
Review buy now, transfer now, transfer + buy, setup needed, watch, and ignored lines. Users do not need to interpret a raw forecast table. The next action is already written.
From recommendation
to draft RFQ.
Review the recommendation, then create or update draft RFQs directly from action lines. Scheduled purchase lines can carry cargo-ready dates, transit time, and expected receipt dates.
The result is not a report.
It is the next decision.
Niyu Forecast turns demand, stock, lead time, incoming supply, and warehouse balance into clear work for the inventory team.
Buy only what still needs buying
Forecast says 120 units may be needed. You already have 50 in stock and 30 incoming. Niyu recommends only the remaining gap.
Move stock before buying more
If Delhi is short and Mumbai has spare stock, the module suggests transfer first, then purchase only what is still missing.
Split: transfer some, buy some
Real inventory decisions are mixed. Niyu supports transfer + buy actions directly instead of forcing one blind recommendation.
Plan cargo-ready and receipt dates
Use simple lead time or split it into cargo-ready days and transit days. Buyers see when to order and when goods should arrive.
Split large buys into batches
Need 900 units but not all today? Create scheduled batches with separate expected receipt dates.
Trust the reason, not only the number
Action lines can show the model used, model reason, guardrails, and confidence note for better buyer review.
Short 80 units? Do not blindly buy 80.
If Warehouse A is short 80 units and Warehouse B has 30 spare units, Niyu Forecast can suggest: transfer 30 and buy 50.
Planning Overview
Your inventory control room. Show urgent actions, buy budget needed, internal rebalance, warehouse pressure, setup blockers, and latest forecast run status.
Action Lines
Every product gets a clear next step: buy now, transfer now, transfer + buy, setup needed, watch, or ignored.
Transfer + Buy Recommendation
Use available stock before spending more. Transfer what is available, then buy only the remaining quantity.
Planning Rule
Control how each product, category, vendor, or warehouse should be planned using safety stock, lead time, MOQ, and purchase schedules.
Purchase Schedule Profile
Split large buys into planned receipt batches for importers, manufacturers, warehouse capacity planning, and cash-flow control.
Forecast Engine Note
Show the model used and reason so the buyer does not blindly trust a number.
Lead Time Suggestions
Review suggested lead times based on purchase receipt history. Nothing is applied automatically.
Every submenu has a job.
Here is what it solves.
Planning Overview
See buying pressure, warehouse pressure, setup blockers, action counts, and latest run status. Use it to decide what to work on today.
Action Lines
Review product, warehouse, forecast, stock, incoming stock, suggested buy, transfer quantity, vendor, reason, and execution status.
Planning Rules
Tell the system how your business buys: safety stock, MOQ, order multiple, vendor, warehouse, lead time, and schedule profile.
Purchase Schedule Profiles
Split large purchase suggestions into two batches, three monthly batches, first-batch-larger plans, or separate RFQs by batch.
Lead Time Suggestions
Review current lead time, suggested lead time, average, median, p80, sample count, and confidence before applying changes.
Analyze Lead Times
Run a limited analysis by date range, vendor, warehouse, category, max PO lines, max suggestions, and minimum receipt count.
Runs
Track forecast jobs. Confirm whether a forecast started, completed, failed, or is still processing.
Exclusions
Keep discontinued products, special-order items, non-stock exceptions, and unwanted products out of planning.
Bulk Update Rules
Create, update, clear, or deactivate thousands of planning rules by CSV without clicking rule by rule.
Settings
Connect your API key, review plan limits, control forecast horizon, exclude archived products, and manage lead-time learning.
Daily inventory problems.
Cleaner answers.
Avoid unnecessary buying
You are about to buy 100 units. Niyu Forecast checks all warehouses and finds 40 units available elsewhere.
Import planning
A supplier takes 20 days to prepare goods and shipping takes 35 days.
Split large purchase
Forecast says 900 units are needed, but the warehouse does not need every unit at once.
Find setup problems early
A product needs buying, but no vendor is configured.
Trust the recommendation
A product has irregular sales. Instead of forcing a regular forecast model, Niyu can treat it as intermittent demand and show the reason behind the action. The buyer understands why the recommendation exists.
The feature is the outcome.
Not the button.
Forecast to action
Turn demand into buy quantity, transfer quantity, split actions, receipt dates, and RFQs.
Multi-warehouse planning
See where inventory is short, where it is available, and where it should move.
Purchase planning inside Odoo
Create RFQs from action lines with schedule, cargo-ready date, transit time, and expected receipt date.
Rules for real businesses
Use simple rules for normal products and advanced rules for imported, expensive, slow-moving, or high-priority products.
Built for large catalogs
Use CSV imports to configure thousands of products without editing rule by rule.
Safer forecasting workflow
Supports multiple models, job tracking, usage limits, temporary result storage, and daily quota tracking.
Forecasting is useful only when it understands
how inventory really works.
Products get replaced. Some warehouses should not be planned. Retail sales happen in POS. Teams work in different languages. Niyu AI now handles these real cases inside Odoo.
New product. Old demand history.
When an old product is replaced by a new one, the new product often has little sales history. A normal forecast sees low demand and recommends too little stock.
Product A is no longer purchased automatically. Product B can inherit Product A’s demand history.
Replacement products get realistic purchase recommendations from day one. Buyers can also see when demand was inherited from an obsolete item.
Not every warehouse should drive purchasing.
Some warehouses should not affect replenishment planning. Niyu lets you exclude a full warehouse, or exclude selected products and categories only inside selected warehouses.
If a warehouse should not influence planning, Niyu will not use it for forecast demand, stock pressure, or purchase recommendations.
Retail sales should count too.
Many businesses sell through both Sales Orders and Point of Sale. If POS sales are ignored, fast-moving retail products can look slow in the forecast.
A product selling every day at the counter will no longer look quiet just because it has fewer sales orders. POS demand is optional, so existing users can keep their current behavior.
Use Niyu in the language your team already uses in Odoo.
Niyu AI follows the user’s Odoo language setting. Menus, fields, buttons, planning labels, and help text are translated for major Odoo markets.
Buyers, warehouse teams, and managers can understand the recommendation in their own Odoo language.
Español
Niyu AI ahora está disponible en español para equipos que gestionan compras, inventario y planificación dentro de Odoo.
Français
Niyu AI est maintenant disponible en français pour les équipes qui planifient les achats, les stocks et le réapprovisionnement dans Odoo.
Deutsch
Niyu AI ist jetzt auf Deutsch verfügbar, damit Einkauf und Lagerplanung direkt in Odoo klarer arbeiten können.
Português
O Niyu AI agora está disponível em português para equipes que planejam compras, estoque e reposição no Odoo.
العربية
يدعم Niyu AI الآن اللغة العربية لفرق المشتريات والمخزون التي تعمل داخل Odoo.
中文
Niyu AI 现在支持中文，帮助团队在 Odoo 中更清楚地管理库存、采购和补货计划。
Also included: Italian, Dutch, Polish, Turkish, Indonesian, Vietnamese, Japanese, Korean, and key regional Spanish and Portuguese variants.
Niyu does not stop at predicting demand.
It turns demand into planning decisions.
It helps your team answer the real operational questions behind every forecast.
Which product should be bought?
Which warehouse should be ignored?
Which product replaced an old item?
Which sales channels should count?
Which RFQ should be created?
Which team member can understand it in their own language?
That is the difference between a forecast report and a practical inventory planning system.
Start free.
Choose your planning scale.
Every plan includes all features. The difference is product limit, warehouse limit, daily refresh allowance, and support level.
Free
For trying it out before upgrading. It also works well for very small businesses.
- ✔ 50 products
- ✔ 2 warehouses
- ✔ All features
- ✔ 2 manual/day
- ✔ 1 scheduled/day
- ✔ Standard support
Pro
For small businesses that need simple daily inventory planning.
- ✔ 2,000 products
- ✔ 3 warehouses
- ✔ All features
- ✔ 2 manual/day
- ✔ 1 scheduled/day
- ✔ Priority support
Business
For growing businesses with larger catalogs and active purchase planning.
- ✔ 15,000 products
- ✔ 4 warehouses
- ✔ All features
- ✔ 2 manual/day
- ✔ 1 scheduled/day
- ✔ Priority support
Enterprise
For large multi-warehouse operations that need custom planning limits and priority support.
- ✔ Large product count
- ✔ Large warehouse count
- ✔ All features
- ✔ Custom refresh limits
- ✔ Priority support
- ✔ Contact us
Need a key or want a higher limit?
Email us with your Odoo version, product count, and required sync frequency.
Email info@niyulabs.comHow to use Niyu Forecast.
From API key to RFQ.
Install, connect, run, review, execute.
The buyer does not need to learn a forecasting tool. The module adds a practical planning workflow inside Odoo: run forecast, review action lines, create RFQs or transfers, and refine rules when needed.
Install the module
Install the module, open Inventory Settings, find the Niyu Forecast section, enter your API key, save, and click Run Initial Sync.
Run your first forecast
Go to Niyu AI → Run Sync Now. After the run completes, open Planning Overview to see status, pressure, blockers, and actions.
Review Action Lines
Review Buy Now, Transfer Now, Transfer + Buy, Setup Needed, Watch, and Ignored lines. This is the main worklist.
Create RFQs
Open a buy action line and click Create RFQ. The module creates or updates a draft RFQ and links it back to the action line.
Create Planning Rules
Use rules for products, categories, warehouses, or vendors that need MOQ, multiples, safety stock, lead time, or schedule behavior.
Use split lead time
Set Lead Time Mode = Cargo Ready + Transit. Example: 20 cargo-ready days + 35 transit days = 55 total lead-time days.
Use Purchase Schedule Profiles
Create profiles like Import - 3 Monthly Batches. Assign the profile to a planning rule so matching action lines get schedule rows.
Bulk update planning rules
Upload CSV to create, update, clear, or deactivate rules for many products at once.
Use lead-time learning
Enable it in Settings, analyze purchase history, then review and apply suggestions manually. Nothing is applied automatically.
Exclude archived products
Enable Exclude Archived Products in Settings so archived products are not sent for new forecasting and can be marked ignored.
FURN_001,simple,14
default_code,lead_time_mode,cargo_ready_days,transit_days
FURN_002,split,20,35
default_code,purchase_schedule_profile
FURN_003,Import - 3 Monthly Batches
default_code,operation
FURN_004,deactivate
FURN_005,clear
Everything you need to know.
✶ Does it work with Odoo Community?
Yes. Niyu Forecast is designed to work with Odoo Community and Odoo Enterprise.
✶ Does it work on Odoo.sh and on-premise?
Yes, if the Odoo instance can make outbound requests to the Niyu forecasting server.
✶ Do I need an API key?
Yes. The API key connects your Odoo database to the Niyu forecasting and planner server. Email info@niyulabs.com to get one.
✶ Is the module free?
Yes. The Free Lifetime plan includes 20 SKUs, one automatic forecast per day, one manual forecast per day, and a 30-day forecast horizon.
✶ Do you store sales history permanently?
No. Sales history is sent for forecast processing. Forecast result payloads are temporary and used to return planning recommendations.
✶ What data is sent?
The module sends the data needed for forecasting and planning, such as product demand history and warehouse context. Customer names are not needed for forecasting.
✶ Can it suggest transfers?
Yes. If another warehouse has available stock, the module can suggest internal transfer before buying.
✶ Can it suggest both transfer and buy?
Yes. It can suggest transferring available stock and buying only the remaining quantity.
✶ Can I split purchases?
Yes. Use Purchase Schedule Profiles to split one suggested buy into multiple planned batches.
✶ Does it replace Odoo reordering rules?
It does not need to replace them immediately. You can use Niyu Forecast as a smarter planning layer for products where normal reorder rules are not enough.
✶ Is it only for large companies?
No. Small users can use the free plan. Larger users can use advanced rules, multi-warehouse planning, purchase schedules, and bulk CSV setup.
✶ Is this GDPR friendly?
Niyu acts as a data processor for forecast processing. Data is used to calculate forecasts and planning recommendations. It is not sold or used for unrelated purposes. For DPA or stricter processing terms, contact info@niyulabs.com.
Stop guessing stock.
Start planning with Niyu Forecast.
Turn Odoo sales and stock data into clear buy, transfer, and receipt plans. Start with the Free Lifetime plan.
|
NIYU LABS
|
Queries & Support
info@niyulabs.com
|
Odoo Proprietary License v1.0 This software and associated files (the "Software") may only be used (executed, modified, executed after modifications) if you have purchased a valid license from the authors, typically via Odoo Apps, or if you have received a written agreement from the authors of the Software (see the COPYRIGHT file). You may develop Odoo modules that use the Software as a library (typically by depending on it, importing it and using its resources), but without copying any source code or material from the Software. You may distribute those modules under the license of your choice, provided that this license is compatible with the terms of the Odoo Proprietary License (For example: LGPL, MIT, or proprietary licenses similar to this one). It is forbidden to publish, distribute, sublicense, or sell copies of the Software or modified copies of the Software. The above copyright notice and this permission notice must be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
Please log in to comment on this module