Batch SKU deletion and bulk barcode import

The Catalog API now covers two operations you previously had to work around: deleting parent and child SKUs in batches, and loading barcodes in bulk from a file, a BigQuery table, or an inline list.

SKU deletion

Endpoint	Summary
POST /v1/sku/parent/delete	ParentSkuDelete — deletes parent partner SKUs / ZSKU parents. This cascades: every associated child SKU is deleted with it.
POST /v1/sku/child/delete	ChildSkuDelete — deletes individual partner SKUs / child ZSKUs.

Both accept batches. Because parent deletion cascades, check what sits underneath a parent before you call it.

Bulk barcode import

Endpoint	Summary
POST /v1/import/generate-import-signed-url	GenerateImportSignedUrl — returns a signed URL for uploading a file straight to GCS. Accepts csv, tsv, json, xlsx, xlsm, and parquet.
POST /v1/import/barcode	CreateBarcodeImport — starts an import from exactly one source: file_url, bq_table, or inline items.
GET /v1/import/status/{reference}	GetImportStatus — returns current status and a processing report: success and failure counts, progress, and completion timestamps.

The usual flow is to call GenerateImportSignedUrl, upload your file to the URL it returns, pass that file_url to CreateBarcodeImport, then poll GetImportStatus with the returned reference until it completes. If your data already lives in BigQuery you can skip the upload and pass bq_table instead.

Full request and response shapes are in the Catalog section of the API reference.