CSV import/export for SKU's and BarCodes from products page and orders page
We really need more robust import/export options for bulk editing and for reporting. For example, what we'd like is the ability to bulk export SKUs to a .csv from the products page, make changes, and then bulk import the updates. This would make it easy to make updates and changes in bulk in MS Excel.
Also the ability to export only the products and kits that are currently awaiting shipment would be helpful. This way we can manipulate the data in Excel and create our own pick lists, bar code labels, kit labels, etc. on the fly rather than having to pre-package all the unbarcoded stuff. I would think this functionality would be very useful to anyone who uses a lot of kits and who sells a significant amount of unbarcoded products.
Christopher Schleyer
shared this idea
It’s now possible to make a selection of orders and export all items in those orders to a CSV file so the data can be used as needed. The export can be arranged so that skus from all selected orders are totaled, or so sku totals are broken down order by order.
-
Good suggestion. While the Backup & Restore function can be used to update product attributes using a spreadsheet editor it's really just intended as a means for backing up products data. All product data is backed up in CSV files. These files are downloaded in a zip archive can be edited and then uploaded with the Restore function.
That said, this works well for simple edits that need to be made across many products, however it is not well suited for creating kits.
It should be possible to have kits backed up separately with kit items appearing one per line so kits could be created with the Restore. I'm not aware of any software that exports kits in this way though I'm sure they exist. My thought is, if each kit item needs to be hand entered into the spread sheet, in many cases it may be as fast or faster to build the kit in GroovePacker. The exception would be situations where each kit has many similar variations, these would be better suited to a spreadsheet.