September 8th - Sprint 210 Release Notes

Happy Sprint Release Day! 🚀

Sprint 210 focuses on outfit building and Editorial: Outfits now capture the sizes, quantities and priorities behind readiness, and Editorial gains bulk workflow editing plus better full-screen review across the whole set. Also now, you can ask AI about your copywriting content.

We're always eager to hear your thoughts, so don't hesitate to share your feedback.

Outfits can now capture exactly what a shoot requires. When adding a component, you can specify the required size, the quantity needed for that size, and whether the component is mandatory or substitutable. Where more than one size works, you can indicate whether any one of them is enough or all are needed.

This gives outfits a precise definition rather than a simple product list, so teams have a reliable basis for judging whether a look is ready to shoot. Every component starts as mandatory and sizes are optional, keeping the builder quick to use.

These options are available in Gamma today, with Chroma and Kelvin support following shortly. Existing outfits are migrated automatically, with every secondary product set to accept any size, so nothing changes until you choose to add a requirement.

Learn More: Outfits Overview

Outfit readiness is now easier to understand at a glance. Status indicator shows whether an outfit is ready, ready with a fallback, or not ready, using green, yellow, and gray states. Readiness of the outfit is dependent on the check-in status of required samples and it provides component-level detail so teams can distinguish a wrong-size fallback from a missing mandatory item.

We're expanding this further, with an Outfit Readiness filter among the options coming soon.

Learn More: Outfits Readiness

Pre-production outfit planning is faster with a product browser inside the builder. You don’t have to rely on scanning or pasting barcodes, instead in a browser you can search, filter, review display images, select the right variants, and add products without leaving the outfit context.

Learn More: Product Browser

Editorial workflow changes no longer have to be repeated deliverable by deliverable. Bulk editing supports template reassignment for not-started deliverables and clear warnings when In Progress or Done.

Learn More: Bulk Deliverable Workflow Edits

Chroma now supports the Editorial-only samples. Samples without an Ecom association can be found and managed through the standard scan experience, including location moves, property updates and scanning flows.

Learn More: Chroma: Scan Tab, Chroma: Flow Tab

Full-screen review in Editorial now continues beyond the images that were initially loaded. When a reviewer reaches the end of the current batch, the next batch loads automatically instead of navigation looping back to the first image.

Integrations can now subscribe to a dedicated SampleCreated webhook event. The event appears in the Sample group alongside existing events and sends required context when a sample record is created, enabling sample-level automation without subscribing to the ProductImported event.

Learn More: Webhooks

Copywriting is now available through MCP, so AI assistants can read and review Text assets across supported languages. Editorial can also discover project documents and Creative Brief metadata, including document types, current versions, deliverable assignments, and whether written direction is present.

Learn More: MCP Server: Data Queries

We’re always striving to create the best product for you and your team! Feel free to drop us a line via email/chat, or submit your ideas and feedback directly to our product team via product@creativeforce.io.