Exclusions, POS Demand, Replacements, and Bulk Rules

Use explicit controls for products and warehouses that do not follow the normal replenishment workflow. This keeps the planning queue explainable and avoids forcing unrelated exceptions into one global setting.

Exclusions

1. Open Inventory > Niyu AI > Configuration > Exclusions.
2. Choose a Product, Product Template, Product Category, or warehouse-only scope.
3. Select warehouses when the exclusion is limited; leave warehouses empty to apply a product scope to all warehouses.
4. Enter a clear reason and use Open Matching Products or Open Affected Lines.
5. Run the next forecast so the scope is removed from new planning and current matching lines are ignored.

Typical exclusions include non-replenished services, project-only items, customer-specific make-to-order products, contractual stock, discontinued products, and warehouses outside the planning process.

POS Demand

1. Open Settings > Niyu Smart Stock > Forecast Inputs.
2. Enable POS Demand and save.
3. Run a forecast.
4. Open Demand History and confirm POS demand appears separately and maps to the correct warehouse.

Do not enable POS when the same demand is already recorded as Sales Orders in a way that would count it twice.

Obsolete and replacement products

1. Enable Obsolete & Replacement Planning in Settings.
2. Open Inventory > Niyu AI > Configuration > Replacement Planning.
3. Mark the old product Obsolete for Planning.
4. Select an active compatible Replacement Product.
5. Set the Replacement Effective Date, Demand Transfer Policy, and Demand Transfer %.
6. Use Allow Manual Purchase only when deliberate buying of the old SKU is still permitted.
7. Add a reason and run a forecast.

The replacement Action Line shows inherited source products and Demand History separates inherited demand from direct Sales Orders and POS.

Bulk Update Rules

1. Open Inventory > Niyu AI > Configuration > Bulk Update Rules.
2. Prepare a UTF-8 CSV with one supported product identifier per row.
3. Add warehouse or vendor identifiers only when the rule must be narrowed.
4. Include only the fields that should change. Blank planning cells are not intended to erase existing values.
5. Choose Create Missing, Update Existing, or both.
6. Apply the file and review created, updated, skipped, and error counts.
7. Open a sample of resulting rules and verify scope before the next forecast.

Bulk-file practices

• Test a small file in staging before a large import.
• Keep a dated source file and record the business owner.
• Do not mix unrelated policy changes in one upload.
• Check decimal separators, product references, warehouse names, vendors, dates, booleans, and UoM-sensitive quantities.
• After the forecast, use No Planning Rule, Group by Ordering Profile, and rule filters to confirm coverage.