Purpose
Prerequisites
Before you start:
- confirm that imports are enabled and that you can edit Supplier products for the selected webshop;
- make sure the relevant Products and Suppliers can be identified in Optiply;
- prepare a UTF-8 CSV file with one row per Supplier-product relationship;
- decide whether the file adds new relationships or updates existing relationships; and
- download the current template. The template and columns marked with
*are the authority for that operation.
For a few relationships, use Connect products and suppliers.
Steps
- Open Products > Supplier products and select Import to Optiply.
- Choose Add new supplier products or Update existing supplier products.
- Choose the Supplier identifier: Optiply ID or Supplier name.
- Choose the Product identifier: Optiply ID, EAN code, SKU code, or Article code.
- Download the template and prepare the CSV with both identifiers on every row.
- Upload the CSV file.
- Under Match columns, map each CSV column to its Optiply field. Map the selected Supplier and Product identifiers and every other required field.
- Under Check for errors, resolve missing columns, duplicate mappings, blank values, and invalid formats.
- When all rows are valid, select Import.
- Open Settings > Data management > Imports/Exports to track the job.
Create supplier products
Choose Add new supplier products when the Product-Supplier relationship does not yet exist. Each row must identify both sides of the relationship. Include the required Supplier-product attributes shown by the template.
Update supplier products
Choose Update existing supplier products when the relationship already exists. Optiply uses the selected Supplier and Product identifiers together to target the row. Review the reported validation and job outcome for rows that are not matched.
Fields and columns
Both selected identifiers and every field marked with * are required. The current template is authoritative if it differs from this baseline reference.
| Column | Required or optional | Meaning and format |
|---|---|---|
| Supplier identifier | Required | Optiply ID or Supplier name, as selected in the wizard. Use the same identifier type for every row. |
| Product identifier | Required | Optiply ID, EAN code, SKU code, or Article code, as selected in the wizard. |
name | Required when adding new Supplier products | Name of the Supplier-specific Product, from 1 to 255 characters. |
skuCode | Required in the baseline Supplier-product model | Supplier SKU, from 1 to 255 characters. |
price | Required in the baseline model | Non-negative decimal purchase price. Do not include a currency symbol. |
eanCode | Optional unless selected as the Product identifier | EAN code as text, from 1 to 255 characters when supplied. |
articleCode | Optional unless selected as the Product identifier | Supplier article code as text, from 1 to 255 characters when supplied. |
minimumPurchaseQuantity | Optional | Positive whole-number minimum purchase quantity. |
lotSize | Optional | Positive whole-number purchasing lot size. |
status | Optional | Supplier-product status. Use ENABLED or DISABLED when the template offers this field. |
preferred | Operation-specific | Boolean indicating whether this is the preferred Supplier relationship. |
availability | Operation-specific | Boolean availability value in the format shown by the template. |
availabilityDate | Operation-specific | Availability timestamp in YYYY-MM-DDTHH:mm:ssZ format. |
freeStock | Operation-specific | Available Supplier stock as a numeric value. |
weight | Operation-specific | Supplier-product weight as a numeric value in the configured unit. |
volume | Operation-specific | Supplier-product volume as a numeric value in the configured unit. |
deliveryTime | Operation-specific | Product-specific delivery time as a whole number in the unit used by the template. |
Expected result
A successful create job adds the accepted Supplier-product relationships. A successful update job changes matched relationships. The Imports table reports total, succeeded, failed, and skipped rows. Verify a sample of Product-Supplier links and purchasing values after completion.
Limitations
- Only CSV files are accepted.
- Both identifiers must point to the intended records. Prefer stable IDs or codes where possible and verify the reported job result when using names.
- Required fields can differ between create and update. Follow the downloaded template and
*markers. - This import manages Supplier-product relationships, not Supplier profile fields or general Product fields.
- Integration-owned price, stock, SKU, or other fields can be synchronized again after the import. Confirm ownership first.
- Starting a job does not establish a universal processing time.
Errors and recovery
Before the job starts
- Missing Supplier or Product identifier: add and map both selected identifier columns.
- Required column missing: add every field marked with
*and remap the file. - Duplicate headers or mappings: keep each CSV header once and map one source column to each Optiply field.
- Blank or invalid value: correct the reported row. Prices must be non-negative decimals; quantities and lot sizes must be positive whole numbers.
- CSV, UTF-8, empty-file, or file-size error: create a supported non-empty UTF-8 CSV and upload it again.
Import job states
- Queued: wait for the job to start, then refresh Imports/Exports.
- Running: processing is still active; wait before deciding that rows are missing.
- Complete: verify the succeeded and skipped counts and inspect a sample of relationships.
- Complete with fails: accepted rows were processed, but some rows failed. Correct the failed relationships and re-import only those rows.
- Failed: the job stopped unexpectedly. Review the displayed message and the two identifier choices, correct the file, and retry. Contact Optiply support with non-sensitive job details if the cause remains unclear.
See Review import and export history for job-column meanings.