Your Shopify export CSV or ZIP
- Shopify’s own product export, as Shopify gave it. Don’t edit or resave it.
- One CSV, a ZIP from Shopify, or several parts of one export chosen together.
- Whole products: every variant of each product in the file.
Shopify guide · files, results and limits
Check that your files fit, see what each result means, and know what must happen before an update reaches Shopify.
01 · Files
One file comes from Shopify, the other from your supplier. Rowvero matches each Shopify variant to a row in the supplier’s file.
Match rows by the same SKU or the same barcode
02 · Limits
Each check is one batch. A larger catalogue goes through in several batches. Keep every variant of a product in the same batch.
Very large files need more memory and can pause the page for several seconds while it works.
03 · Results
Every variant gets one result. The results fall under three headings.
Shopify has no manufacturer code, and the supplier’s file has one clear, usable code for it. Nothing changes until you approve it in the Full version.
Shopify already has a different code. Rowvero never replaces it. Check with your supplier which one is right.
A match that needs its own decision. For example, the same code may appear on another variant. An 11-digit number in a barcode column may be a UPC that lost its leading zero. Check the manufacturer’s original code before approving.
The code can’t go into the update. It doesn’t fit Rowvero’s current export format (below), it’s already on the variant as another type of barcode, or the variant already has 20 barcodes.
Rowvero can’t tell which supplier row is right, for example because a SKU appears twice, or the existing code in Shopify can’t be read. No fill is proposed.
Only when you match by barcode. The Shopify variant has no valid barcode to match on.
A match, but the variant has no barcode yet. The code would become its first barcode, which older connected apps may read as the product barcode. The Full version can keep it in your review reports, not in the update.
The supplier’s file has nothing for this variant. There’s nothing to fill.
The supplier’s row is there, but its code is empty.
The variant has no value in the column you chose to match by.
Both files have the same code. Nothing to change.
Rowvero accepts codes that meet these rules.
These are Rowvero’s export limits. A code Rowvero holds can still be a valid manufacturer identifier. Codes with letters such as ß, ø, æ, ł, đ and œ appear as “Unsupported update” and stay available in the review reports.
04 · Free
Run your own files through Rowvero’s matching, at no cost.
Free preview The free preview shows totals and up to eight examples.
Both files are read in your browser. Nothing is uploaded or saved, and a refresh clears them. A match is a starting point for review, not proof that the supplier’s code is right.
Matches that can’t go into the update can be kept in your review reports.
Barcode warnings on exact SKU matches need an individual decision. If a barcode points to a different record, correct the source files and compare again before updating that variant. When you reopen an older saved review, Rowvero clears the approval on any row with a new warning so you can review it again.
06 · Before Shopify
An update made from an old export can change more than you meant. Here are the risks, before you buy.
An outdated file can undo some later edits to the products it contains, such as a new title or status. It can also create a product you didn’t mean to, which may be live in your store with a zero price.
Rowvero compares the two export files you give it. It can’t verify when either was exported, and it doesn’t watch your store for edits made afterwards. That’s why edits must pause until the import finishes.
Guide last updated .
Back to the free preview