Move a 3D print product spreadsheet into a product library
Import or merge accepted parent-product fields, review duplicate decisions, then add variants and review material or packaging assignments inside PlyOps.
What changes when a spreadsheet becomes a product library?
Moving from a spreadsheet to a product library means choosing one durable parent-product record from repeated rows, importing supported product fields, and then adding or reviewing its variants inside that product.
By Knisley 3D Solutions LLCPublished
- Best first step
- Choose one parent-product row and preserve variant-only columns
- Import inputs
- CSV, TSV, XLS, XLSX, or pasted table data
- Write safeguard
- Map product fields, review duplicates, validate, then confirm
- Data ownership
- Free CSV export and versioned JSON backup
Start with the product, not the row
A spreadsheet often repeats the same description, brand, category, and notes for every size or color. Before importing, mark the fields shared by the whole product and the fields that truly change by variant.
The current spreadsheet importer creates or merges parent-product records; it does not reconstruct variants from repeated rows. Consolidate repeated rows or select one representative parent-product row for the import. Keep the original source so variant names, variant SKUs, dimensions, and option values remain available when you add or review variants inside the product afterward.
- Choose a stable parent product name
- Select or consolidate one parent-product row for the current import
- Preserve variant rows and variant-only columns in the original source
- Separate shared descriptions from channel-specific copy
Map the columns you already trust
The current importer accepts parent-product names, base SKUs, categories, general descriptions, public tags, product dimensions, optional internal and packed dimensions, and Etsy, Shopify, or eBay descriptions. It does not assign variants, prices, materials, packaging supplies, or inventory from spreadsheet columns.
PlyOps supports CSV, TSV, XLS, XLSX, and pasted table data. The current mapping step shows how accepted source headers will become product fields before anything is committed. Leave variant-name, variant-SKU, and other variant-only columns unmapped; add those records within the imported product afterward.
Use one template row for each parent product
The downloadable CSV uses only headers recognized by the current generic importer. Its fictional examples show dimensions, shared tags, and separate Etsy, Shopify, and eBay description fields without implying variant reconstruction or library assignments.
Replace or remove the example rows before importing your own catalog. If your source has one row per size or color, first choose or consolidate one parent-product row and preserve the variant rows in the original spreadsheet for the follow-up step inside PlyOps.
Resolve duplicates before the library changes
An exact SKU is stronger evidence than a similar title. PlyOps separates exact, likely, and possible duplicates so you can compare the imported row with the existing record and choose what to keep.
Imported marketplace descriptions stay in the matching marketplace slot unless you explicitly choose a different outcome. The general description is not silently replaced.
- Review each row as create, merge, or skip
- Confirm field conflicts one decision at a time
- Keep the source spreadsheet until the result is verified
- Download a fresh JSON backup after the migration
Add and review variants after the parent import
Open each imported parent product and add the real size, color, material, or bundle variants from the preserved source. A variant can then carry its own SKU, dimensions, weight, material, packaging, notes, and marketplace identifiers where the values genuinely differ.
This follow-up is deliberate: it prevents repeated spreadsheet rows from becoming duplicate parent products and avoids claiming an automatic parent-and-variant reconstruction that the current importer does not perform.
Choose the storage tradeoff that fits your shop
PlyOps Free keeps product records in the current browser. It is a practical starting point for one-device work, but browser storage is not automatic backup or multi-device sync.
PlyOps Cloud adds hosted backup, sync, private file storage, and access across devices. Paying changes where the library is stored and how it travels; it does not buy back ownership of your basic data.
Keep adjacent workflows in their proper place
Spreadsheet import does not turn PlyOps into an accounting ledger or unattended marketplace publisher. Connected marketplace actions remain seller-reviewed.
Start with the reviewed CSV template
A CSV with three fictional parent-product examples and only fields the current generic importer maps. Keep one row per parent product, review every proposed action, and add variants inside PlyOps after import.
Common questions
Does my spreadsheet need to be perfect before I import it?
No. Keep the original file, remove rows you know are obsolete, and identify which columns describe the parent product versus a variant. The current spreadsheet importer creates or merges product records; preserve variant-only values in your source and add or review variants inside the product afterward.
Will an import overwrite my existing product records?
Not without review. For each row, choose create, merge, or skip. Exact, likely, and possible duplicates stay visible so you can resolve field conflicts before confirming the write.
Do I need PlyOps Cloud to replace a spreadsheet?
No. PlyOps Free stores the library in the current browser and includes generic CSV export and JSON backup. Cloud adds hosted backup, sync, private file storage, and multi-device access.