Bulk updates

CSV imports and exports

Use CSV files to set up or maintain SKUs and supplier items in bulk. TrueSKU imports are designed to update existing records where possible, not create accidental duplicates.

Safe re-import rule: export a CSV, edit supported fields, then re-import it. Existing records are matched by their stable identifier and updated where possible.

SKU CSV imports

SKU CSV import is used for creating and maintaining normal SKU records. Existing SKUs are matched by the sku column within your account.

What you want to do	How it behaves
Create new SKUs	If the SKU code does not already exist, TrueSKU creates a new SKU. A name is required for new SKUs.
Update existing SKUs	If the SKU code already exists, TrueSKU updates supported fields on that SKU instead of duplicating it.
Edit descriptions/names in bulk	Export the SKU CSV, edit the `name` and other supported fields, then re-import it with the same `sku` values.
Change stock quantities	Do not use the SKU CSV importer. Stock quantities must be changed through stock movements, sales, purchase orders or stock takes.

Common SKU columns

Supported SKU import columns include sku, name, image_url, barcode, location, notes, custom_attributes, sync_excluded, stock_mode, reorder_threshold and is_dead.

Important: keep the sku column stable when re-importing. If you change the SKU code, TrueSKU treats it as a different stock record.

Supplier Item CSV imports

Supplier item imports are normally run from inside a supplier's item page. That means the import already knows which supplier you are working on.

Identifier	Used for	Required?
`supplier_item_id`	Exact update of a supplier item from an exported file.	Optional. Useful for export/re-import.
`order_code`	The supplier's product/order code. Used to find existing supplier items within the current supplier.	Yes for normal imports.
`supplier_id`	Internal TrueSKU supplier reference used in exports and API/debugging.	No for normal imports from a supplier page.
`supplier_name`	Human-readable reference in exports.	No. It helps you read the file but is not normally needed for matching.

If supplier_item_id is present, TrueSKU can use it for an exact update. If it is not present, TrueSKU updates by order_code within the supplier you are importing into.

Common Supplier Item columns

Common supplier item columns include order_code, name, cost_price, currency, lead_time_days, pack_qty, moq, tax_rate, barcode, location, notes, active, discontinued and min_stock.

Listing CSV mapping (bulk edit and linking)

Export your channel listings, edit them in a spreadsheet, then re-import to bulk-update multiplier, sync exclusion and SKU links at once. Rows are matched by listing_id_required, the internal id already filled in on export - don't change that column.

Column	What it does
`listing_id_required`	Matches the row back to a listing in your account. Required, and must come from an export or the mapping template.
`stock_multiplier`	How many units of the SKU this listing represents. Leave blank to leave unchanged.
`sync_excluded`	Set to `1` to exclude this listing from outbound stock sync. Leave blank to leave unchanged.
`linked_sku`	Type a SKU code to link (or relink) this listing to that SKU. Leave blank to leave the current link unchanged.

Note: a blank linked_sku cell always means "leave as-is" - it never clears an existing link. To unlink a listing, use the Unlink button on the Listings page instead.

The remaining exported columns (channel, store, external ids, title, current SKU, active status, last seen) are for reference only and are ignored on import.

Large catalogues

The export has no size limit, and respects the filters you have set on the Listings page (for example "unlinked" only), so you can export every listing in one file. Each import file can contain up to 5,000 rows. To link a larger catalogue, split the file into several files of 5,000 rows or fewer and upload them one after another - the import message tells you if a file was cut short so you can upload the rest. You only need the listing_id_required and linked_sku columns in the files you upload. If a listing appears more than once in the same file, only its first row is used.

Tax rate format

Use plain numeric values in CSV files.

VAT rate	CSV value
20% VAT	`20`
Zero-rated	`0`
Reduced 5% VAT	`5`

Do not include the percent sign unless the import screen specifically says it supports that format.

Barcode and location behaviour

Supplier item barcode and location can be imported.

These are useful when your supplier spreadsheet is your cleanest source of operational data.

Creating a SKU from a supplier item copies useful fields.

When a new SKU is created from a supplier item, barcode and location are copied across where available.

Existing curated SKU data should not be overwritten casually.

If a SKU already has a barcode or location, treat changes as deliberate data maintenance rather than automatic guessing.

Recommended spreadsheet workflow

Download the template or export.

Use the template for first imports, or export existing records when you want to update them.

Edit only the fields you mean to maintain.

Do not change stable identifiers like SKU code or supplier order code unless you intend to create or rename records.

Preview before applying.

Use the import preview to check creates, updates, unchanged rows and errors.

Apply the import.

TrueSKU validates the file and reports what changed.

Good practice: for supplier-first onboarding, import supplier items first, create SKUs from supplier items, then link marketplace listings to those SKUs before enabling outbound stock sync.