Define the recipe
Direct the scene, views, motion, formats, and delivery requirements.
Turn prepared product models into catalog images and video. Reuse saved creative work to reduce setup for the next part or material option.
Catalog content automation applies saved templates and output requirements to each prepared 3D model, then tracks production, review, exceptions, and delivery.
Reuse cameras, lighting, scenes, motion, and output settings while keeping product-specific changes editable.
Direct the scene, views, motion, formats, and delivery requirements.
Start a run manually, through the API, or from a supported connected source.
Track status, route exceptions, finish outputs, and return results to the destination.
Prepare the product, direct the scene live, and adapt suitable saved setups for the next request.
The next part needs more images. So does the new material, the revised assembly or the sales team answering a customer request.
Glossi gives your team a browser workspace to create those visuals from your product models. Change the lighting or camera and see the result as you work. Keep useful materials and saved views available for the next job.
Choose the exact assembly or configuration for the first request. Provide its CAD or existing 3D model, plus material references and any labels or artwork.
Your product owner confirms which design is current. The person preparing the model checks the parts and material regions before production. Some files need conversion, geometry cleanup or new materials. Agree who handles that work before setting the delivery date.
Set the product's materials, then adjust the scene in your browser. Save the camera views your catalog needs. Check a useful detail, such as a welded joint or a reflective surface, before applying that treatment more widely.
The operator can be a designer, a 3D artist or a content producer with the right prepared assets and training. Glossi's built-in Assistant can help with supported scene changes. The operator inspects the result and refines it.
Give the product reviewer the views needed to check shape and detail. Review materials and artwork against the supplied references. A material that looks right from the front can behave differently at another angle.
Then check the delivery itself. Does each file show the right product and material? Does the framing work? Are its dimensions and filename right for the destination?
AI finishing needs another product check because it can change labels or details. A convincing image still needs to represent what you sell.
MagnaFlow built its catalog workflow around prepared engineering models and saved materials, lighting and camera views. Its team tested images and a 360 view on a product page, then checked the output requirements against its own files.
The next product can start from suitable saved work. Different proportions may require new framing; changed geometry or materials need review. Test a second part before assuming the first setup covers the range.
Keep the models and finished visuals organized in the shared library so the team can find them again. A new catalog view or customer request can build from existing product work.
See progress, errors, retries, approvals, and output links without managing production through folders and status messages.

Finished MagnaFlow images from engineering CAD: an exhaust assembly and two views from a converter’s 24-frame rotation.
MagnaFlow · Exhaust assembly
MagnaFlow · View 7 of 24
MagnaFlow · View 1 of 24High-volume, repeatable content requirements with prepared products, saved templates, and known destinations.
Product readiness, creative exceptions, compliance-sensitive work, and final approval should keep explicit human ownership.
Learn more about catalog production with Glossi.
It is the use of reusable product content recipes and tracked workflows to produce required assets across many prepared products with fewer repeated manual steps.
Glossi supports batch and pipeline workflows, but capacity, model readiness, branch logic, and connector behavior should be tested against the actual catalog.
Yes. Runs expose stage status and errors so teams can route products that need correction instead of hiding them inside a zero-touch claim.
Tell us what you make repeatedly and who will make it. Bring an example model or product link, the views you need and the next request you expect. We can check whether the standard product fits and identify any separate preparation work.