Catalog management
Import and maintain your clothing catalog in Closku, with clear images, active products, and a reliable mapping to storefront product IDs.
Reviewed by Closku documentation team ·
Import a sample first
Use Products → Import CSV in the merchant dashboard. The importer reads Shopify, WooCommerce, BigCommerce, and generic export formats. Preview product names, images, colors, sizes, and status before confirming.
Your plan sets a limit on how many products you can keep in your Closku catalog: 50 products on Starter, 150 on Growth, and 300 on Scale. Enterprise plans are custom. The limit counts your total catalog, not a single import, so delete unused products before importing more — deactivating a product does not free space in your limit. See the pricing page for the current limits and contact support to raise yours.
Start with a few products and inspect the import result. An unreachable or failed image can leave a product without a usable garment image. CSV import adds records; it does not automatically keep source-store changes synchronized or safely update every existing product on re-import.
Review the catalog reference for a generic CSV example and the read-only product endpoint.
Use suitable product photography
Choose clear, well-lit images showing the complete garment, with accurate colors and minimal obstruction. Aim for at least 1000 × 1000 pixels as catalog-quality guidance. The current importer keeps up to four product images and compresses uploaded images; it does not upscale a low-resolution image into a better source.
Use direct HTTPS image URLs on a public hostname for CSV imports. Credentials in the URL, local or private network hosts, literal IP addresses, excessive redirects, and downloads over 15 MiB are rejected. Check image errors in the import result and replace an inaccessible or oversized source before retrying.
Check that the imported image is visible and belongs to the correct product. Keep the photo consistent with the variant being previewed. If a variant-specific image is not available, the rendering path can fall back to a product image.
Categories, variants, and sizing
The clothing rendering path distinguishes tops, bottoms, and one-piece garments. Confirm category configuration with Closku and test representative products; unknown or missing metadata currently falls back to one-piece processing. Shoes, jewelry, and non-apparel products are outside the documented clothing workflow.
Review variant colors, size labels, and IDs after import. Retain a mapping from your store product to its Closku product UUID. A SKU or a platform product number alone does not establish that mapping.
Keep your garment measurements and size chart visible for shoppers. AI size recommendation is planned and is not currently available; try-on previews do not replace size information or guarantee fit.
Keep a catalog change log
- Assign a catalog owner and record your source export date.
- Check for duplicates before importing a revised export.
- Reconcile changed photos, variants, and active products through available dashboard tools and support.
- Retest the product mapping after catalog or theme changes.
- Keep your size chart and product descriptions accurate in the storefront.
Next steps
Install and test the mapped catalog.
Review submission and rendering outcomes.
Related pages
Read CSV and widget product fields.
Check missing images and failed imports.