Stocky import: troubleshooting and FAQ

File and upload problems

• "This file does not look like a CSV" : you uploaded a spreadsheet (.xlsx, .numbers) or a PDF. In Excel, Numbers, or Google Sheets choose Save As or Download and pick CSV, then upload that.
• "That file is empty" : the file has no data. Choose a file that contains your rows.
• "CSV has no header row" : the first line should be your column names. Remove any blank rows above them, then re-save.
• "The file appears to be malformed (an unterminated or misplaced quote)" : there is a stray double-quote in a text field. Fix it near the line shown, or re-export a fresh copy from Stocky (a clean export usually fixes it).
• Garbled accented characters (for example "é" instead of "é"): re-save the file as CSV UTF-8 and upload again.
• "That file is larger than 30MB" : split it into smaller files and import them one at a time. A file can also have too many rows; that message appears when you run the Preview, not at upload.

Messages about specific rows

• "N lines across M records could not be imported" : those product lines could not be matched (most often because the products have not finished syncing from Shopify). The records imported without those lines. Finish syncing, then re-import.
• "Line variant not found" : the line could not be matched by Shopify id, SKU, barcode, or name. Sync the product, or fix the SKU or barcode, then re-import.
• Missing or zero quantity : give that line a valid quantity.
• Missing identifier (a PO number, adjustment number, or supplier name) : fill in the missing value, or delete the row if it is junk.
• "A date couldn't be parsed" : the record still imports, stamped with the import date. To keep the real date, use the YYYY-MM-DD format and re-import.
• "Unrecognized currency, left blank" : use a three-letter code (USD, EUR, GBP). Note that a three-letter typo such as "UDS" is accepted as-is, so double-check your codes.
• "Duplicate supplier, first row used" : the same supplier name appeared more than once; only the first row was used.
• "Location not found" (stocktakes and adjustments): create the location in Organizely first (locations are not created for you), then re-import.
• "not_adjusted" rows skipped : expected. Those adjustments were never actually applied in Stocky, so they are left out on purpose.
• "Required fields not matched" or "Nothing would be imported" : go back to the Match columns step and make sure the required fields are matched to real columns.

When an import is "already running"

Frequently asked questions

• Will this create duplicates? No. Purchase orders, adjustments, and suppliers are matched by their Stocky id (or by name for suppliers); stocktakes are matched on the file's contents. Re-importing the same data updates the existing records in place instead of creating duplicates, so it is always safe to fix and re-import.
• Will it change my live Shopify stock? No. Everything imports as history; your current on-hand quantities stay in sync with Shopify.
• How long does it take? A few seconds for small files, a few minutes for large ones. Large imports run in the background, so keep the tab open.
• Can I undo an import? There is no one-click undo. For purchase orders, adjustments, and suppliers, fix your file and re-import (it updates in place). For a stocktake, delete it and re-import. If you imported the wrong thing entirely, contact support.
• What if my products are not synced yet? Some lines will be skipped. Finish syncing your products, then re-import; the skipped lines will come in.

A few terms

• SKU / barcode: short codes that identify a product.
• Variant: one specific version of a product (for example, Medium / Blue).
• Dry run / preview: a safe check that shows what would happen without saving anything.
• Upsert: "update if it exists, otherwise add". This is why re-running is safe.
• Historical record: a record of something that already happened; it does not change your live stock.

Need help?