From Approved Virtual Sample to a Polished Garment Still for E-Commerce Launch Teams

Record the approved garment revision before the first export.

• Keep technical fit approval and image approval as separate decisions.
• Choose the requested product views and recipient specifications before rendering.
• Use CLO for a fixed garment still when its in-app image meets the brief.
• Move to another renderer when the deliverable calls for a distinct scene, compositing or motion.

1. Separate garment approval from image approval

A virtual sample approval records a decision about the garment; a still-image approval records a decision about how the garment appears in a specific asset. Carry the approved garment version into image production, then review the image as its own deliverable for framing, colorway, details and intended use.

Fit review examines garment ease, balance, set, grain and line, according to a 2024 study in Fashion and Textiles. The study also describes fit models as a source of tactile and comfort feedback, including comments on how a garment feels while worn and during movement. This gives the technical gate a clear record: the sample version, size and avatar reviewed, the fit observations, and any resulting pattern decision.

A study of men’s T-shirt development in a virtual environment reports realistic drape and fit assessment through iterative virtual simulation. The study also explains that strain maps flag tight or loose areas and can guide fit adjustments before production. For launch work, keep the fabric setup and fit comments attached to the approved garment record so the still team starts from the same reviewed state.

Image approval asks a different question: does this particular view show the approved garment clearly for its audience? Approve the crop, camera angle, background, lighting, garment details and any size or colorway label against the release brief. A useful approval trail has two decisions: “garment fit and design approved” and “these images approved for this channel.”

2. Define the still set and recipient requirements

Choose the image set before opening the render controls. The storefront, buyer portal or line-sheet template determines the required ratio, pixel dimensions, background, file type, naming and views; those details belong in the render brief, rather than in a general-purpose standard.

For an e-commerce product page, a practical starting set is a front view, a back or three-quarter view where it answers a shopper question, close-ups of important construction details, and separate images for colorways that must be shown individually. For a wholesale line sheet, the buyer may need a clean front view, a back view and a colorway sequence. Treat those as proposed views, then match the final set to the retailer’s actual content requirements.

Mobile cropping should shape the camera framing. Shopify’s 2026 website-image guidance says image width depends on the display area, gives 1,200 pixels as general guidance for main content and notes that square or vertical product images fit mobile screens well.

Platform behavior can also crop an otherwise well-composed render. For SHOPLINE OS Theme 2.1, its image guide recommends a 2:3 product-image ratio, a minimum of 560 by 840 pixels for its stated mobile display, and 1,700 by 2,550 pixels as a recommended detail-page image size. The same guide says fixed-height and fixed-ratio components can crop images, with centered cropping used when the image display area is unset.

Put the receiving requirements into a short render brief:

• The destination and its required pixel dimensions, aspect ratio and accepted file format.
• The required front, back, angled, detail and colorway views.
• The intended background and any required empty space for labels or layout.
• The approved garment version, size and colorway names.
• The reviewer who signs off the rendered images.

3. Decide whether to render in the garment application

CLO supports garment fit-and-drape simulation and includes an internal renderer for garment images. CLO’s features page lists the control as “Render | Grading Sizes.”

Browzwear’s Rendering Overview describes creating a render from a finished VStitcher or Lotta simulation and lists line sheets, presentations, fitting sessions, merchandising and e-commerce as uses. It distinguishes the render type, or how the image is built, from the output format, or how people receive it. Teams already using that workflow can keep the still in the garment application when the output fits their approved pipeline.

For one clean front image, a separate application may add steps without changing the deliverable. For a campaign image that needs a designed environment or compositing, plan the separate-render handoff before release.

4. Check the approved asset before rendering

Confirm that the source file matches the approved version, the intended size and colorway, and the fabric or material setup used during review.

CLO’s Grading Review instructions describe simulating each selected size and saving that size’s result for review. They also specify re-simulating a size when a pattern mesh changes after its saved simulation. Use the same principle in a release workflow: when a pattern correction changes the garment after approval, refresh the relevant simulation and review the image source before rendering the revised still.

Use this checklist before generating final images:

• Version: Open the approved garment file and record its revision identifier.
• Simulation: Confirm the current pattern and simulation state match the latest approved review.
• Material: Confirm the fabric and colorway assigned to the render are those in the release brief.
• View: Set the pose, camera, lighting and crop to show the design features required for this image.
• Output: Set dimensions, aspect ratio and background for the destination rather than relying on an attractive viewport crop.
• Review owner: Route a draft to the person responsible for visual release approval.

Color calls deserve a named owner and a known reference. X-Rite’s apparel color-control guidance presents digital color management as a way to make color assessment more precise and reliable through production. In practice, route a color-sensitive still to the team member who owns the approved color reference, and record that reference with the image review.

5. Handle multi-size images as a separate image decision

A size run changes both the render workload and what each image communicates. Decide whether the recipient needs one representative size, a coordinated image for every approved size, or a comparison view that displays several sizes together.

CLO 2026.1 documents selecting specific grading sizes and rendering them together on its features page. That is a useful fit when the launch pack needs a set across several graded sizes. CLO’s Grading Review provides a Panoramic layout to check and compare all grading sizes in one 3D window.

Name each exported image with the style, size, colorway and view, for example Jacket-01_Medium_Navy_Front. Keep the fit-review status in a separate field or approval record. A row of size renders shows the available image views; the separate review record carries the fit decision for each size.

6. Use a separate renderer when the brief needs more than a still

A garment still is a fixed image of the simulated product. A turntable, animated view, composed campaign scene or multi-layer visual treatment asks for a different output, so compare the deliverable with what the garment application can export before sending files elsewhere.

Browzwear’s rendering documentation describes a turntable as a set of images from different angles combined into an interactive pseudo-3D output; the documented formats are HTML or animated GIF. It also describes high-quality ray tracing as a resource-intensive task whose completion time depends on system memory and image detail. These examples show why teams should choose the renderer from the output requirement: still image, interactive angle view, or a more resource-intensive visual treatment.

For any separate-render handoff, test one approved style first. Browzwear’s practical file guide describes its digital material archive as carrying properties such as weight, stretch and drape calibrated against fabric swatches. The guide asks teams to check whether a garment file is matched to calibrated fabric data; it describes rendered-mesh exports for merchandising or sales as visual references that contain no construction data. Use the source format that carries what the receiving team needs, and keep an image-only export in its visual-reference lane.

A test handoff should answer four questions before the team transfers a full collection:

1. Does the target application open the chosen garment and material files?
2. Does the fabric appearance and garment shape match the approved source closely enough for the stated visual task?
3. Can the target deliver the required view, background, ratio, dimensions and file type?
4. Does the exported image keep the approved size, colorway and revision identity?

If the test still can be completed in the original application and meets the brief, keep the render there. If the brief depends on a separate scene, compositing or motion output, document the tested file path and assign an owner for maintaining the handoff.

7. Release the still-image pack

Package the approved files as a traceable set rather than as anonymous image exports. Include the destination, style, garment revision, size, colorway, view name, dimensions and visual-approval status in the file names or accompanying manifest.

Use this release sequence:

1. Match each image to the requested view list and recipient specifications.
2. Review the files at their delivery dimensions and in the destination layout, including mobile crops where the channel uses responsive images.
3. Confirm each size and colorway label against the approved garment record.
4. Attach the image approval and identify the garment version from which the stills were produced.
5. Deliver the image files and any source handoff the recipient’s workflow requires.

For a fixed still, choose CLO when its in-app garment image meets the brief; keep an established Browzwear workflow when its finished simulation supplies the required still, and choose a separate renderer for a distinct scene, composite or motion treatment.