Catalog
Sync product data cleanly to the Closku platform. This page covers the catalog data model, supported product types, image requirements, and synchronization best practices.
Catalog data model
Closku catalogs are organized by merchant account. Each product in the catalog requires the following fields:
| Field | Type | Required | Notes |
|---|---|---|---|
| product_id | string | Yes | Your internal product identifier |
| title | string | Yes | Product display name |
| category | enum | Yes | top, bottom, or dress |
| image_url | URL | Yes | Minimum 1000×1000px, JPEG or PNG |
| size_chart | object | Recommended | Size measurements for accurate fitting |
| fabric | string | Recommended | Material composition for drape simulation |
| color_variants | array | Recommended | Available colors with matching images |
Supported categories
The virtual try-on engine supports three product categories. Tops include shirts, blouses, jackets, hoodies, and other upper-body garments. Bottoms cover pants, skirts, shorts, and other lower-body garments. Dresses include one-piece garments that cover both upper and lower body. Products outside these categories will not render: shoes, jewelry, and non-apparel items are not supported, though accessories and footwear are on the future roadmap.
Sync guidance
Synchronize your catalog in a way that makes partial updates safe to replay. Use the catalog API to push product updates incrementally, and validate image resolution at the 1000 by 1000 pixel minimum before submitting. Handle webhook confirmation events to verify sync completion. Catalog drift becomes expensive when ownership is unclear, so define which system owns each field. Validate inputs early and make catalog issues visible before they leak into customer-facing workflows: downstream try-on logic should never depend on silent catalog assumptions.
Related pages
Catalog API endpoints.
API credential management.