• Minimum stock is a manual floor used by applicable planning paths.
  • Maximum stock is a manual planning constraint when Product maximum stock is enabled.
  • Safety stock is calculated for uncertainty.
  • Order Up To is a calculated planning target.

Task 1 — Set Product Minimum and Maximum stock

Purpose

Add or change manual stock boundaries for one Product while keeping them distinct from calculated planning values.

Prerequisites

  • Open the intended Product and have permission to edit it.
  • Confirm whether the Product maximum-stock feature is enabled before entering Maximum stock.
  • Review current stock, incoming supply, and the Product's existing planning settings.
  • Wait for Product Settings to finish loading.

Steps

  1. Open Products and select the Product.
  2. Open Product Settings and select Edit.
  3. Enter Minimum stock, Maximum stock, or both when the applicable controls are available.
  4. When both values are set, keep Minimum below Maximum.
  5. Review the pending values against the Product's planning strategy.
  6. Continue to Task 2 to save or discard the changes.

Fields and columns

This is a Product Settings form, not a table:

  • Minimum stock — an optional manual floor.
  • Maximum stock — an optional manual planning constraint shown when the feature is enabled.
  • Safety stock and Order Up To — calculated values shown elsewhere and not replacements for the manual fields.
  • If neither manual value is configured, the Product view shows Not set.

Expected result

The intended Product contains valid pending Minimum and/or Maximum values, or remains unchanged when the controls are unavailable or the values are not approved.

Limitations

  • A manual Minimum is not another name for Safety stock.
  • Maximum stock is not a guaranteed physical ceiling. Current stock, incoming supply, manual orders, pack sizes, delivery timing, and other events can produce a different real quantity.
  • Saving a constraint does not guarantee an immediate order or a particular purchase-advice quantity.
  • Final advice can also depend on forecast, service level, stock position, Lead time, Reorder period, Supplier eligibility, MOQ, Lot Size, Minimum order value, and current processing state.
  • A manual Minimum can conflict with a phase-out objective; phase-out and Ignore are separate states.

Errors and recovery

  • If a value is rejected, correct it using the validation shown by Product Settings and check the relationship between Minimum and Maximum.
  • If Maximum stock is missing or locked, verify feature configuration and Product permission rather than entering a substitute field.
  • If Product Settings are loading or saving, wait for the state to finish before editing again.

Task 2 — Save or discard Product constraint changes

Purpose

Persist valid manual stock constraints or leave the Product with its previous saved values.

Prerequisites

  • Review the Product and pending values from Task 1.
  • Correct all visible validation.
  • Have Product edit access and wait for loading or saving to finish.

Steps

  1. Select Save when the pending Minimum and Maximum values are valid.
  2. Wait for save feedback and verify the Product shows the persisted values.
  3. Select Cancel if the pending changes should be discarded.
  4. Confirm that Cancel leaves the saved Product values unchanged.
  5. Review purchase advice only through the applicable Product and planning views; do not infer an order from the save button.

Fields and columns

  • Save and Cancel — persist valid constraints or discard pending Product edits.
  • Minimum stock, Maximum stock, and validation — define the values and whether the form can be saved.

The Product editor provides Save and Cancel. There are no table columns in this task. Verify the Product identity, Minimum stock, Maximum stock, Safety stock, and Order Up To context after saving or cancelling.

Expected result

Save stores the valid manual constraints for the selected Product. Cancel discards applicable pending edits. The Product remains unchanged when validation or the save request fails.

Limitations

  • A saved constraint is one planning input among several and does not promise immediate visibility in advice.
  • No universal processing, recalculation, or overnight timing is established.
  • Removing a manual floor may be necessary when phasing out a Product, but this task does not change phase-out or Ignore state automatically.

Errors and recovery

  • If Save is disabled, check permissions, Product state, feature locks, validation, loading, and whether there are valid pending changes.
  • If Save fails, reload or reopen the Product and use the persisted values as the source of truth before retrying.
  • If advice remains unexpected, inspect stock position, incoming supply, forecast, Supplier constraints, and current planning state instead of repeatedly saving the same constraint.