Bulk adjustments via CSV

Available on: Pro Plus.

When you have many lines to adjust, import them from a CSV instead of adding them one at a time. Use it after a count done outside Stockie, a stock write-off, or a data cleanup.

The import fills in a draft adjustment. Nothing is written to Shopify until you apply it.

Importing

  1. Go to Adjustments   and create an adjustment as normal.
  2. Choose the location.
  3. Instead of adding products by hand, import your CSV.
  4. Review the draft that comes back.
  5. Apply it.

The file format

Two things are required:

Column Required
SKU or BARCODE One of the two
QTY Yes - QUANTITY also works

QTY  is the amount to adjust by, not the new total. A row of -5   removes five units; a row of 12   adds twelve. This is the opposite of a stocktake, where you enter the quantity you counted.

Values must be whole numbers and cannot be zero. A file can hold up to 5,000 rows - split anything larger.

What happens to rows that do not match

Rows are matched against products already in your store, by SKU or barcode. A row matching nothing is not imported, and no product is created for it.

A row missing its quantity is reported with its row number so you can fix it.

Check the number of lines in the draft against the number of rows in your file. If they disagree, some rows did not match - usually a SKU that differs from the one in Shopify, or a barcode with a leading zero that a spreadsheet has eaten.

Reasons

The import brings in products and quantities. Set the reasons on the adjustment afterwards, in the draft, before applying.

A reason is required before an adjustment can be applied, so an imported draft cannot be applied until you have set them.

Review before you apply

An imported draft is a normal draft - editable, deletable, and safe to leave alone until you are happy with it.

Once applied, it locks. There is no undo, and the notes cannot be edited afterwards. See Adjustments lock after apply.

Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.

Still need help? Contact Us Contact Us