Product catalog and CSV import
Import products through the merchant dashboard, then use the read-only widget product endpoint to map storefront products to Closku IDs.
Reviewed by Closku documentation team ·
Catalog input and ownership
The current workflow uses the merchant Products area and CSV import. Closku reads exports shaped for Shopify, WooCommerce, BigCommerce, or a generic CSV. Preview parsed names, images, and variants before confirming; export formats can differ.
Import creates Closku records. It is not live storefront sync or a catalog upsert API. Re-importing can create duplicates; retain an ID mapping and reconcile existing products before repeating an import.
name,sku,color,size,image_url,status
Blue T-shirt,TEE-BLUE,Blue,M,https://YOUR_IMAGE_HOST/blue-tee.jpg,activeFor a generic CSV, name identifies the product; sku, color, and size carry product and variant details. image_url supplies an accessible image, and status should be active for widget visibility. Up to four product images are supported. This row is illustrative; use your actual product and image.
Read-only widget data
GET /api/widget/products?merchantId=MERCHANT_UUID returns active products under products:
| Field | Meaning |
|---|---|
id | Closku product UUID for requests and storefront mapping |
name, sku | Display name and optional SKU |
primaryImage | First ordered product image URL, or null |
variants | Variant id, color, size, sku, and imageUrl |
The endpoint does not translate platform IDs. Map them to Closku IDs before setting data-product-id or submitting a job.
Images and garment categories
Use clear, well-lit images showing the full garment and accurate color. Aim for at least 1000 × 1000 pixels as catalog-quality guidance; importing does not make a low-resolution image suitable by upscaling it. Check that every imported image is present.
CSV product-image URLs must use HTTPS and a public hostname, without embedded credentials. Localhost, literal IP addresses, and hostnames resolving to private or local network addresses are rejected. Each redirect is checked, with at most two redirects, and downloads over 15 MiB are rejected. Use direct product-image URLs and review any unreachable, too_large, or download_failed import results.
These remote URLs are for merchant catalog images. Shopper-photo submission is different: the widget sends a base64 image data URL, not a remote shopper-photo URL.
The rendering path distinguishes tops, bottoms, and one-piece garments. Category metadata can use category, garment_category, or garmentType. Missing or unknown values currently fall back to one-piece processing. Verify categories with Closku rather than assuming every CSV field is imported or every non-apparel product is automatically rejected.
Keep size charts and fabric details accurate for shoppers. The documented product response does not provide size-chart or fabric-simulation fields. AI size recommendation is planned and is not currently available.
Catalog maintenance
- Assign someone to maintain the storefront-to-Closku ID mapping.
- Review active status, variant labels, image downloads, and import errors before publishing.
- Reconcile source-store changes through available product tools and support. No live catalog sync is included in this workflow.
- Test affected products after changes to images, variants, categories, or themes.
Next steps
Install with mapped product IDs.
Read and submit a mapped product.
Related pages
Plan catalog operations.
Read the product endpoint contract.