# Import suppliers with a CSV file

## Purpose

Use the Supplier import to add or update many Supplier profiles in one job. For more than 50 records, use an import instead of editing Suppliers one by one.

This is a Supplier-level import. Supplier-product relationships use [Import supplier products](/article/import-supplier-products).

## Prerequisites

Before you start:

- confirm that imports are enabled and that you can edit Suppliers for the selected webshop;
- prepare a UTF-8 CSV file with one header row and one row per Supplier;
- decide whether the file adds new Suppliers or updates existing Suppliers;
- confirm which values are owned by Optiply and which are synchronized from a connected system; and
- download the current template. The template and columns marked with `*` are the authority for that operation.

Use [Manage and configure suppliers](/article/the-supplier-page) for a small number of individual changes.

## Steps

1. Open **Suppliers** and select **Import to Optiply**.
2. Choose **Add new suppliers** or **Update existing suppliers**.
3. For updates, choose **Optiply ID** or **Supplier name** as the identifier. Supplier creation skips this identifier step.
4. Download the template and prepare the CSV for the selected operation.
5. Upload the CSV file.
6. Under **Match columns**, map every required Supplier field. Leave unrelated CSV columns unselected.
7. Under **Check for errors**, resolve missing columns, duplicate mappings, blank values, and invalid formats.
8. Correct the file and upload it again when validation reports errors.
9. When all required columns are matched and all rows are valid, select **Import**.
10. Open **Settings > Data management > Imports/Exports** to track the job.

### Create suppliers

Choose **Add new suppliers** for Supplier profiles that do not yet exist. Include `name` and all fields marked with `*` in the current template. The wizard does not ask you to select an update identifier for this operation.

### Update suppliers

Choose **Update existing suppliers** for Suppliers already in Optiply. Use **Optiply ID** where available, or **Supplier name** when it uniquely identifies the intended Supplier. Review the reported validation and job outcome for rows that are not matched.

## Fields and columns

The update identifier and every field marked with `*` are required. The current template is authoritative if it differs from this baseline backend reference.

| Column | Required or optional | Meaning and format |
| --- | --- | --- |
| `id` / Optiply ID | Required when selected for update | Numeric Optiply Supplier identifier. |
| `name` | Required for creation; required when used as update identifier | Supplier name, up to 255 characters. |
| `emails` | Required in the baseline model | One or more valid email addresses in the format shown by the template. |
| `minimumOrderValue` | Required in the baseline model | Minimum order value as a decimal without a currency symbol. |
| `fixedCosts` | Optional | Fixed ordering costs as a decimal. |
| `deliveryTime` | Optional | Delivery time as a whole-number period in the unit used by the template. |
| `userReplenishmentPeriod` | Optional | Manual replenishment period as a whole number. |
| `reactingToLostSales` | Required in the baseline model | Boolean that controls reaction to lost sales. |
| `lostSalesReaction` | Required in the baseline model | Non-negative decimal reaction value. |
| `lostSalesMovReaction` | Required in the baseline model | Non-negative decimal moving reaction value. |
| `backorders` | Required in the baseline model | Boolean that enables backorder handling. |
| `backorderThreshold` | Required in the baseline model | Decimal from `0` through `1`. |
| `backordersReaction` | Required in the baseline model | Non-negative decimal reaction value. |
| `ignored` | Required in the baseline model | Boolean indicating whether Optiply should ignore the Supplier. |
| `maxLoadCapacity` | Optional | Positive decimal, up to two decimal places. |
| `containerVolume` | Optional | Positive decimal container volume, up to two decimal places. |
| `globalLocationNumber` | Optional | GLN containing exactly 13 digits. |
| `type` | Operation-specific | Supplier type. Use an offered value such as `vendor` only when it appears in the current template or wizard. |

Do not place Supplier-product MOQ, Lot Size, Supplier-product price, or Product-specific Lead time in a Supplier-profile import.

## Expected result

A successful create job adds the accepted Supplier profiles. A successful update job changes matched profiles. The Imports table shows total, succeeded, failed, and skipped rows. After completion, refresh Suppliers, verify a sample of profiles, and check related Supplier products separately.

## Limitations

- Only CSV files are accepted.
- Supplier names can be ambiguous; prefer Optiply ID for updates when available.
- Required fields differ by operation. The current template and `*` markers win over an older saved file.
- Invalid planning periods, booleans, decimals, email lists, GLNs, or agenda values are rejected.
- Integration-owned fields can be synchronized again after the import. Confirm ownership before uploading.
- Starting a job does not establish a universal processing time.

## Errors and recovery

### Before the job starts

- **Only .csv files are allowed:** save the file as CSV and upload it again.
- **Empty, unreadable, oversized, or non-UTF-8 file:** export a supported 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, email, date, enum, GLN, or length error:** correct the reported row and column using the displayed format, then upload again.
- **Ambiguous Supplier name:** use Optiply ID or make the identifier unambiguous before retrying.

### Import job states

- **Queued:** the job is waiting to start. Wait, then refresh Imports/Exports.
- **Running:** processing is still active. Wait before evaluating the final counts.
- **Complete:** confirm that succeeded and skipped counts match expectations and inspect a sample of Suppliers.
- **Complete with fails:** some rows succeeded. Correct only the failed rows and import those rows again.
- **Failed:** review the displayed message, operation, and identifier, correct the file, and retry. If the cause remains unclear, contact Optiply support with the selected webshop, job date, and non-sensitive error text.

See [Review import and export history](/article/imports-exports) for all job columns and outcome meanings.
