Key Takeaway
- With CLO-SET, reviewers with an account and access to the Content can review supported 3D garment files in a browser and pin notes to specific locations in the 3D Viewer.
- Each Content version in CLO-SET has its own Web Tech Pack, and teams choose whether to update technical data when uploading a new version.
- Supported
.zprjand.zpacfiles populate Bill of Materials and Point of Measure sections in the Web Tech Pack.
During a sample review, a technical designer and a patternmaker examine how a sleeve hangs on a digital garment. Notes taken in chat threads or separate spreadsheets sit apart from the seam or measurement being discussed. When evaluating software for fit reviews and tech pack updates, consider where reviewers leave feedback, how they view it across file versions, and how garment data enters the production record. In CLO-SET, reviewers can add comments and viewpoint-based annotations in the 3D or 2D Viewer, while supported Style Content files can populate Web Tech Pack data. Comments are review feedback; the documentation does not describe converting comments automatically into specifications. Teams choose whether to update Web Tech Pack data when uploading a new version.
Pinning 3D Fit Comments in a Browser
When merchandisers or external partners do not have 3D authoring software installed, CLO-SET’s browser-based review can provide a way to inspect supported 3D garment files and leave feedback. Reviewers need a CLO-SET account and access to the Content; they can examine the garment and point to an area without first exporting a static screenshot.
With supported 3D garment files, team members can review the garment in CLO-SET’s browser-based 3D Viewer without installing separate 3D authoring software. Reviewers can pin comments to specific locations in the Viewer. Viewpoint-based annotations can highlight a position or detail in the 3D Viewer or 2D Pattern Viewer.
As a style goes through multiple rounds of fit adjustments, reviewers can view comments across Content Versions by default or turn off View All Versions to see comments for the current version. This helps teams distinguish feedback by iteration. If non-3D users need to review a garment in the browser and leave spatial feedback, confirm that the file format is supported and that reviewers have a CLO-SET account and Content access.
Managing Versioned Tech Pack Updates
Uploading a revised 3D sample raises an operational question for technical designers: should the new file automatically overwrite the existing specification sheet, or should the update wait until the changes are verified? Automatic overwrites alter a tech pack that may still be referenced for costing or vendor communication, while manual re-entry requires separate steps.
CLO-SET manages comments at the Content level, allowing teams to view them across Content Versions or filter them to the current version. For supported .zprj and .zpac Style Content, Web Tech Pack data is versioned; selecting an update when uploading a new version creates an updated Web Tech Pack version. On the current Content Page, BOM, POM, and Cost Estimation are available directly in their respective tabs; the separate Construction tab is documented for the legacy Content Page.
When a designer uploads a new Content Version, the team can choose whether to update the Web Tech Pack. Selecting Update creates a new version and updates relevant technical information—including BOM, Construction, Measurement, and Cost Estimation—based on the uploaded file and existing Web Tech Pack data. The update is user-selected, not automatic. Teams can decide at upload whether to create an updated tech pack version. This update applies to Web Tech Pack data, not to comments being converted into specifications.
Populating Specs From 3D Files
Moving from a fit review into production readiness requires translating visual garment changes into structured tables for materials, measurements, and costs. If your patternmakers already build fabric, trim, and measurement details into their 3D files, typing those same values into a separate tech pack document duplicates the work.
For supported .zprj and .zpac Style Content, CLO-SET can populate BOM and POM data from the file. The legacy Web Tech Pack has five sections; on the current Content Page, BOM, POM, and Cost Estimation are available as tabs, while Construction remains documented for the legacy page:
- Overview summarizes Content information and schedule details in the Web Tech Pack.
- BOM data is auto-filled from supported
.zprjand.zpacfiles; teams can edit BOM details and add material information. - Construction is available in the legacy Web Tech Pack, where teams can review design construction and add annotations.
- Measurement, or Point of Measure (POM), data is auto-filled from supported files; teams can manage details such as tolerance and target values. POM can also be added manually when a file has no measurement data.
- Cost Estimation uses fabric and trim costs from the BOM and allows teams to enter additional costs such as labor and transportation.
Because filling BOM and POM data from supported CLO files depends on .zprj and .zpac formats, teams using other file formats will need to account for that condition when evaluating how much manual data entry this workflow saves.
Review and Tech Pack Workflow Matrix
When comparing how platforms connect sample feedback to the next product record, look at the surface where reviewers leave comments, how feedback links to product versions, and how the tech pack record is generated and tracked. CLO-SET, Centric PLM from Centric Software, and Apparel PLM from ApparelMagic handle these steps differently across their review and tech pack workflows.
| Platform | Review Input Surface | Feedback and Version Linkage | Tech Pack and Next-Round Record |
|---|---|---|---|
| CLO-SET | Browser-based 3D Viewer for supported garment files; comments can be pinned to locations, and viewpoint-based annotations can highlight details in the 3D or 2D Pattern Viewer | Comments are managed at the Content level; viewable across Content Versions by default or filtered to the current version by turning off View All Versions | Web Tech Pack data for supported .zprj/.zpac Style Content can be updated by user choice on version upload; current Content Page tabs include BOM, POM, and Cost Estimation, while Construction is documented for the legacy page |
| Centric PLM | Centric’s 3D Sample Review mobile app supports reviewing digital samples in virtual fit scenarios and adding comments | Digital assets can be attached to style data and incorporated into active line plans | The product page describes reviewing digital samples, adding comments, and receiving amended samples in Centric PLM |
| Apparel PLM | Annotates photos and flats with measurements and notes | Tracks sample iterations and fit-session feedback, including long-form comments and imagery, bundled with tech packs | Generates tech packs with images, specs, and BOMs, and tracks tech-pack version history in PDFs |
FAQ
How does a team turn 3D garment decisions into production specifications after fit comments?
In CLO-SET, supported .zprj and .zpac Style Content can populate BOM and POM data from the file. Teams can enter target measurements and additional costs such as labor and transportation. The legacy Web Tech Pack includes Overview, BOM, Construction, Measurement, and Cost Estimation; on the current Content Page, BOM, POM, and Cost Estimation are available in their own tabs. Comments and annotations provide review feedback; they are not automatically converted into specifications.
How do fit comments on a digital sample carry over into tech pack revisions for the next sample round?
CLO-SET manages comments at the Content level, allowing teams to view feedback across Content Versions or filter to the current version. For supported .zprj and .zpac Style Content, a designer can choose to update the Web Tech Pack when uploading a new Content Version. This updates versioned tech pack data, including the BOM; it does not convert comments into specifications.