{"slug":"settings-algorithm-section","sourcePath":"settings-algorithm-section.md","title":"Configure Algorithm settings","status":"reviewed","editorialStatus":"customer-ready","publicationBlocker":"","publishable":true,"needsReview":false,"reviewReason":"","category":"settings","lastReviewed":"2026-09-29","excerpt":"Use Settings → Algorithm to review forecast-related controls for the selected webshop. The fields shown and whether they can be edited depend on permissions, edition, enabled simulator…","wordCount":799,"readingMinutes":4,"articleType":"How-to guide","qualityFlags":[],"searchText":"configure algorithm settings use settings → algorithm to review forecast-related controls for the selected webshop. the fields shown and whether they can be edited depend on permissions, edition, enabled simulator… configure algorithm settings use settings → algorithm to review forecast-related controls for the selected webshop. the fields shown and whether they can be edited depend on permissions, edition, enabled simulator features, loading, saving, and temporary settings locks. task 1 — configure algorithm controls purpose set the available algorithm inputs deliberately for the selected webshop without treating a field label or example value as a guaranteed forecast outcome. prerequisites - select the intended webshop and open settings → algorithm. - have settings edit access for changes; view-only users can inspect values. - confirm whether the simulator feature is enabled before looking for simulator-only fields. - wait for the section to finish loading. - use the current visible validation and field explanation as the authority for the account. steps 1. review the persisted algorithm values before editing. 2. set yearly seasonality only when the intended value is known and valid. 3. choose the appropriate outlier filtering and wholesale options when they are available. 4. if the simulator controls are shown, enter the applicable sell order threshold and history length. 5. correct visible validation and compare the pending values with the approved planning strategy. 6. leave the fields unchanged if a feature lock, account boundary, or missing source data makes the intended effect unclear. 7. continue to task 2 to save or undo the pending changes. fields and columns this is a settings form, not a table: - yearly seasonality — required in the current form, with a minimum of 0, maximum of 1, and step 0.1. - outlier filtering — controls whether abnormal sales spikes are filtered in the applicable forecasting path. - wholesale — enables the applicable wholesale demand treatment; it is locked in lite in the current experience. - sell order threshold — where shown, a required non-negative whole number used by the applicable classification path. - history length — where shown, a required whole number from 30 through 365 days. expected result the selected webshop has valid pending algorithm values, or the existing values remain unchanged when a control is unavailable or the intended change is not approved. limitations - yearly seasonality is not a literal percentage of last year's sales and does not promise a fixed blend of historical and recent demand. - outlier filtering is an input to demand modeling; it does not guarantee that every promotion, bulk order, or unusual day is removed. - wholesale does not guarantee the same forecast change for every product; results depend on history and the applicable processing path. - the initial values shown by the component are not universal recommendations. persisted webshop settings replace local initial state when the page loads. - this guide does not establish an immediate, overnight, or other universal recalculation time. errors and recovery - if a numeric field is invalid, use the visible range, step, and required-field message to correct it. - if a field is locked or absent, check the account edition, simulator feature, permissions, and selected webshop. - if the section is loading or saving, wait for the state to finish before editing again. - if a source description conflicts with the current label or field behavior, preserve the conflict for review and follow the current visible validation rather than inventing a default. task 2 — save or undo algorithm changes purpose persist valid algorithm settings or discard pending edits while keeping the selected webshop's saved configuration intact. prerequisites - review the pending algorithm values in task 1. - correct all visible validation. - have settings edit access and wait for loading or saving to finish. steps 1. select save when the pending values are valid and approved. 2. wait for the save feedback and verify that the saved values remain after the form updates. 3. select undo changes instead if the pending values should not be stored. 4. confirm that the persisted values are shown after undo. 5. check downstream forecast or advice only through the applicable product and planning views; do not infer completion from the button state alone. fields and columns - save and undo — persist valid changes or restore saved algorithm values. - validation, loading, and simulator state — determine whether the current configuration can be saved safely. the shared settings action bar provides save and undo changes. there are no table columns. verify the selected webshop and the visible persisted fields. expected result save stores the valid algorithm settings. undo restores the saved settings before a new save. the account remains in its prior state when validation or a request fails. limitations - saving a setting does not guarantee a particular forecast, classification, or purchase-advice value. - a downstream planning or calculation process may be applicable before advice reflects a change; no universal timing is promised. - a saved form value does not by itself confirm that later planning or calculation work has finished. errors and recovery - if save is unavailable, inspect permissions, feature locks, validation, loading, and whether there are pending changes. - if save fails, keep the persisted values as the source of truth, correct the reported issue, and retry safely. - if navigation is blocked by unsaved changes, save valid edits, undo them, or remain on the page until the choice is clear.","customerSafe":true,"body":"# Configure Algorithm settings\n\nUse **Settings → Algorithm** to review forecast-related controls for the selected webshop. The fields shown and whether they can be edited depend on permissions, edition, enabled simulator features, loading, saving, and temporary Settings locks.\n\n## Task 1 — Configure Algorithm controls\n\n### Purpose\n\nSet the available Algorithm inputs deliberately for the selected webshop without treating a field label or example value as a guaranteed forecast outcome.\n\n### Prerequisites\n\n- Select the intended webshop and open **Settings → Algorithm**.\n- Have Settings edit access for changes; view-only users can inspect values.\n- Confirm whether the simulator feature is enabled before looking for simulator-only fields.\n- Wait for the section to finish loading.\n- Use the current visible validation and field explanation as the authority for the account.\n\n### Steps\n\n1. Review the persisted Algorithm values before editing.\n2. Set **Yearly seasonality** only when the intended value is known and valid.\n3. Choose the appropriate **Outlier filtering** and **Wholesale** options when they are available.\n4. If the simulator controls are shown, enter the applicable **Sell order threshold** and **History length**.\n5. Correct visible validation and compare the pending values with the approved planning strategy.\n6. Leave the fields unchanged if a feature lock, account boundary, or missing source data makes the intended effect unclear.\n7. Continue to Task 2 to save or undo the pending changes.\n\n### Fields and columns\n\nThis is a settings form, not a table:\n\n- **Yearly seasonality** — required in the current form, with a minimum of `0`, maximum of `1`, and step `0.1`.\n- **Outlier filtering** — controls whether abnormal sales spikes are filtered in the applicable forecasting path.\n- **Wholesale** — enables the applicable wholesale demand treatment; it is locked in Lite in the current experience.\n- **Sell order threshold** — where shown, a required non-negative whole number used by the applicable classification path.\n- **History length** — where shown, a required whole number from `30` through `365` days.\n\n### Expected result\n\nThe selected webshop has valid pending Algorithm values, or the existing values remain unchanged when a control is unavailable or the intended change is not approved.\n\n### Limitations\n\n- Yearly seasonality is not a literal percentage of last year's sales and does not promise a fixed blend of historical and recent demand.\n- Outlier filtering is an input to demand modeling; it does not guarantee that every promotion, bulk order, or unusual day is removed.\n- Wholesale does not guarantee the same forecast change for every Product; results depend on history and the applicable processing path.\n- The initial values shown by the component are not universal recommendations. Persisted webshop settings replace local initial state when the page loads.\n- This guide does not establish an immediate, overnight, or other universal recalculation time.\n\n### Errors and recovery\n\n- If a numeric field is invalid, use the visible range, step, and required-field message to correct it.\n- If a field is locked or absent, check the account edition, simulator feature, permissions, and selected webshop.\n- If the section is loading or saving, wait for the state to finish before editing again.\n- If a source description conflicts with the current label or field behavior, preserve the conflict for review and follow the current visible validation rather than inventing a default.\n\n## Task 2 — Save or undo Algorithm changes\n\n### Purpose\n\nPersist valid Algorithm settings or discard pending edits while keeping the selected webshop's saved configuration intact.\n\n### Prerequisites\n\n- Review the pending Algorithm values in Task 1.\n- Correct all visible validation.\n- Have Settings edit access and wait for loading or saving to finish.\n\n### Steps\n\n1. Select **Save** when the pending values are valid and approved.\n2. Wait for the save feedback and verify that the saved values remain after the form updates.\n3. Select **Undo changes** instead if the pending values should not be stored.\n4. Confirm that the persisted values are shown after undo.\n5. Check downstream forecast or advice only through the applicable product and planning views; do not infer completion from the button state alone.\n\n### Fields and columns\n\n- **Save and Undo** — persist valid changes or restore saved Algorithm values.\n- **Validation, loading, and simulator state** — determine whether the current configuration can be saved safely.\n\nThe shared Settings action bar provides **Save** and **Undo changes**. There are no table columns. Verify the selected webshop and the visible persisted fields.\n\n### Expected result\n\nSave stores the valid Algorithm settings. Undo restores the saved settings before a new save. The account remains in its prior state when validation or a request fails.\n\n### Limitations\n\n- Saving a setting does not guarantee a particular forecast, classification, or purchase-advice value.\n- A downstream planning or calculation process may be applicable before advice reflects a change; no universal timing is promised.\n- A saved form value does not by itself confirm that later planning or calculation work has finished.\n\n### Errors and recovery\n\n- If Save is unavailable, inspect permissions, feature locks, validation, loading, and whether there are pending changes.\n- If Save fails, keep the persisted values as the source of truth, correct the reported issue, and retry safely.\n- If navigation is blocked by unsaved changes, save valid edits, undo them, or remain on the page until the choice is clear."}