Quadro Design
Back to Insights

Shop-Script CSV Imports: Match Products, Prevent Duplicates and Check Stock

Importing a spreadsheet into a live online shop sounds straightforward until a matching mistake creates a duplicate product, a new stock value hides an item that is still on the shelf, or an incorrect price becomes visible before anyone checks it. The dangerous step is often not uploading a CSV...

Shop-Script CSV Imports: Match Products, Prevent Duplicates and Check Stock

Importing a spreadsheet into a live online shop sounds straightforward until a matching mistake creates a duplicate product, a new stock value hides an item that is still on the shelf, or an incorrect price becomes visible before anyone checks it. The dangerous step is often not uploading a CSV file; it is deciding what every row represents and which existing record may be changed. This guide presents a repeatable quality-control workflow for bulk product imports in Webasyst Shop-Script. It is written for catalogue managers, technical suppliers and used-parts sellers who need reliable updates without treating a spreadsheet as unquestionable truth.

Decide the job before preparing the file

Separate initial catalogue creation from updating known products. A first import may create categories, products and variants. A later price update should normally touch only identified existing records and the deliberately selected fields. A supplier's file may mix new products, revised descriptions, warehouse quantities and obsolete lines; processing everything in one pass obscures which action each row will perform. Write an import brief: source, responsible person, date, expected number of new records, expected number of updates, allowed fields, prohibited fields and the approval criteria. Identify the system of record for price, stock and product condition. A third-party sheet should not automatically override carefully inspected descriptions of individual used items.

Start from an export of the actual store

Before formatting a new CSV, export a small representative selection from the installed Shop-Script store. Include a simple product, a product with several SKUs, an item assigned to categories, and an item with multiple stock locations if the business uses them. The official Webasyst CSV import guide recommends obtaining a correctly formed example by exporting products, then using the result as a model. Check the actual installation, any import plugin and the available permissions: columns and behaviours may differ by version and configuration. Keep the original supplier file untouched, and make a separate working copy with an explicit version number.

Define product identity and SKU identity separately

A display name is not a trustworthy database key. Two parts may share a generic name yet differ in fitment, manufacturer reference or physical condition. Equally, one product may contain several sellable variants. Decide whether the import should identify existing products using Shop-Script's product ID, or identify SKUs using a stable code and the appropriate SKU identification mode. The official guide documents distinct identification options and explains that a SKU-only import can update SKUs without importing product or category records. For a catalogue of one-off used items, an internal unique part reference may be especially valuable. Do not replace an existing product merely because two titles look alike.

Map fields deliberately rather than trusting automatic detection

Create a mapping sheet with four columns: source column, destination property, example value and validation rule. Map product title and description separately from SKU code, SKU price, stock quantity, category, visibility and images. Check whether the file has one row per product or one row per variant. Shop-Script's documented CSV format supports an explicit row type for category, product and variant records; it also lets an operator review the automatic matching of CSV columns. Pay particular attention to fields with similar labels. A number that is an OEM reference is not necessarily the store's internal SKU. An empty purchase price is not a zero retail price, and a supplier's availability status is not necessarily your public stock figure.

Use a miniature test file to expose edge cases

Build a sample with perhaps eight to twelve rows, not a thousand. Include a known product to update, a new product, two SKUs belonging to one parent product, an item with a non-ASCII title, a field containing a comma, a missing optional attribute, a zero stock count and an intentionally invalid identifier. Ensure the CSV encoding, delimiter and quotation rules are correct: text with embedded delimiters must not silently slide into the next column. Compare imported values with a documented expected-result table, not just a successful import notification. Webasyst itself recommends trying a small number of rows before importing a larger set because major mistakes can be difficult to reverse.

Protect price, currencies and warehouse quantities

For monetary data, record the expected currency and whether values represent retail, purchase or comparison prices. A value such as 129.50 must not turn into 12950 because of decimal formatting. For stock, identify each physical warehouse and decide whether the incoming number is an absolute count or a change to be applied by another process. According to the Webasyst guide, a single stock column and warehouse-specific columns such as In stock @stock1 have different roles. Confirm the names in your own store before mapping them. If orders can be placed while an import runs, define how subsequent sales affect stock and whether a fresh reconciliation is required after the upload.

Treat categories, URLs and product media as protected assets

Never assume a CSV update will repair category assignments. The current Webasyst guide explains that category assignment through this import applies to newly imported products, while updating an existing product's data does not change its category assignment. Test your own configuration before relying on that behaviour. Be careful with storefront URL slugs: changing a product's URL can break existing links and search traffic unless a redirect plan is in place. Image fields deserve their own checks. A filename may point to a local import directory, while a URL may cause an image to be retrieved. Verify the image belongs to the exact item, especially when each used part has distinctive marks.

Record a before-and-after change report

For a bulk run, save an export of the affected records before making changes and obtain a recoverable backup under the site's normal operational policy. After the test import, produce a comparison report: created product IDs, updated product IDs, changed SKUs, prices, warehouse quantities, visibility flags, image counts and errors. Look for unexpected changes to products not in the input file. Count duplicates using stable identifiers, not just repeated names. Check whether the system imported all intended rows and whether any were rejected, skipped or merged. A simple spreadsheet comparison often catches errors that a green completion message cannot show.

Inspect real storefront behaviour before approving a larger run

Open several affected product pages on desktop and mobile. Verify the correct photo, model information, clear condition notes, price, stock availability and functioning add-to-cart action. For variants, change the selection and confirm that price and availability correspond to the selected SKU. Use a safe checkout test only where it is appropriate and approved. If the catalogue feeds eBay or other sales channels, check that newly imported identifiers do not create duplicate marketplace listings and that the direction of stock synchronisation remains deliberate. A successful database update is not the same as a correct end-to-end selling experience.

Choose an import method by risk, not only convenience

A one-time, carefully reviewed CSV is sensible for a controlled catalogue launch or occasional corrections. Repeat imports from several suppliers need stronger ownership rules, error reports and defined conflict handling. A continuously changing inventory may need an integration with product matching, incremental updates and monitoring rather than manual files. Custom automation is justified only after the underlying data has consistent identifiers and a clear source of truth. Schedule imports outside critical trading periods when practical, keep an operator available to resolve exceptions, and document the rollback or correction process. Do not assume a generic plugin can make unreliable supplier data safe automatically.

Release only when you can explain every change

The safest import is one whose operator can answer which records were created, which were updated, which fields were deliberately left alone and how the outcome was checked. Begin with a small file, review matching rules and field mapping, compare the results and only then scale the operation. That approach protects customer-facing accuracy while making future catalogue work easier to maintain. If a Shop-Script store needs a more reliable structure for product data, catalogues or repeated imports, Quadro Design's eCommerce development service can help assess the existing workflow and plan an appropriate implementation without promising a one-click solution.

Need a store that is easier to use and easier to grow?

We design eCommerce websites with clearer structure, better product presentation, and stronger foundations for search, marketplaces, and long-term scale.

Request a Quote View Services

Request a Quote

Send Products for Review

Upload 2-5 product samples and we'll prepare a free listing preview.

No file selected

Discuss Your Project

Tell us a bit about your project and we'll get in touch to discuss the details.