Purpose

Optiply Lite: Promotions, including Dashboard Import and Support-Assisted Import, are not available in Optiply Lite. If you cannot access Promotions, contact your Customer Success Manager or Optiply support to check your plan and feature access.

Prerequisites

  • Confirm the selected webshop and that Promotions and imports are available.
  • For Dashboard Import, have permission to edit Promotions and access their Products. Create or open the intended promotion first.
  • Use identifiers that match Products already in Optiply. Preserve leading zeroes in SKU and EAN codes.
  • Decide whether you are adding Products to one promotion or asking support to create multiple promotions.
  • Review the dates and expected sales uplift before importing. Promotions affect demand planning; they are not checkout price discounts.

See Create and manage promotions for promotion settings and uplift meanings.

Dashboard Import — one promotion, self-serve

Steps

  1. Open Promotions and create or edit the intended promotion.
  2. Open its Products area and select Import products.
  3. Choose Add new products to promotion or Update existing products in promotion as appropriate. This choice affects Product rows in that promotion, not the creation of new promotions.
  4. Choose the Product identifier used consistently in your file: Optiply ID, EAN code, SKU code, or Article code.
  5. Download the current template. Prepare a UTF-8 CSV file with one header row and one row per Product.
  6. Upload the CSV file and continue to Match columns. Map your identifier and uplift columns to the corresponding Optiply fields, including every field marked with *.
  7. Under Check for errors, correct any missing identifiers, duplicate mappings, blank values, or invalid formats. Upload the corrected CSV again if needed.
  8. When validation allows it, select Import.
  9. Track the job under Settings > Data management > Imports/Exports. Return to the same promotion and verify the imported Product list and Product-specific uplift values.

Fields and columns

The SKU-based example uses these three columns. The downloaded template and fields marked with * remain authoritative for your selected identifier and operation:

ColumnMeaning
skuCodeSKU code identifying a Product already in Optiply. If you select another identifier, use the corresponding template column instead.
specificUpliftTypeProduct-specific uplift type, such as relative or absolute, using a value accepted by the current template.
specificUpliftIncreaseExpected Product-specific sales increase: a percentage for relative uplift or a fixed-quantity increase for absolute uplift.

The open promotion supplies the promotion context. This file does not need the master file's promotion name and date columns. For the full create/update workflow, see Import products to a promotion.

No uplift: product import versus promotion setting

For No uplift per Product in Products in a promotion, leave both specificUpliftType and specificUpliftIncrease cells empty. Keep the headers from the current template. Do not enter 0 or -: neither means No uplift, and the importer rejects them with a reason.

The upload import cannot set No uplift for the promotion itself. Set that promotion-level option in the promotion editor, not in the uploaded Product file. The product-import blank-field rule is separate from changing the promotion's own uplift setting.

Expected result

Accepted rows are added to, or updated within, the promotion you selected. Check the succeeded, failed, and skipped row counts; a finished job does not mean every row succeeded. Verify a sample of Product identifiers and uplifts in the promotion before relying on it for planning.

Support-Assisted Import — multiple promotions

Steps

  1. Prepare a CSV file with the nine headers listed below. Use the Product identifier your system relies on; you do not need to populate both SKU and EAN for each row.
  2. Enter the intended promotion name, start and end dates, default uplift, and Product-specific uplift values.
  3. Check that the identifiers match existing Products, the end dates are not earlier than the start dates, and percentages or quantities are correct.
  4. Save the file as .csv and include the preparation date in its name, for example Promotions_2026-09-30.csv.
  5. Send the completed file to support@optiply.nl or through the in-app chat. Explain that you want to create multiple promotions and identify the intended webshop.
  6. After support processes the file, open Promotions and verify the promotion names, dates, Products, and uplift values.

Fields and columns

Keep all nine headers in the support file:

ColumnMeaning and format
nameName of the promotion to create.
skuCodeSKU code identifying the Product. Populate the identifier you use; both SKU and EAN values are not required.
eanCodeEAN code identifying the Product, if this is your primary identifier. Keep leading zeroes.
start_datePromotion start date in YYYY-MM-DD format.
end_datePromotion end date in YYYY-MM-DD format.
upliftTypeDefault promotion uplift type: relative or absolute.
upliftIncreaseDefault expected sales increase: a percentage for relative uplift or a fixed-quantity increase for absolute uplift.
specificUpliftTypeProduct-specific uplift type: relative or absolute.
specificUpliftIncreaseExpected increase for that Product, interpreted according to its specific uplift type.

A promotion-level No uplift setting cannot be supplied by upload import; use the promotion editor for that setting. The per-Product blank-field rule above applies to Products in a promotion, not a new master-file token.

For a close-out promotion, use close_out in both upliftType and specificUpliftType. Leave upliftIncrease and specificUpliftIncrease empty for those rows. Close-out is a temporary promotion choice, not permanent Product phase-out.

Expected result

Support creates the promotions from the reviewed master file. Verify the resulting promotions in the selected webshop. Submission is not confirmation that processing has finished; ask support for the processing status if the promotions are not yet visible.

Limitations

  • Neither import method is available in Optiply Lite.
  • Dashboard Import works within one selected promotion; it is not a self-serve master-file upload for creating multiple promotions.
  • The current dashboard wizard accepts CSV files. Export a spreadsheet as CSV before uploading it.
  • The current dashboard template determines operation-specific required columns. Do not reuse an older file without checking the template.
  • Processing time depends on the job. A file upload or support message does not guarantee immediate visibility, a fixed completion time, or a particular purchase-advice result.

Errors and recovery

  • Could not prepare the import. Please try again: retry the dashboard import. If preparation keeps failing, contact support with the selected webshop, promotion, and non-sensitive error text.
  • Promotions or the import option is missing: confirm the webshop, plan, feature access, and edit permissions. Contact your Customer Success Manager or support if access remains unclear.
  • Required identifier or column missing: add the required header, populate the identifier, and map every field marked with *.
  • Invalid file or formatting: save a non-empty UTF-8 CSV, remove blank rows and duplicate headers, and correct the row or column reported by validation before uploading again.
  • Products are not matched: check the chosen identifier and exact SKU, EAN, Article code, or Optiply ID against the existing Product.
  • Queued or Running job: wait and refresh Imports/Exports before starting a replacement job.
  • Complete with fails: review the failed rows, correct them, and import only those rows again. Review skipped counts even when the job says Complete.
  • Failed job: review the displayed message and selected promotion, correct the file, and retry. If the cause is unclear, contact support with non-sensitive job details.
  • Support-assisted file needs correction or is not visible yet: contact support with the file name and intended webshop; confirm its processing status before resending the whole file.

See Review import and export history for dashboard job states and row-count meanings.