Sync Piro Data

Upload fresh Piro exports and the BC catalog to the database. Do this once a week — the whole team can then generate imports without uploading files.

Upload Files

Run weekly

Files are read in your browser and sent in small chunks. Sync time depends on file size and your connection speed.

Item Type Attributes Report

Sheet: Table

Item Types Report

Sheet: ItemTypes

BC Catalog Export

Export from BigCommerce → Products (.csv) — include Custom Fields

Amazon Listings Report

Seller Central → Reports → All Listings Report (.txt)

GTIN Backup Export

Internal GS1/GDSN export — fallback Name/stone code/Size (.xlsx)

How this works

Once a week (you): Export the two Piro files, the BC catalog CSV, and the Amazon Listings report, drop them here, click "Sync Piro Data" — whatever's attached uploads together in one pass.

Anytime (anyone on the team): Open Generate page, paste newness SKUs, click Generate. No files needed.

The sync overwrites: Every sync replaces all data with fresh exports so prices, stock, stone codes, and product URLs stay current.

BC Catalog export: Go to BigCommerce → Products → Export, and make sure the export template includes Custom Fields. This lets the tool reuse existing product URLs on re-imports (avoiding duplicate URL errors) and powers Product Filter.

"Sync BC Catalog" / "Sync Amazon Listings" / "Sync GTIN Backup" buttons: Only needed to re-sync just that one file on its own, outside the weekly routine.

GTIN Backup export: An internal GS1/GDSN product export from another system, keyed by the same SKU format as Piro. Used as a fallback for Name, stone code, and Size whenever Piro's own fields are blank — not needed weekly, only re-sync it when a colleague sends a fresh copy.

Owner: Christian manages this sync. If it errors or the data looks off, reach out to him before re-running.