Job shopify-csv-import-merged-or-overwrote-products · revised 11 October 2026
Put products back after a Shopify CSV import overwrote them
A corrective product file and change report restore the fields and variants an import replaced or blanked, proved on a test store that first shows the same damage, before you touch the live one.
You might be seeing
- Product descriptions, vendors or tags are empty after an import
- A product that had sizes and colours now has a single default variant
- Prices or SKUs on existing products changed to values from the spreadsheet
- Images are missing or attached to the wrong products
No passwords, keys, card details or admin invites needed to start.
What usually happened
Shopify matches import rows to existing products by their URL handle. With the overwrite option on, matching products take the values in the file, a blank cell in a column that is present clears the stored value, and variant columns without their option columns can remove variants. Shopify keeps no import history and cannot cancel an import in progress, so the damage is only visible by comparing the file with the products.
Who it’s for: Owner or merchandiser of a Shopify store who imported a product spreadsheet and found existing products changed, blanked or stripped of variants.
Usually starts when: An import finished, then product descriptions, prices, vendors or variants on products you did not mean to change were replaced or emptied.
The result: For the products you agree were affected, a test store loaded with the damaged products first differs from a reference you choose, and after a corrective file is imported a fresh export matches that reference in the agreed columns and variants, with no differences.
Check whether this job fits
Four questions, about two minutes. Your answers stay on this page unless you choose to email them.
Checks you can run yourself
Compare headers before anything else
Open the file you imported and a fresh export side by side and read the column headers.
Look for: Headers are case sensitive, so a lowercase handle column does not match. A column present but empty is read as blank, which clears the stored value.
Look at the store activity log
Open your store activity log and filter to the day of the import.
Look for: A burst of product changes at one time confirms which products the import touched.
What you get
- The corrective file in Shopify import format, UTF-8, with the exact headers the import expects
- A row-by-row change report: product, column, value found, value restored
- The before and after comparison from the test store: the damaged state against the reference, then the restored state against the reference
- A one-page explanation of what the import did and how to avoid repeating it
- Import steps for your live store, including a fresh backup export first, and how to reverse it
Included
- Comparing three files you send: the export from before the import, the file that was imported and a fresh export of the current products
- Finding which products, columns and variants were replaced, blanked or removed, and why the import did it
- A corrective product file limited to the agreed handles and columns
- A test-store check: load the test store with the damaged products, show it differs from the reference, import the corrective file and show the differences are gone; then a short import guide for your live store
Not included
- Importing into your live store; you or your administrator run that import
- Restoring the old variant IDs, which a spreadsheet cannot do once option values were changed
- Stock counts for stores with more than one location
- Rebuilding data that no reference file or source system holds
- Customers, orders, discounts, collections membership, apps or theme display problems
How we know it’s done
Agreed with you before work starts. Each check produces evidence you keep.
Before the corrective import, the test store seeded from the current export differs from the reference in the damaged columns and variants, and those differences match the damage on the live store
Evidence: A comparison listing each product and column that differs from the reference, with the seeded test-store export and the current live export
After the corrective import on the test store, a fresh export matches the reference in every agreed column for every agreed product
Evidence: A comparison listing each product and column with zero differences, and both export files
Each corrected product has the reference number of variants, with the same option names, option values, SKUs and prices
Evidence: A variant table for each product, reference against test store
The corrective file contains only the agreed handles and columns, so no other product changes
Evidence: A list of handles and headers in the file, and a test-store export showing untouched products unchanged
The corrective file imports on the test store with no row errors
Evidence: Screenshot or text of the import result, with store details removed
Sign-off. You review the comparison and sign off on the test-store result before payment. Importing into your live store is a separate step you take.
If it fails. If the checks do not pass, you do not pay, and we hand over what we found so anyone can continue.
When it fits, and when we stop
It fits when
- A file or export exists from before the import, or the supplier or source system can produce one for the affected products
- You can send the file that was imported and a current product export, with no customer data in them
- You, or someone you authorise, can create a separate test store, such as a development store, and run an import there
- Fewer than 100 products are affected, or you accept a quote for more
We stop and tell you if
- No reference exists for the damaged fields and the source system cannot supply one
- Subscription, bundle or inventory apps depend on the old variant IDs and cannot be re-pointed; we explain and quote that part separately
- The products were also edited by hand after the import so there is no single right value, and nobody can choose
- The damage is in orders, customers or payments rather than product data
What could go wrong
The live store is not changed by us. The handover says to export the live products first, so you can import that export to undo a corrective import. Test-store changes are discarded when you delete the test store.
Scroll the table sideways to read it all.
| Risk | How we handle it |
|---|---|
| The corrective import itself overwrites something else | The file holds only agreed handles and columns, the test store shows the effect first, and you export the live products before importing. |
| Product images no longer download from their old addresses | We list image rows that fail in the test import and ask you for working image links; we do not guess images. |
| Customer or supplier data is sent by mistake | We ask for product columns only, tell you which to remove, and delete the files after sign-off. |
A second reviewer checks that the corrective file touches only the agreed handles and columns, that no customer data is in any file, that the test store was first shown to hold the damaged state, and that the comparison afterwards was done on a fresh export.
How we deliver
We arrange the work and independent review, then show you the result against the agreed checks. You keep authority over your systems.
- Check the three files open correctly: UTF-8 text, expected headers, one row per variant
- Match products by handle and list every column and variant that differs from the reference
- Explain why the import changed each one, including the overwrite setting, blank cells and missing option columns
- Build a corrective file limited to the agreed handles and columns
- Seed your test store from the current (damaged) export, then export it and confirm it shows the same damage as live and differs from the reference in the listed columns
- Import the corrective file on the test store, re-export and compare with the reference
- Independent review of the comparison, then hand over the file, report and live import steps
This is a one-off job, not emergency cover or a subscription. We confirm eligibility, the total price, a start window and a delivery date before you accept. Work starts only after agreed inputs, secure access, any licences and necessary permissions are in place. Platform, app and supplier charges are excluded unless the written quote includes them. No charge or booking is created by an enquiry.
Need to keep it working?
Discuss a before-import checklist and a test-store dry run for future bulk imports as a separate agreement.
Ongoing work is separately scoped and quoted: no monitoring, response-time guarantee or automatic subscription is included in this job.
Explore an ongoing engineering lane, or mention the responsibility you need in your enquiry.
What you can check
This is a new service. We have not delivered this job for a client yet.
Other ways to get this done
- If you still have a recent complete export, importing it back with overwrite on a test store first may be enough. Check one product before doing it on the live store.
- Shopify support or a Shopify Partner can help with a large or urgent restore, and can see account details we do not.
Questions
Will you import the file into my live store?
No. You run the live import with our steps, after exporting your live products first.
Can you bring back the old variant IDs?
No. A file cannot restore IDs Shopify discarded when option values changed. We list the products affected so an app vendor can re-link them.
What if I never exported before the import?
We need some reference for the right values, such as a supplier file or an older export. Without one this fixed job does not fit.
Send an enquiry
Send us
- Which products and columns look wrong, with two or three public product links
- When the import ran, and whether the overwrite option was ticked if you remember
- Whether you have an export from before the import, and its approximate date
- How many products were in the imported file and how many look affected
- Whether the store has more than one stock location
Later, once you agree
- The three product files, with any customer data removed and sent by the agreed secure route
- A separate test store you create and own, where you or your administrator run the damaged-state load and the corrective import
- Who chooses the right value where the reference and the imported file disagree
- A company-controlled secure handoff agreed before access: no live passwords, keys, private code or customer records by ordinary email.
You keep the live store, its admin logins and all customer data. We work from product files and your test store, and we never log in to the live store or run an import on it.
Email fallback: open your mail app
If website submission is unavailable, review and send the fallback email yourself. An email fallback is not a website receipt. Or write to hello@syntheticindustry.ai with “shopify-csv-import-merged-or-overwrote-products” as the subject.