Open Imports/Exports

  1. Open Settings.
  2. Expand Data management.
  3. Select Imports/Exports.

If an expected tab is missing, confirm that you selected the intended webshop and that your user can access Settings.

Track and recover an import job

Purpose

Use the Imports tab to confirm whether a CSV import is waiting, running, complete, partly successful, or failed, and to decide what to do next.

Prerequisites

Start the import from one of the supported workflows, then note the selected webshop, entity, and operation. The history page shows up to the last 20 available import jobs from the previous year.

Steps

  1. Open Settings > Data management > Imports/Exports and select Imports.
  2. Review the latest history. Where it refreshes automatically, let the current refresh finish; use refresh when another read is needed.
  3. Locate the job by its name, source, operation, and import date.
  4. Check Status first, then compare Total records, Succeeded, Failed, and Skipped.
  5. If the job is still queued or running, wait and refresh later.
  6. If some rows failed, review the actual affected records before preparing a correction import. For Sell orders, check the orders and their lines and contact Optiply Support if the result is unclear; do not resubmit the whole upload or assume that every line needs importing again. For other entities, follow that entity's recovery instructions and include only records that still need processing.
  7. Return to the affected Products, Suppliers, Supplier products, orders, or promotion and verify a sample of the accepted changes.

Fields and columns

ColumnMeaning
NameJob name used to identify the run.
SourceEntity or source processed by the job.
OperationWhether the job adds new records or updates existing records.
Date of ImportDate and time at which processing started.
Total recordsRecords in the job's displayed unit. For order imports, distinguish orders from their separate order-line count.
SucceededRecords reported as successfully processed, in that job's unit.
FailedRecords reported as unsuccessful, in that job's unit.
SkippedRecords reported or calculated as skipped for that entity and layout. This is an outcome count, not another job status; a blank value is not a verified zero.
StatusCurrent or final job state.

Expected result

A finished job displays Complete, Complete with fails, or Failed. Review the outcome counts and actual records. A Complete job can still contain skipped records, so completion alone does not mean that every intended record changed.

Read Sell-order and Buy-order counts

For order imports, the displayed order total is not the number of CSV order lines. In the summary-based layout, it combines succeeded, failed and existing/skipped orders; updated counts are not added to that total. When an information tooltip is offered beside the total, it shows the separate Sell-order-line or Buy-order-line count. A missing order summary can leave the total and skipped value unavailable even when a line count is known.

Older Sell-order job views can use distinct nonblank order identifiers from the uploaded file to count orders, and older or incompletely read jobs can lack that count. Do not substitute the number of uploaded lines. A blank or unavailable skipped value is not proof of zero skips, all rows skipped, or successful persistence. A toast or processing-started dialog is not a substitute for the final job and actual result.

For a Sell-order CSV upload, invalid lines or lines that do not match exactly one Product can be left out while the order is processed with its remaining valid lines. The order's total value is calculated from only those retained lines. Orders with no valid lines, or orders identified as already imported, can be skipped. An order-level outcome does not confirm that every uploaded line was imported. Check the actual orders and lines before deciding what needs correction; do not retry the whole upload on the strength of the counts alone.

View skipped Sell orders

Where View skipped sell orders is offered for a Sell-order job, open it to inspect the returned record identifiers and reasons. Details load when you open the panel. While they load, wait for the result. If the panel says The skipped sell orders could not be loaded, the details are unavailable; this does not mean that no orders were skipped. This is a read-only preview, not a retry action or complete export.

  • It keeps the first 50 returned skipped records and the 10 most frequent reasons. Other reasons accounts for remaining reason counts.
  • Read any Showing the first … of … note before treating the displayed list as complete.
  • The preview is based on returned details; its count is separate from the overall Skipped summary column. No available details does not prove that nothing was skipped.
  • Return to the final job status and verify the relevant records before deciding what, if anything, should be corrected or retried. Opening the preview does not re-import them.

Limitations

  • The page shows up to the last 20 available jobs in the requested history window; it is not an unlimited archive.
  • Counts can be incomplete while a job is running.
  • Import history records the outcome but does not prove that an integration-owned field will not be synchronized again later.
  • Processing time depends on the job and cannot be promised from this page.

Errors and recovery

  • Queued: the job is waiting to start. Wait and refresh; do not submit the same file again immediately.
  • Running: the job is processing. Wait for a final state before comparing totals.
  • Complete: processing finished. Confirm succeeded and skipped counts and verify a sample of records.
  • Complete with fails: some records succeeded and others failed. Verify the actual result before preparing corrections. For Sell orders, inspect the orders and their lines and ask Support when the outcome is unclear; do not blindly re-import the file.
  • Failed: review the displayed message, operation, source file and actual records. Correct identified issues before considering a retry. An unclear Sell-order result requires checking the orders and lines first, not assuming nothing was imported.
  • No job appears: confirm the selected webshop and refresh. A newly triggered job can take time to appear.
  • Cause remains unclear: contact Optiply support with the selected webshop, source, operation, date, status, counts, and non-sensitive error text. Never send passwords or access tokens.

Start a CSV import

Where enabled, open Data import from the main menu. In the top-bar layout, look for the import icon after the webshop selector and its Data import tooltip; it may not be a text-labelled button. Settings > Imports/Exports remains the place to follow job progress. Earlier layouts instead offer Import in the Imports/Exports header. Use the entry point actually offered for your webshop and account.

  1. Open Data import, or the older Import entry where shown.
  2. Choose the entity offered by the picker: Import products, Import suppliers, Import supplier products, or Import sell orders. Older layouts can show shorter entity names. These are entity choices, not new import types; not every choice is available to every account.
  3. Follow that entity's operation and identifier steps. Products update existing Products, not create missing Products. Suppliers and Supplier products offer their own create/update choice. Sell orders use their creation flow; the identifier selection identifies the Products in the order lines, not the order's own identifier.
  4. Prepare and map the CSV using the fields, required-column markers and formats offered by that wizard. A downloadable example is a starting point, not a complete required-field contract.
  5. Resolve validation issues and submit once. If a job is queued or running, wait for its final state and check its outcome before starting another import.
  6. When Import started appears, Go to imports opens job progress. The dialog means processing has begun, not that rows have successfully imported.

Promotion-product imports stay inside the selected promotion's workflow; this entity picker is not a way to create multiple promotions from one master file. A missing or disabled entry does not establish a backend error or justify bypassing access controls. If job status cannot be read, do not assume that the interface has prevented overlapping jobs.

Use the relevant entity guide for preparation:

Do not reuse a CSV layout from another entity or operation. Download the current example for the job you are starting and follow the actual offered mappings, not a field list inferred from the example.

Validate the CSV before submission

  • Match every field marked required by the selected entity's wizard. Check missing columns and cells rather than relying on a successful file upload alone.
  • Use the accepted date format shown for the mapped field and keep it consistent within the file. There is no single date-format instruction that applies across every mapping or wizard version. A displayed expected format is guidance, not proof of backend date acceptance.
  • Where calendar validation is shown, correct impossible dates or times as well as their written format. Follow a displayed integer-range or numeric-length message for that field; this does not make negative values valid everywhere or establish a universal business limit.
  • If a row has too many values, check separators and quote values containing commas. The error preview can show only the first three affected lines and indicate that more exist; it is not a complete error export or a guarantee that every malformed CSV is detected.
  • Validating is still in progress. A validation-failed or unreadable-file message requires correction and reupload; an empty error list or disabled Import button is not a successful job result.

Export-history overview

The Exports tab lists generated files with their name, file type, source, creation date, status, and available actions.

Use refresh to request the latest list. Open a row's actions to rename an export or download the generated file when those actions are available.

Table-control overview

Use Column view to choose, hide, or reorder columns. The tables can also support sorting, resizing, and pinning columns. Saved layouts and available columns can differ between Imports and Exports.

Review generated exports

Purpose

Review generated export history, rename an available file, and download the intended export for offline use.

Prerequisites

  • Open Settings > Imports/Exports > Exports.
  • Confirm the webshop and expected export type.
  • Wait for the export job to finish before downloading it.

Steps

  1. Find the export by type, creation time, status, or file name.
  2. Review its status and available actions.
  3. Rename the file when a clearer local reference is needed.
  4. Choose download and save the generated file.
  5. Open the file and verify that it matches the expected export job.

Fields and columns

  • File name, export type, and creation time — identify the generated export.
  • Status, rename, and download actions — describe availability and supported file operations.

File name, export type, creation time, status, and available rename or download actions identify each generated file. Exact columns depend on the current table configuration.

Expected result

The intended completed export has a clear name where changed and is downloaded for review.

Limitations

  • Export history is a snapshot of generated jobs, not live synchronized data.
  • Rename changes the export-file label, not underlying Product, Supplier, or order data.
  • Availability and retention can depend on account configuration.

Errors and recovery

  • If no file appears, confirm the Exports tab, filters, webshop, and job status.
  • If download is unavailable, wait for completion and verify access before retrying.
  • If the file is wrong or stale, generate or select the correct export rather than editing it as a source of truth.

Adjust the tables

Purpose

Choose, order, pin, hide, or resize Imports and Exports columns so job results can be reviewed efficiently.

Prerequisites

  • Open the Imports or Exports history table.
  • Wait for the table to finish loading.
  • Decide which job fields are needed for the current review.

Steps

  1. Open the table's column control.
  2. Show required columns and hide unnecessary ones.
  3. Reorder, pin, or resize columns where those controls are available.
  4. Close the control and review the resulting layout.
  5. Reset or adjust the layout if required job information is hidden.

Fields and columns

  • Import file, type, status, succeeded, failed, and skipped — describe import history.
  • Export file, type, status, creation time, and actions — describe generated export history.

Import tables can include file, type, status, succeeded, failed, skipped, and time information. Export tables can include file name, export type, status, creation time, and actions.

Expected result

The current table presents the fields needed to review import or export jobs without changing job data.

Limitations

  • Column controls change presentation only and do not change job status or outcomes.
  • Available columns differ between Imports and Exports.
  • A hidden column still exists in the job data when the interface provides it.

Errors and recovery

  • If a column is missing, reopen the control and clear search within the column list if available.
  • If the table is empty, clear job filters and confirm the selected webshop and tab.
  • If layout changes do not persist, keep the required columns visible for the current review and retry after reloading.