How to import cross-sell, up-sell and related products
Import product relationships (cross-sell, up-sell, related) into Elovate with a simple file.
Important: only link to SKUs that already exist in Magento/Elovate. If you reference a SKU that is created later in the same file, the link will fail (the target doesn’t exist yet).
Best practice is a two-step flow: create/update products first, then run a links-only import.
1) Prepare your file
Minimum columns
sku(the product that gets the links)cross_sell(comma/semicolon separated SKUs)up_sell(comma/semicolon separated SKUs)related(comma/semicolon separated SKUs)
Example
sku | cross_sell | up_sell | related |
base-1001 | 1234,1245 | 2001;2002 | A100,A101 |
base-1002 |
| 2003 | A102;A103;A104 |
Use a multi-value delimiter your workspace supports (
,or;). You can set/confirm the multi-select delimiter under Settings → Import settings.Do not include non-existent SKUs in these columns. First import/create them, then link them.
Safer alternatives if you must create and link in one go
Split into two files:
products (create), 2) product links (cross/up/related).
Or run two jobs: schedule the links-job to start after the products-job is Done.
2) Create the import job
Go to Apps → Import → Add new import job.
Upload CSV/Excel or select a Google Sheet.
Choose the target store view and other options as needed.
3) Map your columns
In Mapping:
sku→ SKUcross_sell→ Product Links → Cross-sell SKUsup_sell→ Product Links → Up-sell SKUsrelated→ Product Links → Related SKUs
4) Validate, then import
Click Validate to check structure and targets.
If validation passes, open the job, review the preview, and click Run Import.
Monitor Import Status and spot-check a few products in Magento.
Notes & tips
New products: don’t link to SKUs created later in the same file—this will error. Run links after products exist.
Delimiters: match your file’s delimiter to the multi-select delimiter configured in Elovate (
,or;).Large batches: consider splitting links across multiple files (by category/brand) to simplify troubleshooting.
Rollback: if a link set is wrong, you can re-import the correct links or, where applicable, use your revert flow to restore the previous state.
Troubleshooting
“SKU not found” / “Target not found”
The cross/up/related list contains a SKU that doesn’t exist yet. Import/create the target SKU first, then re-run links.“Invalid delimiter / cannot parse list”
Your file uses a different separator than configured. Align the multi-select delimiter or standardise the file.“No changes detected”
The exact same link set is already present; nothing to update. Add or remove links to trigger a change.
Summary: Import product links in a second pass against existing SKUs, map to Product Links fields, and use the correct multi-select delimiter. This avoids “SKU not found” errors and makes your cross-sell, up-sell and related relationships reliable from the start.