Setting up a client with thousands of codes? Skip the product-by-product editing. Load all their aliases in one CSV, then export the same file later to fix and re-import.

📌 Heads up: Requires SKU Aliases to be switched on. If it’s off, you won’t see the import type or the export action.

Import aliases

1. Go to Imports and click Import CSV.
2. Choose SKU Aliases as the import type.
3. Click Template to download the file with the right columns.

4. Fill in one row per alias and upload it.

The Imports list shows how many rows went in and how many were refused. Click the download icon on the row for the error report.

Working across clients? Set Customer to “Customer from row” and put the client’s name in each row. One file can cover several clients.

🚨 If a row fails, only that row fails. The rest of the file still goes in. If another product already uses the alias SKU, the error names that product and links to it. A code held only by a different client isn’t a clash.

Fix or retire aliases

Upload the same sku + alias again and Packiyo updates the alias instead of adding a second one.

• New type? It replaces the old one.
• active = no switches the alias off.
• delete = yes removes it, but only if it has never matched an order line. Otherwise you’ll get “Deactivate it instead,” and the alias stays.

See who changed what

Every alias the import creates or changes is written to the product’s Product Log under the name of whoever uploaded the file.

Export aliases

1. Go to Products.
2. Click Export SKU Aliases, the plain download arrow next to Export Products.
3. Read the note and click Export. The file shows up on the Exports page when it’s ready.

The file uses the same columns as the import, so you can edit it and upload it straight back with nothing changed.

⚠️ The export ignores your Products list search and filters. You get every alias for the selected customers. Aliases whose master is archived or deleted are left out.

Good to know

• One alias file at a time, per client. Wait for it to finish before uploading another. Two files processed at once can both claim the same alias SKU.
• Save as plain CSV, not “CSV UTF-8.” Excel’s UTF-8 option adds an invisible mark that triggers “Missing required columns: sku.” This affects every import type.
• Use lowercase yes and no. “Yes” and “No” with capitals get refused.
• Error report row numbers run one low. Your 4th data row shows as row 3.
• Hover to tell the icons apart. The Products page icons have no labels.
• The column is headed alias, not “Alias SKU”. That’s intentional, so the template imports back as is.