Troubleshooting Niyu Smart Stock

Start with the latest Forecast Run, then trace one affected Action Line. Most apparent errors come from stale snapshots, rule scope, incoming supply, ordering cadence, demand events, a planner override, horizon limits, or an execution blocker.

Dashboard is empty or stale

• Confirm the latest Run is Done and its results were applied.
• Check the active company, allowed companies, warehouse coverage, and Action Lines without dashboard filters.
• New orders, deliveries, receipts, stock corrections, and policy changes require a new forecast sync to change the planning snapshot.
• A browser refresh cannot create missing server-side planning records.

Recommendation is lower than expected

• Compare the same protection dates, not only average monthly demand.
• Confirm the intended Ordering Profile is linked by the winning Planning Rule.
• Review stock, reservations, eligible dated RFQs/POs/transfers, safety days, target coverage, and horizon.
• Check Planner Purchase Quantity, including an explicit zero.
• Reconcile stock UoM, purchase UoM, MOQ, Order Step, Case Pack, and supplier constraints.

Recommendation is unusually high

• Open Demand History and check confirmed demand, source split, stockout evidence, and recent event dates.
• Use Demand Review for a detected anomaly. Use a known Demand Event before the run for a promotion, storm, launch, closure, or planned uplift/downturn.
• Do not use Planner Purchase Quantity zero as a historical correction.
• Check duplicated POS/Sales Order demand, replacement demand, wrong warehouse mapping, and broad rule scope.

Ordering Profile appears ignored

• Creating a profile alone changes nothing. Link it on the matching Planning Rule.
• Read the selected rule and Applied Rule Summary on the Action Line.
• Check company, warehouse, vendor, product scope, active dates, and priority.

Stockout days do not adjust demand

• Open Settings > Niyu Smart Stock > Forecast Inputs and check any Planning Rule override.
• Flag only warns without estimating. Estimate constrained demand needs supported backend evidence. Ignore intentionally skips availability.
• Availability Unknown means dependable warehouse history was unavailable for that result.

Transfer is missing or blocked

• Check global Internal Rebalancing, winning rule strategy, transfer-in/out permissions, network, roles, route, and timing.
• A donor may be protected for its own demand, reservations, cycle, safety, incoming supply, or outbound commitments.
• Read the deterministic transfer explanation and any live revalidation blocker.

Decimals or surprising RFQ quantity

• Forecast demand may remain decimal; executable quantities follow UoM precision.
• Check purchase-UoM conversion, MOQ, Order Step, Case Pack, supplier packaging, and schedule rounding.
• Supplier case-pack rules do not apply to internal transfers.

Demand History differs from current Odoo

• It is a snapshot as of the selected run.
• Open another run or start a new forecast for current source data.
• Opening Demand History itself does not consume a refresh.

Upgrade fails but reinstall works

• Do not use uninstall/reinstall as the normal upgrade path because module-owned records can be removed.
• Deploy the complete addon version and restart Odoo before upgrading Python changes.
• Use the first model, file, view, or action named in the full error.
• Refresh web assets after a successful upgrade that changed JavaScript, QWeb, or styles.

Support evidence

• Odoo version, Niyu version, company, warehouse, and SKU.
• Latest Run name, state, time, horizon, message, and source.
• Action Line calculation tabs, selected Planning Rule, Ordering Profile, Demand Event, and linked documents.
• Expected result, actual result, and the exact dates and UoMs compared.
• Complete server or browser error with timestamp; never include the API key.