Operating Routine, FAQ, and Glossary

Use this operating routine to keep planning current without reviewing every product individually. The queues are designed to move planners from freshness, to exceptions, to approved execution.

Daily planning routine

1. Open Inventory > Niyu AI > Workbench > Planning Overview.
2. Confirm Last Sync, Latest Run, company, and warehouse coverage.
3. Open Setup Required and fix blockers that prevent approved work.
4. Review due Buy, Transfer, and Transfer + Buy Action Lines. Read the recommendation explanation on exceptions.
5. Use Purchase Review for planner quantity decisions and Vendor Order Review for consolidated periodic orders.
6. Create draft RFQs and internal transfers only after quantities and timing are approved.
7. Review Execution Progress and linked documents before ending the session.

Weekly control routine

• Review ignored lines, manual planner quantities, and suggestions that changed since the last run.
• Review Stockout Affected, Availability Unknown, donor protection, multiple-donor, and horizon-blocked queues.
• Check upcoming recurring and manual order windows by vendor and Ordering Profile.
• Review missing vendors, missing rules, transfer routes, purchase schedules, and UoM setup.
• Check failed or delayed forecast runs and remaining account capacity.

Monthly policy routine

• Analyze supplier lead times and decide whether to accept suggestions through controlled updates.
• Review Planning Rules, Ordering Profiles, Transfer Networks, exclusions, replacements, and bulk-created rules.
• Validate vendor MOQ, case packs, purchase UoMs, prices, currencies, and company ownership.
• Review Inventory & Service, Forecast Quality, and Planning Impact after enough evidence has matured.
• Archive obsolete rules and profiles only after confirming no active planning scope depends on them.

Frequently asked questions

Does Niyu place purchase orders automatically?

No. It prepares recommendations and creates draft RFQs only when an authorized user runs the relevant action. Purchase confirmation remains an Odoo approval decision.

Does Niyu complete internal transfers automatically?

No. It can create and confirm the internal picking after live revalidation, but warehouse users still execute and validate the physical movement in Odoo.

Does opening Demand History consume a forecast refresh?

No. Demand History reads the stored planning snapshot for the selected run.

Why is purchase quantity different from forecast demand?

Forecast demand is one input. The executable purchase quantity also accounts for available stock, dated incoming supply, eligible transfers, review timing, safety policy, planner overrides, stock and purchase UoMs, MOQ, Order Step, Case Pack, and supplier constraints.

Can a planner deliberately set purchase quantity to zero?

Yes. An explicit zero is preserved as a manual decision. Add a reason so later reviewers understand it. Reset the field when the system suggestion should apply again.

Why did creating an Ordering Profile change nothing?

Profiles are reusable policy templates. A matching Planning Rule must link the profile to products, vendors, categories, warehouses, or another supported scope.

Can forecast values be decimal?

Yes. Expected demand can be decimal. RFQs and transfers use executable quantities that respect the configured UoM precision and ordering constraints.

How should made-to-order, project, service, seasonal, or backorder products be handled?

Use Planning Rule overrides or exclusions that reflect how demand is captured. Stockout adjustment is most useful for normal stocked products where unavailable stock suppresses recorded sales.

Why are the Performance tabs blank after installation?

Performance measures require durable evidence and mature evaluation windows. Collecting Baseline, Missing Cost Data, and Insufficient Samples are expected states until the required records exist.

Does Niyu delete sales when correcting stockout bias?

No. Recorded demand remains intact. When enabled and supported by evidence, stockout handling can only add a conservative estimate to confirmed zero-sales stockout days.

Are current Action Lines historical evidence?

No. Action Lines represent the current planning snapshot. Forecast Evaluation, Delivery Facts, Inventory Snapshots, and Impact Events retain the durable records used for performance evaluation.

Glossary

• Action Line: the current product-warehouse planning decision and its execution status.
• System Suggested Purchase: the read-only purchase quantity calculated by the current plan before an explicit planner decision.
• Planner Purchase Quantity: an editable, persistent quantity chosen by a planner, including a deliberate zero.
• Planning Rule: the scope-resolution record that applies product, vendor, category, warehouse, timing, stockout, and rebalancing policy.
• Ordering Profile: a reusable continuous, recurring, or manually scheduled purchasing cadence.
• Purchase Schedule Profile: rules for splitting a planned purchase into valid dated quantities.
• Order Step: the allowed increment used to round executable purchase quantity.
• Case Pack: the supplier pack multiple applied to purchases, not internal transfers.
• MOQ: the supplier or rule minimum order quantity.
• Stock UoM: the product quantity unit used for internal demand, supply, stock, and transfer calculations.
• Purchase UoM: the unit placed on an RFQ or purchase order after conversion from the stock UoM.
• Protected window: the dated demand period a recommendation is intended to cover.
• Review date: the date a recurring or manual purchasing decision is scheduled.
• Preparation window: the number of days before a review date when work should enter the planner queue.
• Donor protection: the inventory retained at a source warehouse for its own demand, commitments, and safety needs.
• Forecast horizon blocker: a warning that the available forecast does not extend far enough to support the required protected window.
• Stockout-censored: an evaluation state where unavailable stock may have limited observed demand.
• WAPE: total absolute forecast error divided by total actual demand for eligible mature observations.
• Bias: signed forecast error; positive is over-forecast and negative is under-forecast.

Escalation sequence

1. Read the Action Line explanation and setup status.
2. Confirm the selected Planning Rule and Ordering Profile.
3. Reconcile stock, incoming supply, transfers, dates, and UoMs.
4. Open the Forecast Run and Demand History snapshot.
5. Collect the support evidence listed in the Troubleshooting guide before escalating.