{"slug":"use-promotions-to-adjust-purchase-advice","sourcePath":"use-promotions-to-adjust-purchase-advice.md","title":"Use Promotions to adjust purchase advice","status":"reviewed","editorialStatus":"customer-ready","publicationBlocker":"","publishable":true,"needsReview":false,"reviewReason":"","category":"purchase-advice","lastReviewed":"2026-09-29","excerpt":"Use Promotions to record temporary demand changes caused by a planned sale, campaign, seasonal event, or clearance. Eligible promotion data can affect the demand information used for…","wordCount":3212,"readingMinutes":15,"articleType":"How-to guide","qualityFlags":[],"searchText":"use promotions to adjust purchase advice use promotions to record temporary demand changes caused by a planned sale, campaign, seasonal event, or clearance. eligible promotion data can affect the demand information used for… use promotions to adjust purchase advice use promotions to record temporary demand changes caused by a planned sale, campaign, seasonal event, or clearance. eligible promotion data can affect the demand information used for forecasting and purchase advice. promotions are not checkout price discounts and do not guarantee a particular purchase quantity. known limitations: there is no established universal priority rule when promotions overlap, automatic inclusion of products created later, a same-day date cutoff or timezone rule, or a universal recalculation time. the tasks below require readback of the current list, product scope, and advice instead of assuming those outcomes. task 1 — open, filter, and inspect promotions purpose find the correct webshop promotions, narrow the list, and open a promotion without changing its data. prerequisites - promotions must be enabled for the webshop and available to the account. - have promotions view access to inspect the list; edit access is required for create and mutation actions. - have products permission if you need to use the products tab or product actions inside a promotion. - confirm the selected webshop before reviewing results. steps 1. open promotions from the main navigation. 2. wait for the list to finish loading. 3. search by the available promotion fields and apply filters such as notes, whether notes exist, promotion name, start date, end date, uplift type, expected uplift, and products count. 4. sort the result using the shared sort control where sorting is available. 5. use column view to choose, order, show, pin, or resize visible columns. 6. change the page size or move through pagination when needed. the current table exposes page sizes from 10 through 200; its current initial page size is 50. 7. use clear all to remove active searches and filters when it is available. 8. select a row or its promotion name to open the details view. fields and columns the normal list columns are: - notes; - promotion name; - start date and end date; - uplift type and expected uplift; - products or products count. editable users can also see selection and actions columns. filters, sort, search, pagination, refresh, and column controls are visible only where the account exposes them. products count accepts whole numbers from zero upward in the current list. expected result the list shows the current result for the selected webshop and active search/filter state, or the selected promotion opens in its details view. no promotion is changed by inspection alone. limitations - view-only access does not expose all mutation controls. - an empty result does not prove that no promotion exists; active filters, search, pagination, permission, and webshop selection can affect the result. - notes are not sortable in the current list. - the list's page-size values and visible columns are current interface behavior, not a promise that every account has identical controls. errors and recovery - while loading, the table can temporarily show no rows. wait for loading to finish before interpreting the result. - if the result is empty, clear filters and search terms, refresh, and confirm the webshop. - if a load fails, use the visible error feedback, resolve the access or connection issue, wait for the failed state to finish, and select refresh. - if a row cannot be opened, check promotions and products permission rather than retrying a mutation. create a promotion purpose create a promotion with an intentional date range, uplift type, and enabled state. prerequisites - have promotions edit access or shop-administrator access. - confirm that promotions is enabled for the selected webshop and is not locked by the account plan. - decide whether the promotion is relative, absolute, close-out, or no uplift. - prepare the products or scope that will be associated after creation. steps 1. select create promotion. 2. enter a promotion name. 3. choose the start date and end date, ensuring the end date is not earlier than the start date. 4. choose an uplift type. 5. enter expected uplift when relative or absolute requires an editable value. do not use zero where the current form rejects zero. 6. review the enabled toggle; the current form can open enabled, but the value must be checked before saving. 7. continue to the product-scope step. 8. review the values and select create promotion. 9. use the post-create choice to view details or add products. fields and columns the create form contains: - promotion name — required in the current form. - start date and end date — required; the end date cannot be earlier than the start date. - uplift type — relative (%), absolute, close out, or no uplift. - expected uplift — required when the selected type uses an editable value; its validation is shown by the form. - enabled — the promotion state to review before creation. there are no list columns in the create panel; product-scope choices appear in the next step. expected result a promotion is created with the values you reviewed, and the workflow offers the next available product-association or details action. limitations - a relative uplift is a percentage-style demand adjustment and an absolute uplift is a fixed-quantity adjustment; neither is a checkout price discount. - close out is a temporary planning choice and is not the same as permanently phasing out a product. - no universal uplift value, same-day cutoff, timezone interpretation, forecast result, or order quantity is established. - close and back controls can be unavailable while a save is in progress. errors and recovery - if create is disabled, correct required fields, date order, uplift value, and the visible enabled-state validation. - if creation fails, return to the list or details view and verify whether a promotion was actually created before trying again. - if the post-create panel does not load, keep the promotion record as the source of truth and use add products from its details view after access is restored. add products and choose product scope purpose associate the intended current webshop products with an existing promotion by manual selection, import, or the entire-webshop action. prerequisites - have promotions edit access and products permission for product-scope actions. - open an existing promotion or reach the product step after creation. - for import, prepare a csv or excel file containing product ids or skus accepted by the current entry point. - check whether another import or conflicting job is running. steps 1. open add products from the promotion's products area or choose the product action after creation. 2. choose one available scope: import products, select products, or apply promotion to all webshop products. 3. for manual selection, search or filter available products, select the intended rows, and review the selection. 4. for import, upload the csv or excel file and wait for the job result. 5. for the entire-webshop option, review the confirmation carefully and confirm only when the current product scope is intended. 6. read back the promotion's products table after the action finishes. 7. confirm that the intended products and any product-specific values are present before relying on the promotion. fields and columns the product-scope workflow can expose: - product id or sku used for import; - product identity and the shared search/filter controls; - selected-row count, with the current table selection ceiling of 200; - import job feedback; - products-table identity, uplift, and action columns where enabled. expected result the promotion's products view shows the current associations that were accepted by the selected workflow. treat the request as incomplete until you review the products table or job result. limitations - a successful upload or entire-webshop request is not proof that every row was accepted or that downstream processing has finished. - the entire-webshop operation applies to the current webshop products exposed by the action. the current workflow does not establish automatic inclusion of products created later. - product actions depend on products permission and can be unavailable while another job or table operation is running. - do not send an import file containing unnecessary private data to support; use an authorized support channel only when requested. errors and recovery - if import is unavailable, check for a conflicting job, file type, product id/sku format, permission, and current promotion state. - if the job reports partial or failed results, use the job feedback and products table to identify what was actually accepted before retrying. - if the entire-webshop request is asynchronous or the table is stale, wait for the visible operation to finish and refresh the products view. - if a product is missing, verify the selected webshop and source product identifier instead of repeatedly adding it. edit promotion information, settings, and notes purpose update an existing promotion's information, enabled state, scope, or promotion note while preserving the distinction between editable fields and derived status. prerequisites - open the correct promotion and have promotions edit access. - confirm whether you are editing the information, settings, or notes section. - check the current products scope before changing an entire-webshop setting. - wait for any existing save or product operation to finish. steps 1. open the promotion's overview and review its current dates, uplift, enabled state, derived status, settings, notes, and products scope. 2. select the section's edit control. 3. change only the intended information or enabled/scope setting. 4. use save to persist the section or cancel to restore its persisted values. 5. for notes, open the notes panel, enter or change the promotion note, then save; use close or cancel to leave it unchanged. 6. if the entire-webshop scope is enabled, review the resulting products list after the background operation. 7. read back the promotion details after each save. fields and columns the overview and editor can show: - promotion name; - start date and end date; - uplift type and expected uplift; - enabled state; - derived status such as disabled, planned, in progress, or ended; - entire-webshop scope; - notes and the notes indicator in the list; - products information when the products tab is available. expected result the selected section saves the valid changes, or cancel leaves its persisted values unchanged. the promotion details and list reflect the saved state after readback. limitations - status is derived from enabled state and dates; it is not a separate editable status field. - this guide does not establish an exact start/end cutoff or timezone rule. - entire-webshop scope can trigger background processing, so saving the setting is not proof that every current product has been associated. - notes are internal promotion notes; do not place credentials or sensitive customer payloads in them. errors and recovery - if save is disabled, check required values, date order, permission, loading, and whether another edit is active. - if a section save fails, use the persisted detail view as the source of truth and retry only after correcting the visible issue. - if status appears unexpected, compare the saved dates and enabled state rather than manually trying to edit a derived status. edit product-specific uplift purpose set or remove a product-level uplift for a product already associated with a promotion. prerequisites - open the promotion's products tab with the products permission and promotions edit access. - confirm the correct product and promotion before editing. - wait for the products table to finish loading and ensure no other row is in edit mode. - decide whether the product should use the promotion default or an override. steps 1. search or filter the products table to the intended product. 2. open the product row for editing. 3. choose relative, absolute, close out, or no uplift. 4. enter expected uplift when the selected type requires it. 5. review the row and select save. 6. to remove a complete product-specific override, clear the override and save; confirm that the product remains associated. 7. use the separate remove action only when the product should no longer belong to the promotion. fields and columns the products table can expose: - product identity and searchable product columns; - promotion-level and product-specific uplift information; - the product-specific uplift type; - expected uplift when required; - row edit, save, cancel, remove, and other actions where permitted. expected result the saved product row either uses its valid product-specific uplift or falls back to the promotion-level uplift when the complete override is cleared. removing a product is a separate association action. limitations - a product can be associated with more than one promotion. the current workflow does not establish a “latest promotion wins” or other priority rule. - a product-specific uplift is planning input, not a checkout price change and not a guaranteed order quantity. - product rows can be locked while the table is loading, another edit is active, or a conflicting operation is running. - product details promotion controls are products-owned; use the central promotion editor for promotion-level scope and lifecycle changes. errors and recovery - if the row cannot be edited, finish or cancel another row edit and check permission, loading, and promotion state. - if the expected value is rejected, use the visible validation for the selected uplift type. - if save fails, re-open the row and verify whether the old override, promotion default, or persisted removal is shown before trying again. - do not remove the product to clear an override; clear the override when the association should remain. bulk enable, disable, or delete promotions purpose use lifecycle and data-transfer actions deliberately, with a readback check before or after any potentially destructive operation. prerequisites - have promotions edit access for enable, disable, delete, import, and other mutation actions. - have exports enabled and the required export permission for export actions. - review the exact rows selected and the current enabled state. - confirm that no unsaved edit or conflicting job is in progress. steps 1. for one row, open its actions menu and review the available action. 2. use disable to stop an enabled promotion reversibly, or enable to re-enable a disabled promotion. 3. use single-row delete only after reading its confirmation and accepting that the action cannot be undone. 4. for a bulk action, select only the intended rows and choose enable, disable, or delete. 5. for import or export, review the file/job or current filters, search, sort, and selected promotions before dispatching it. 6. after the action, wait for feedback, confirm that selection is cleared where applicable, and reload the list or details view. 7. verify the resulting enabled state, presence/absence, products scope, or job result before taking another destructive action. fields and columns relevant controls include: - row actions: edit, disable, delete, enable, or the actions available for the current state; - selected-row count, limited to 200 in the current list; - exportable visible data columns: notes, promotion name, dates, uplift type, expected uplift, and products; - current search, filters, sort, and optional selected promotions used by export; - import or export progress and result feedback. expected result the requested lifecycle or data-transfer action has visible feedback and its result is confirmed in the refreshed list, details view, or job result. a disabled promotion remains available for later enabling; a deleted promotion is removed from the normal list. limitations - disable is reversible; delete is destructive and the single-row flow warns that it cannot be undone. - the bulk delete menu does not establish a separate confirmation step. treat the selected rows as the confirmation and verify them before choosing delete. - dispatching an import or export does not prove that every row was processed or that a file was generated successfully. - seeing a completed ui request does not prove downstream forecast, email, or integration processing has finished. errors and recovery - if an action is unavailable, check the row state, permission, feature configuration, loading, selection count, and current job state. - if a mutation reports failure or times out, do not repeat a destructive action immediately. refresh or open the details view and confirm the current state first. - if an import or export fails, use its result feedback and current filters/selection to correct the request before retrying. - if a bulk selection is wrong, clear it and start again rather than relying on a hidden or stale selection. task 7 — check promotion impact and recover from unexpected advice purpose validate that the intended promotion data is present before interpreting a forecast or purchase-advice change, without promising a fixed runtime or quantity. prerequisites - confirm the correct webshop, promotion enabled state, dates, uplift type, expected uplift, and product scope. - read back any product-specific overrides and import/entire-webshop job results. - have access to the relevant forecast, stock, and purchase-advice views. - keep the visible error text and affected product information available without including credentials or unnecessary personal data. steps 1. check whether the promotion is enabled and whether its dates place it in the intended planning period. 2. compare promotion-level and product-specific uplift values. 3. review overlapping promotions for the same products instead of assuming precedence. 4. check current stock, incoming supply, forecast, supplier constraints, and the applicable planning state. 5. review the purchase advice after the applicable processing has completed according to the account's visible state; no fixed schedule is implied. 6. if the result is unexpected, correct the source data or promotion configuration only after identifying the difference. 7. record the promotion name, affected product identifiers, dates, uplift choice, and visible error for an authorized support request when needed. fields and columns use these values as the troubleshooting record: - promotion name, start date, end date, enabled state, and derived status; - promotion-level uplift type and expected uplift; - product association and product-specific uplift type/expected uplift; - overlapping promotion names and scopes; - import, export, or entire-webshop job result; - current stock, incoming stock, forecast, supplier constraints, and purchase-advice value where visible. expected result the active promotion configuration and product scope are understood, and any advice difference is reviewed against the available planning inputs rather than an assumed priority or timing rule. limitations - when promotion processing is enabled, eligible promotion data can affect demand normalization, forecasts, and proposed purchase quantities, but the source does not establish a universal recalculation time or resulting order quantity. - relative, absolute, close out, and no uplift have different planning meanings; the ui value alone does not promise a business outcome. - multiple promotions can apply to one product, and no customer-safe priority rule is established. - this guide does not claim that a promotion changes checkout pricing, stock, or an external webshop. errors and recovery - if the promotion or advice is missing, confirm webshop, permission, enabled state, dates, and products scope first. - if an action failed, recheck the list or details view before repeating it. - if advice remains unexpected, compare the promotion with stock, incoming supply, forecast, supplier eligibility, moq, lot size, minimum order value, and current planning state. - escalate with only the necessary visible identifiers and error text; never include credentials, tokens, or raw private payloads. manage products in a promotion purpose find, add, import, remove, or export intended product associations for an existing promotion. prerequisites - open the correct promotion with promotions edit access and product permission. - confirm the current webshop and promotion state. - wait for any existing product operation or import job to finish. steps 1. open the promotion's products view. 2. search, filter, sort, or paginate to find intended associations. 3. use add products for manual selection, the import workflow for a file, or the available remove action for selected associations. 4. use export when you need a file snapshot of current associations. 5. reload the products view and verify accepted additions, removals, or the export source. fields and columns - product identity and association state — identify each product included in the promotion. - product-specific uplift and selection count — describe available product-level values and staged actions. product identity, product-specific uplift, selection count, association actions, search, filters, sorting, pagination, and export controls can be shown. import results are reviewed separately in job feedback. expected result the promotion's products view shows intended current associations after completed operations, or provides the requested file snapshot. limitations - adding, importing, removing, and exporting are separate operations with separate outcomes. - a successful upload does not prove every file row was accepted. - product actions can be unavailable during another edit or job. errors and recovery - if a product is missing, verify webshop, identifier, filters, permission, and promotion state. - if an import is partial or failed, use job feedback before retrying rejected rows. - if a removal or addition result is unclear, reload and verify the association before repeating the action.","customerSafe":true,"body":"# Use Promotions to adjust purchase advice\n\nUse **Promotions** to record temporary demand changes caused by a planned sale, campaign, seasonal event, or clearance. Eligible promotion data can affect the demand information used for forecasting and purchase advice. Promotions are not checkout price discounts and do not guarantee a particular purchase quantity.\n\n> **Known limitations:** There is no established universal priority rule when promotions overlap, automatic inclusion of products created later, a same-day date cutoff or timezone rule, or a universal recalculation time. The tasks below require readback of the current list, product scope, and advice instead of assuming those outcomes.\n\n## Task 1 — Open, filter, and inspect Promotions\n\n### Purpose\n\nFind the correct webshop promotions, narrow the list, and open a promotion without changing its data.\n\n### Prerequisites\n\n- Promotions must be enabled for the webshop and available to the account.\n- Have **Promotions View** access to inspect the list; Edit access is required for create and mutation actions.\n- Have Products permission if you need to use the Products tab or product actions inside a promotion.\n- Confirm the selected webshop before reviewing results.\n\n### Steps\n\n1. Open **Promotions** from the main navigation.\n2. Wait for the list to finish loading.\n3. Search by the available promotion fields and apply filters such as Notes, whether notes exist, Promotion name, Start date, End date, Uplift type, Expected uplift, and Products count.\n4. Sort the result using the shared sort control where sorting is available.\n5. Use **Column view** to choose, order, show, pin, or resize visible columns.\n6. Change the page size or move through pagination when needed. The current table exposes page sizes from `10` through `200`; its current initial page size is `50`.\n7. Use **Clear all** to remove active searches and filters when it is available.\n8. Select a row or its promotion name to open the details view.\n\n### Fields and columns\n\nThe normal list columns are:\n\n- **Notes**;\n- **Promotion name**;\n- **Start date** and **End date**;\n- **Uplift type** and **Expected uplift**;\n- **Products** or Products count.\n\nEditable users can also see selection and **Actions** columns. Filters, sort, search, pagination, refresh, and column controls are visible only where the account exposes them. Products count accepts whole numbers from zero upward in the current list.\n\n### Expected result\n\nThe list shows the current result for the selected webshop and active search/filter state, or the selected promotion opens in its details view. No promotion is changed by inspection alone.\n\n### Limitations\n\n- View-only access does not expose all mutation controls.\n- An empty result does not prove that no promotion exists; active filters, search, pagination, permission, and webshop selection can affect the result.\n- Notes are not sortable in the current list.\n- The list's page-size values and visible columns are current interface behavior, not a promise that every account has identical controls.\n\n### Errors and recovery\n\n- While loading, the table can temporarily show no rows. Wait for loading to finish before interpreting the result.\n- If the result is empty, clear filters and search terms, refresh, and confirm the webshop.\n- If a load fails, use the visible error feedback, resolve the access or connection issue, wait for the failed state to finish, and select **Refresh**.\n- If a row cannot be opened, check Promotions and Products permission rather than retrying a mutation.\n\n## Create a promotion\n\n### Purpose\n\nCreate a promotion with an intentional date range, uplift type, and enabled state.\n\n### Prerequisites\n\n- Have Promotions Edit access or shop-administrator access.\n- Confirm that Promotions is enabled for the selected webshop and is not locked by the account plan.\n- Decide whether the promotion is relative, absolute, close-out, or no uplift.\n- Prepare the products or scope that will be associated after creation.\n\n### Steps\n\n1. Select **Create promotion**.\n2. Enter a Promotion name.\n3. Choose the Start date and End date, ensuring the End date is not earlier than the Start date.\n4. Choose an Uplift type.\n5. Enter Expected uplift when **Relative** or **Absolute** requires an editable value. Do not use zero where the current form rejects zero.\n6. Review the enabled toggle; the current form can open enabled, but the value must be checked before saving.\n7. Continue to the product-scope step.\n8. Review the values and select **Create promotion**.\n9. Use the post-create choice to view details or add products.\n\n### Fields and columns\n\nThe create form contains:\n\n- **Promotion name** — required in the current form.\n- **Start date** and **End date** — required; the End date cannot be earlier than the Start date.\n- **Uplift type** — Relative (%), Absolute, Close out, or No uplift.\n- **Expected uplift** — required when the selected type uses an editable value; its validation is shown by the form.\n- **Enabled** — the promotion state to review before creation.\n\nThere are no list columns in the create panel; product-scope choices appear in the next step.\n\n### Expected result\n\nA promotion is created with the values you reviewed, and the workflow offers the next available product-association or details action.\n\n### Limitations\n\n- A Relative uplift is a percentage-style demand adjustment and an Absolute uplift is a fixed-quantity adjustment; neither is a checkout price discount.\n- Close out is a temporary planning choice and is not the same as permanently phasing out a Product.\n- No universal uplift value, same-day cutoff, timezone interpretation, forecast result, or order quantity is established.\n- Close and Back controls can be unavailable while a save is in progress.\n\n### Errors and recovery\n\n- If Create is disabled, correct required fields, date order, uplift value, and the visible enabled-state validation.\n- If creation fails, return to the list or details view and verify whether a promotion was actually created before trying again.\n- If the post-create panel does not load, keep the promotion record as the source of truth and use **Add products** from its details view after access is restored.\n\n## Add Products and choose Product scope\n\n### Purpose\n\nAssociate the intended current webshop products with an existing promotion by manual selection, import, or the entire-webshop action.\n\n### Prerequisites\n\n- Have Promotions Edit access and Products permission for product-scope actions.\n- Open an existing promotion or reach the product step after creation.\n- For import, prepare a CSV or Excel file containing product IDs or SKUs accepted by the current entry point.\n- Check whether another import or conflicting job is running.\n\n### Steps\n\n1. Open **Add products** from the promotion's Products area or choose the product action after creation.\n2. Choose one available scope: **Import products**, **Select products**, or **Apply promotion to all webshop products**.\n3. For manual selection, search or filter available products, select the intended rows, and review the selection.\n4. For import, upload the CSV or Excel file and wait for the job result.\n5. For the entire-webshop option, review the confirmation carefully and confirm only when the current product scope is intended.\n6. Read back the promotion's Products table after the action finishes.\n7. Confirm that the intended products and any product-specific values are present before relying on the promotion.\n\n### Fields and columns\n\nThe product-scope workflow can expose:\n\n- product ID or SKU used for import;\n- product identity and the shared search/filter controls;\n- selected-row count, with the current table selection ceiling of `200`;\n- import job feedback;\n- Products-table identity, uplift, and action columns where enabled.\n\n### Expected result\n\nThe promotion's Products view shows the current associations that were accepted by the selected workflow. Treat the request as incomplete until you review the Products table or job result.\n\n### Limitations\n\n- A successful upload or entire-webshop request is not proof that every row was accepted or that downstream processing has finished.\n- The entire-webshop operation applies to the current webshop products exposed by the action. The current workflow does not establish automatic inclusion of products created later.\n- Product actions depend on Products permission and can be unavailable while another job or table operation is running.\n- Do not send an import file containing unnecessary private data to Support; use an authorized support channel only when requested.\n\n### Errors and recovery\n\n- If import is unavailable, check for a conflicting job, file type, product ID/SKU format, permission, and current promotion state.\n- If the job reports partial or failed results, use the job feedback and Products table to identify what was actually accepted before retrying.\n- If the entire-webshop request is asynchronous or the table is stale, wait for the visible operation to finish and refresh the Products view.\n- If a product is missing, verify the selected webshop and source Product identifier instead of repeatedly adding it.\n\n## Edit promotion information, settings, and notes\n\n### Purpose\n\nUpdate an existing promotion's information, enabled state, scope, or promotion note while preserving the distinction between editable fields and derived status.\n\n### Prerequisites\n\n- Open the correct promotion and have Promotions Edit access.\n- Confirm whether you are editing the information, Settings, or Notes section.\n- Check the current Products scope before changing an entire-webshop setting.\n- Wait for any existing save or product operation to finish.\n\n### Steps\n\n1. Open the promotion's Overview and review its current dates, uplift, enabled state, derived status, Settings, Notes, and Products scope.\n2. Select the section's edit control.\n3. Change only the intended information or enabled/scope setting.\n4. Use **Save** to persist the section or **Cancel** to restore its persisted values.\n5. For Notes, open the Notes panel, enter or change the promotion note, then Save; use Close or Cancel to leave it unchanged.\n6. If the entire-webshop scope is enabled, review the resulting Products list after the background operation.\n7. Read back the promotion details after each save.\n\n### Fields and columns\n\nThe Overview and editor can show:\n\n- Promotion name;\n- Start date and End date;\n- Uplift type and Expected uplift;\n- Enabled state;\n- derived status such as Disabled, Planned, In progress, or Ended;\n- entire-webshop scope;\n- Notes and the Notes indicator in the list;\n- Products information when the Products tab is available.\n\n### Expected result\n\nThe selected section saves the valid changes, or Cancel leaves its persisted values unchanged. The promotion details and list reflect the saved state after readback.\n\n### Limitations\n\n- Status is derived from enabled state and dates; it is not a separate editable status field.\n- This guide does not establish an exact start/end cutoff or timezone rule.\n- Entire-webshop scope can trigger background processing, so saving the setting is not proof that every current product has been associated.\n- Notes are internal promotion notes; do not place credentials or sensitive customer payloads in them.\n\n### Errors and recovery\n\n- If Save is disabled, check required values, date order, permission, loading, and whether another edit is active.\n- If a section save fails, use the persisted detail view as the source of truth and retry only after correcting the visible issue.\n- If status appears unexpected, compare the saved dates and enabled state rather than manually trying to edit a derived status.\n\n## Edit Product-specific uplift\n\n### Purpose\n\nSet or remove a product-level uplift for a product already associated with a promotion.\n\n### Prerequisites\n\n- Open the promotion's Products tab with the Products permission and Promotions Edit access.\n- Confirm the correct product and promotion before editing.\n- Wait for the Products table to finish loading and ensure no other row is in edit mode.\n- Decide whether the product should use the promotion default or an override.\n\n### Steps\n\n1. Search or filter the Products table to the intended product.\n2. Open the product row for editing.\n3. Choose **Relative**, **Absolute**, **Close out**, or **No uplift**.\n4. Enter Expected uplift when the selected type requires it.\n5. Review the row and select **Save**.\n6. To remove a complete product-specific override, clear the override and save; confirm that the product remains associated.\n7. Use the separate remove action only when the product should no longer belong to the promotion.\n\n### Fields and columns\n\nThe Products table can expose:\n\n- product identity and searchable product columns;\n- promotion-level and product-specific uplift information;\n- the product-specific **Uplift type**;\n- **Expected uplift** when required;\n- row edit, save, cancel, remove, and other actions where permitted.\n\n### Expected result\n\nThe saved product row either uses its valid product-specific uplift or falls back to the promotion-level uplift when the complete override is cleared. Removing a product is a separate association action.\n\n### Limitations\n\n- A product can be associated with more than one promotion. The current workflow does not establish a “latest promotion wins” or other priority rule.\n- A product-specific uplift is planning input, not a checkout price change and not a guaranteed order quantity.\n- Product rows can be locked while the table is loading, another edit is active, or a conflicting operation is running.\n- Product Details promotion controls are Products-owned; use the central promotion editor for promotion-level scope and lifecycle changes.\n\n### Errors and recovery\n\n- If the row cannot be edited, finish or cancel another row edit and check permission, loading, and promotion state.\n- If the expected value is rejected, use the visible validation for the selected uplift type.\n- If Save fails, re-open the row and verify whether the old override, promotion default, or persisted removal is shown before trying again.\n- Do not remove the product to clear an override; clear the override when the association should remain.\n\n## Bulk enable, disable, or delete promotions\n\n### Purpose\n\nUse lifecycle and data-transfer actions deliberately, with a readback check before or after any potentially destructive operation.\n\n### Prerequisites\n\n- Have Promotions Edit access for Enable, Disable, Delete, import, and other mutation actions.\n- Have Exports enabled and the required export permission for export actions.\n- Review the exact rows selected and the current enabled state.\n- Confirm that no unsaved edit or conflicting job is in progress.\n\n### Steps\n\n1. For one row, open its Actions menu and review the available action.\n2. Use **Disable** to stop an enabled promotion reversibly, or **Enable** to re-enable a disabled promotion.\n3. Use single-row **Delete** only after reading its confirmation and accepting that the action cannot be undone.\n4. For a bulk action, select only the intended rows and choose Enable, Disable, or Delete.\n5. For import or export, review the file/job or current filters, search, sort, and selected promotions before dispatching it.\n6. After the action, wait for feedback, confirm that selection is cleared where applicable, and reload the list or details view.\n7. Verify the resulting enabled state, presence/absence, Products scope, or job result before taking another destructive action.\n\n### Fields and columns\n\nRelevant controls include:\n\n- row **Actions**: Edit, Disable, Delete, Enable, or the actions available for the current state;\n- selected-row count, limited to `200` in the current list;\n- exportable visible data columns: Notes, Promotion name, dates, Uplift type, Expected uplift, and Products;\n- current search, filters, sort, and optional selected promotions used by export;\n- import or export progress and result feedback.\n\n### Expected result\n\nThe requested lifecycle or data-transfer action has visible feedback and its result is confirmed in the refreshed list, details view, or job result. A disabled promotion remains available for later enabling; a deleted promotion is removed from the normal list.\n\n### Limitations\n\n- Disable is reversible; Delete is destructive and the single-row flow warns that it cannot be undone.\n- The bulk Delete menu does not establish a separate confirmation step. Treat the selected rows as the confirmation and verify them before choosing Delete.\n- Dispatching an import or export does not prove that every row was processed or that a file was generated successfully.\n- Seeing a completed UI request does not prove downstream forecast, email, or integration processing has finished.\n\n### Errors and recovery\n\n- If an action is unavailable, check the row state, permission, feature configuration, loading, selection count, and current job state.\n- If a mutation reports failure or times out, do not repeat a destructive action immediately. Refresh or open the details view and confirm the current state first.\n- If an import or export fails, use its result feedback and current filters/selection to correct the request before retrying.\n- If a bulk selection is wrong, clear it and start again rather than relying on a hidden or stale selection.\n\n## Task 7 — Check promotion impact and recover from unexpected advice\n\n### Purpose\n\nValidate that the intended promotion data is present before interpreting a forecast or purchase-advice change, without promising a fixed runtime or quantity.\n\n### Prerequisites\n\n- Confirm the correct webshop, promotion enabled state, dates, uplift type, expected uplift, and product scope.\n- Read back any product-specific overrides and import/entire-webshop job results.\n- Have access to the relevant forecast, stock, and purchase-advice views.\n- Keep the visible error text and affected product information available without including credentials or unnecessary personal data.\n\n### Steps\n\n1. Check whether the promotion is enabled and whether its dates place it in the intended planning period.\n2. Compare promotion-level and product-specific uplift values.\n3. Review overlapping promotions for the same Products instead of assuming precedence.\n4. Check current stock, incoming supply, forecast, Supplier constraints, and the applicable planning state.\n5. Review the purchase advice after the applicable processing has completed according to the account's visible state; no fixed schedule is implied.\n6. If the result is unexpected, correct the source data or promotion configuration only after identifying the difference.\n7. Record the promotion name, affected Product identifiers, dates, uplift choice, and visible error for an authorized support request when needed.\n\n### Fields and columns\n\nUse these values as the troubleshooting record:\n\n- Promotion name, Start date, End date, enabled state, and derived status;\n- promotion-level Uplift type and Expected uplift;\n- product association and product-specific Uplift type/Expected uplift;\n- overlapping promotion names and scopes;\n- import, export, or entire-webshop job result;\n- current stock, incoming stock, forecast, Supplier constraints, and purchase-advice value where visible.\n\n### Expected result\n\nThe active promotion configuration and product scope are understood, and any advice difference is reviewed against the available planning inputs rather than an assumed priority or timing rule.\n\n### Limitations\n\n- When promotion processing is enabled, eligible promotion data can affect demand normalization, forecasts, and proposed purchase quantities, but the source does not establish a universal recalculation time or resulting order quantity.\n- Relative, Absolute, Close out, and No uplift have different planning meanings; the UI value alone does not promise a business outcome.\n- Multiple promotions can apply to one product, and no customer-safe priority rule is established.\n- This guide does not claim that a promotion changes checkout pricing, stock, or an external webshop.\n\n### Errors and recovery\n\n- If the promotion or advice is missing, confirm webshop, permission, enabled state, dates, and Products scope first.\n- If an action failed, recheck the list or details view before repeating it.\n- If advice remains unexpected, compare the promotion with stock, incoming supply, forecast, Supplier eligibility, MOQ, Lot Size, Minimum order value, and current planning state.\n- Escalate with only the necessary visible identifiers and error text; never include credentials, tokens, or raw private payloads.\n\n## Manage Products in a promotion\n\n### Purpose\n\nFind, add, import, remove, or export intended Product associations for an existing promotion.\n\n### Prerequisites\n\n- Open the correct promotion with Promotions edit access and Product permission.\n- Confirm the current webshop and promotion state.\n- Wait for any existing Product operation or import job to finish.\n\n### Steps\n\n1. Open the promotion's **Products** view.\n2. Search, filter, sort, or paginate to find intended associations.\n3. Use **Add products** for manual selection, the import workflow for a file, or the available remove action for selected associations.\n4. Use export when you need a file snapshot of current associations.\n5. Reload the Products view and verify accepted additions, removals, or the export source.\n\n### Fields and columns\n\n- **Product identity and association state** — identify each Product included in the promotion.\n- **Product-specific uplift and selection count** — describe available Product-level values and staged actions.\n\nProduct identity, Product-specific uplift, selection count, association actions, search, filters, sorting, pagination, and export controls can be shown. Import results are reviewed separately in job feedback.\n\n### Expected result\n\nThe promotion's Products view shows intended current associations after completed operations, or provides the requested file snapshot.\n\n### Limitations\n\n- Adding, importing, removing, and exporting are separate operations with separate outcomes.\n- A successful upload does not prove every file row was accepted.\n- Product actions can be unavailable during another edit or job.\n\n### Errors and recovery\n\n- If a Product is missing, verify webshop, identifier, filters, permission, and promotion state.\n- If an import is partial or failed, use job feedback before retrying rejected rows.\n- If a removal or addition result is unclear, reload and verify the association before repeating the action."}