We have over 13,000 parent items in our store and currently need to bulk edit about 4,000.
can we upload a list and what format does it have to be in to accomplish this?
We also have the app Meatfield guru if there are any solutions using that.
you can bulk edit your 4,000 products by uploading a CSV file in Shopify. The file needs to be formatted with the same column structure Shopify uses, which includes things like Handle, Title, Variant SKU, Price, Inventory, etc. If you’re making specific edits, you only need to include the columns you’re changing.
Since you have Metafield Guru, you can also bulk update your custom metafields using their import/export feature. That means if you’re editing product details beyond the basic Shopify fields (like extra descriptions, dimensions, or special tags), you can use Metafield Guru to do it faster.
- Export a CSV of your products from Shopify Admin > Products > Export (so you have the right format).
- Make your changes in Excel or Google Sheets.
- Upload the file back to Shopify or use Metafield Guru if updating metafields.
For a 4,000-product change, I would treat this as two separate jobs: standard product fields through Shopify CSV and custom metafields through a metafield-aware tool or the admin bulk editor.
Before running the full update, export the current products, test 5-10 products, and confirm that the exact metafield namespace, key, and type are unchanged after import. The risky part is not only getting values in; it is noticing if unrelated fields or existing metafields changed during the same pass.
Hasan’s split is right, and there is a third job hiding under it: knowing what the 4,000 looked like before the update, in a form you can write back.
A metafield CSV round trip has no undo. If the namespace or key is off by one character, or a value lands in the wrong column, Shopify accepts the file and you find out from a product page a week later. Test on five to ten products first, as he says. Then, before the full run, export the current values of exactly the metafields you are about to change, so the rollback file exists before the mistake does.
Better than an export is a copy that updates as products change, because a store with 13,000 products does not stand still while you prepare the file. StoreVault keeps that copy per product, metafields included, shows the list of fields a restore would write before it writes them, and only touches the fields that moved. A bad batch on 4,000 products becomes 4,000 targeted writes instead of a second CSV you also have to get right.