When is CSV import worth using?

Use it when a Konfig has enough parts that manual selection becomes slow, such as larger diagrams, manufacturer lists, or catalogue migrations.

What does the marker column do?

The marker column tells Konfigr which numbered diagram position each product should belong to.

What should I check before importing the CSV?

Check product identifiers, marker numbers, duplicate SKUs, missing values, repeated parts, and variant references before importing.

How should repeated parts be represented in a CSV?

Represent each diagram position clearly while still pointing back to the same Shopify product where the part is identical.

What should I do immediately after import?

Review the imported parts, place or adjust hotspots on the diagram, then test the marker-to-product relationships.

How do I bulk import parts into a Shopify diagram?

Prepare a CSV from your Shopify product data, add marker numbers for the diagram positions, import it into the Konfig, then review and place the hotspots.

What information should be in a parts import CSV?

It should include the product or variant identifier, the marker number, and any other fields required to map the product to the correct Konfig position.

Can CSV import handle repeated spare parts?

Yes, as long as the spreadsheet clearly maps the same product to each relevant marker position.

Why should I check variants before CSV import?

If the diagram needs a specific variant, the import must identify that variant correctly. Otherwise the wrong option may appear in the Konfig.

Importing Parts in Bulk with CSV

CSV import is for bigger Konfigs

Adding products manually is fine when a Konfig has a handful of parts.

It becomes slow when the diagram has thirty, fifty, or a hundred parts. It is also slower when you are migrating from a manufacturer list, a spreadsheet, or an existing parts catalogue.

That is when CSV import makes sense.

The goal is simple: prepare the parts in a spreadsheet, include the marker information, then import them into the Konfig instead of selecting everything one at a time.

Start from Shopify products

The parts should already exist in Shopify.

Konfigr links to Shopify products. It is not a separate product creation tool for building your whole catalogue from nothing.

Start by exporting the relevant products from Shopify or preparing a list that clearly identifies the products you want to add.

Use stable product identifiers where possible. Product IDs, variant IDs, SKUs, or handles can all help depending on the import format you are working with.

Add the marker column

The marker column is what connects each product to a numbered position in the Konfig.

If the diagram has marker 1 for the lid, marker 2 for the basket, marker 3 for the seal, and marker 4 for the impeller, your CSV should reflect that mapping.

This turns the spreadsheet from a product list into a diagram plan.

Do not rush this part. A clean marker column saves time later. A messy one creates cleanup work after import.

Use the diagram while preparing the spreadsheet

Keep the diagram open while you prepare the CSV.

Work through the image in order. Assign marker numbers logically. Check that the product in the row is the product you actually want attached to that marker.

If the diagram is already numbered, follow that numbering where it makes sense. If the old numbering is messy or does not match what you sell, create a cleaner sequence.

The spreadsheet should reflect the customer-facing diagram, not just your internal product list.

Handle repeated parts deliberately

Some parts appear more than once on a diagram.

A screw, washer, clip, O-ring, or bracket may have several positions. In your CSV, make sure that repeated use is represented clearly.

Depending on the import structure, that may mean assigning multiple marker positions to the same product or including repeated rows for the same product with different marker numbers.

The point is to avoid creating duplicate Shopify products just because one part appears several times.

Check for duplicate SKUs before importing

Duplicate SKUs can create confusion during bulk setup.

Sometimes duplicate SKUs are legitimate. Sometimes they reveal old product records, variants that were not cleaned up, or copied products that should not exist.

Before importing, scan the CSV for duplicates, missing values, and inconsistent formatting.

Fixing those issues in the spreadsheet is usually faster than fixing them after import.

Watch variant products carefully

If a part is a specific variant, make sure the CSV identifies the right one.

A product-level reference may not be enough if the Konfig needs a particular size, side, voltage, colour, or configuration.

Use variant information where needed so the imported item points to the correct option.

This matters most when your Shopify catalogue uses variants to represent different spare parts under one product.

After import, place the hotspots

CSV import helps get the products and marker relationships into the Konfig.

You still need to check the visual placement on the diagram.

After import, review the marker list and assign or adjust hotspot positions on the image. Make sure the marker location matches the part, not just the spreadsheet row.

The CSV gets you most of the way there. The diagram still needs a human check.

Test the imported Konfig

Once the import is complete and hotspots are placed, test the page.

Click each marker. Check the matching item. Confirm products, variants, marker order, and any repeated parts. Look for obvious mistakes like marker 12 pointing to the marker 13 product.

Bulk import saves time, but it can also import mistakes quickly if the spreadsheet is wrong.

Testing is part of the workflow, not an optional extra.

Use CSV when it saves real time

CSV import is not required for every Konfig.

If the diagram has eight parts, manual setup may be faster. If the diagram has sixty parts, CSV import can keep the process manageable.

Use the method that fits the job.

The best CSV import is not complicated. It is simply a clean product list with clear marker mapping, checked before and after import.