Key Takeaway
- Use the Company Library to organize shared assets such as fabrics, trims, block patterns, avatars or dummies, and brand logos.
- Upload a new file version to update an existing Content; use Linked Contents to connect separate Parent and Child Contents.
- Review designs with viewpoint-based Annotations and Content-level Comments, which can be filtered to show comments across versions or only the current version.
CLO-SET’s Company Library provides a shared space for teams to organize brand logos, virtual fabrics and trims, block patterns, avatars or dummies, and other commonly used content. See Company Library – CLO-SET for setup and access details.
Step-by-Step Asset and Revision Workflow
- Organize shared resources in Company Library Workrooms and Child-Workrooms by asset type, such as block patterns, avatars, fabrics, and trims.
- Use the Company Library to manage reusable assets such as block patterns, fabrics, and trims; the Component Library guide explains how to set up shared Workrooms for these resources.
- Upload 3D garments as Style Content. Since June 2026, non-CLO files such as images and PDFs can also be assigned a Content Type during upload; selecting Style makes BOM and POM options available for those Contents.
- Upload a newer file as a version of the same Content, or—after setting up CLO-SET Library in CLO 3D—link a newly uploaded Content to its Parent. Linked Contents are not compatible with version uploads.
- Review available information on the Content Page, including BOM, POM, and Cost Estimation, and use Content-level Comments for discussion.
Organizing Reusable Apparel Components
A library only stops duplicate work when designers can find verified building blocks faster than they can recreate them on a local drive. When teams organize their shared catalog, they can draw from common asset categories across their workspace:
- Block patterns for pattern development
- Virtual fabrics for material application
- Trims for garment detailing
- Avatars or dummies for 3D fitting
- Brand logos for consistent branding
Keeping these elements accessible requires clear hierarchy as the catalog grows. Dividing workspaces by component type lets team members locate shared resources without digging through unrelated garment projects.
Running Development as System Data
CLO-SET’s Company Library and Content Page support different parts of this workflow: the library organizes shared assets, while Content records hold uploaded files, versions, linked-content relationships, and review information. For supported Style Contents, Web Tech Pack provides production information such as BOM, POM, construction, and cost estimation alongside 3D files.
A style does not have to begin as a complete 3D file. Since June 2026, teams can assign non-CLO files such as images and PDFs a Content Type during upload; selecting Style makes BOM and POM options available for those Contents. As specifications and 3D assets come together, contributors can review them in the Viewer and discuss them through Content-level Comments.
Controlling Versions, Derivations, and Reviews
Apparel development can involve both revisions to an existing style and new styles derived from a block or earlier design. CLO-SET distinguishes these through two different actions: a version upload adds a newer file to the same Content, while Linked Contents connects separate Parent and Child Contents.
For supported Style Content based on a .zprj or .zpac file, a Web Tech Pack is created per Content version. When a new version is uploaded, teams can choose whether to update the Web Tech Pack. To link a derivative Content to its source, teams must upload it as a new Content from CLO 3D with Linked Content enabled; this option is not available for version uploads.
In the 3D or 2D Viewer, reviewers can set a viewpoint and add Annotations to highlight specific locations. Comments are managed at the Content level; reviewers can view comments across versions or filter them to the current version. CLO-SET also supports AI translation for comments and provides Workflow and Status fields for organizing and tracking Content.
Platform Comparison: Asset, Version, and Review Capabilities
CLO-SET, Style3D Cloud, and Browzwear Stylezone address asset libraries, version tracking, and design review with distinct capabilities.
| Capability Area | CLO-SET | Style3D Cloud | Browzwear Stylezone |
|---|---|---|---|
| Centralized Asset Categories | Fabrics, trims, block patterns, avatars or dummies, and brand logos in Centralized Asset and Company Libraries | 3D garments, styles, fabrics, trims, and styling elements in centralized digital asset management libraries | Garment assets stored, organized, and reused in a virtual design library |
| Library Organization & Formats | Company Library with Workrooms and Child-Workrooms organized by component type; Component Library | Shared 3D libraries compatible with OBJ, FBX, glTF, u3ma, GLB, SBSAR, and DXF formats | Virtual design library for storing and organizing garment assets |
| File Registration & Upload Scope | Registers 3D garments and (since 2026-06) non-CLO files including 2D sketches, images, and documents | Centralizes company-wide 3D files | Uploads styles from VStitcher or Lotta to Stylezone |
| Versioning & Content Lineage | Version uploads add files to the same Content; Linked Contents connects separate Parent and Child Contents; supported Style Contents based on .zprj/.zpac files can have a Web Tech Pack per version | Shared 3D libraries act as a single source of truth for the latest version | Tracks design updates and iterations in a complete version history; Basic Versioning lets users upload a new version or edit an existing version from VStitcher or Lotta |
| Review & Collaboration Surfaces | 3D/2D Viewer with viewpoint-based Annotations, AI-translated comments, version-filtered comment views, Workflow & Status, and Content Page tabs (Overview, Viewer, BOM, POM, Cost Estimation) | 3D model annotations, collaborator mentions, and comments | Comments and updates to align teams on feedback and changes |
FAQ
How does CLO-SET handle tech packs when a new garment version is uploaded?
For supported Style Content based on a .zprj or .zpac file, a Web Tech Pack is created per Content version. After uploading a new version, teams can choose whether to update the Web Tech Pack.
How does CLO-SET relate to PLM during product development?
Development work—including design changes, 3D, BOM and tech-pack work, and sample rounds—happens in CLO-SET, while PLM holds the confirmed results.
Source Note: Reviewed November 25, 2026. Method: checked the official CLO-SET Help Center documentation for Company Library and component setup, non-CLO file uploads, Linked Contents, Web Tech Pack, design review, and Comments. References: Company Library, Component Library, Non-CLO file support (June 2026), Linked Contents, Web Tech Pack, Review Design, and Comment.