Purpose
Prerequisites
Before you start:
- confirm that imports are enabled and that you can edit Products for the selected webshop;
- prepare a UTF-8 CSV file;
- use one row per Product and one header row;
- remove duplicate headers;
- confirm that the Products already exist and that your identifiers match the intended records; and
- download the Product CSV example from the wizard. Use the wizard's Match columns and Check for errors screens for the fields and requiredness of this update operation; the example file is a starting point, not a complete required-field specification.
Use Manage products for a small number of individual changes.
Steps
- Open Data import and choose Import products, or use Products > Import to Optiply where offered.
- Continue in Update existing products mode; this Product flow does not offer an Add-new operation.
- Choose the identifier used consistently in your CSV: Optiply ID, EAN code, SKU code, or Article code.
- Download the Product CSV example as a starting point and prepare the CSV for existing-Product updates.
- Upload the CSV file.
- Under Match columns, map each column in your file to the corresponding Optiply field. Map every required field and leave unrelated columns unselected.
- Under Check for errors, review missing columns, duplicate mappings, blank values, and invalid formats.
- Correct the CSV and upload it again when the validation screen reports errors.
- When required columns are matched, validation has finished without blocking errors and Import is available, submit once. An empty error list alone does not establish successful validation or a completed job.
- Use Go to imports after the processing-started confirmation where shown, or open Settings > Data management > Imports/Exports, to track the job. Started is not completed; wait for the final status and verify the resulting Products.
Updates, not Product creation
This CSV flow updates existing Products. The selected identifier determines which Product each row targets. Include only the supported values you intend to change, together with every column the wizard marks as required. Review the reported validation and job outcome for rows that are not matched.
A missing Product is not an Add-new CSV job in this flow. Confirm the supported Product-creation route with your administrator or CSM before proceeding; do not use an undocumented import path.
Fields and columns
The selected identifier is required. Follow the Product update wizard's required-column and validation messages for accepted fields, requiredness and formats; do not infer them from the example CSV or an older saved file. Only map fields offered by your update wizard. The reference below explains identifiers and common field meanings; it does not mean that every field is available in every import.
| Column | Required or optional | Meaning and format |
|---|---|---|
id / Optiply ID | Required when selected as identifier | Numeric Optiply Product identifier. Recommended for updates when available. |
eanCode | Required when selected as identifier; otherwise optional | EAN code as text. Keep leading zeroes. |
skuCode | Required when selected as identifier; otherwise optional | SKU code as text. Follow the length limit shown by the wizard. |
articleCode | Required when selected as identifier; otherwise optional | Article code as text. Follow the length limit shown by the wizard. |
name | If offered, follow the wizard’s required-column messages | Product name. Follow the length limit shown by the wizard. |
price | If offered, follow the wizard’s required-column messages | Product price. Use the numeric format accepted by the wizard; do not include a currency symbol. |
stockLevel | If offered, follow the wizard’s required-column messages | Stock level. Use the number format accepted by the wizard. Confirm that this field is owned by the import rather than a connected system before using it. |
notBeingBought | If offered, follow the wizard’s required-column messages | Boolean value indicating that purchasing is paused. Use the boolean format required by the update wizard. |
resumingPurchase | If offered, follow the wizard’s required-column messages | Date on which purchasing resumes. Use the date format accepted by the wizard. |
status | If offered, follow the wizard’s required-column messages | Product status. Use a value accepted by the update wizard. |
assembled | If offered, follow the wizard’s required-column messages | Boolean value indicating whether this is an assembled Product. |
minimumStock | If offered, follow the wizard’s required-column messages | Minimum stock value. Use the number format accepted by the wizard. |
ignored | If offered, follow the wizard’s required-column messages | Boolean value indicating whether Optiply should ignore the Product. |
Expected result
After validation, Optiply starts an import job. A successful update job changes the matched existing Products; it does not create missing Product records. The history page shows total, succeeded, failed, and skipped row counts. Verify a sample of changed Products before relying on the imported values for purchasing.
Limitations
- Only CSV files are accepted by this wizard.
- A Product identifier must be consistent and unique enough to match the intended Product.
- The wizard can reject empty, oversized, unreadable, non-UTF-8, or duplicate-header files.
- This guide covers existing-Product updates, not creation. Required and optional fields follow the update operation; the wizard’s mapping and validation messages win over the static example CSV or an older saved file.
- Fields synchronized from a connected webshop or other integration can be overwritten again. Confirm field ownership before importing those values.
- Starting a job does not establish a universal processing time.
Errors and recovery
Before the job starts
- Could not prepare the import. Please try again: check whether a job started before retrying. If preparation keeps failing, contact Optiply support with the selected webshop, operation, and non-sensitive error text.
- Only .csv files are allowed: save the file as CSV and upload it again.
- The file is empty / failed to read / is not UTF-8: export a non-empty UTF-8 CSV and retry.
- Duplicate columns: remove or rename duplicate headers.
- Required columns missing: add and map every field marked with
*. - Blank, number, integer, boolean, date, or length error: correct the reported row and column using the displayed format, then upload the corrected file.
- Validating / validation failed: wait while validation is in progress. If it fails, correct or re-export the file and upload it again; a disabled Import button is not evidence of successful processing.
- Invalid date or integer range: where these checks are offered, correct the calendar value or use a number within the displayed field limits. Keep the mapping's accepted date format consistent; a valid-looking format alone does not prove backend acceptance.
- Too many values in a row: check the separators and quote values containing commas. The preview shows only the first three affected lines and can indicate more; inspect the complete file rather than only those examples.
Import job states
- Queued: the job is waiting to start. Wait, then refresh Imports/Exports.
- Running: processing is still in progress. Do not start a replacement job just because the counts are incomplete.
- Complete: processing finished. Confirm that the succeeded count matches what you expected and review skipped rows.
- Complete with fails: some rows were accepted and others failed. Correct only the failed rows, create a new CSV for those rows, and import them again.
- Failed: the job stopped unexpectedly. Review the displayed message and file setup, correct any identified issue, and retry. If the cause remains unclear, contact Optiply support with the selected webshop, operation, identifier, job date, and non-sensitive error text.
See Review import and export history for all job columns and outcome meanings.