Outfits in Creative Force enable "Shop The Look" functionality by allowing you to create styling sets that group multiple products together as they appear on set. With integrations to our Planning module, Gamma, Kelvin, and Chroma, you can track your Outfits from initial Session Planning all the way through embedding outfit properties as metadata during Asset Delivery.

Introduction

An Outfit consists of one Primary Component and one or more Secondary Components. Once the items have been associated together as an Outfit, Creative Force creates an Outfit Code that can be tracked throughout production.

Outfits can be tracked and interacted with in multiple places throughout Creative Force, such as Gamma, Kelvin, Chroma, and Dreem. Outfits dont require any setup before starting, and are available for all studios.

Characteristics

When an Outfit has been created, it will have a number of characteristics that will be related to it and can be managed independently.

Option	Function
Outfit Code	Outfit Codes can be manually entered or automatically created by the system if no manual entry is given. This code will allow the outfit to be tracked and filtered throughout the system. Learn more.
Outfit Name	This is an optional attribute that can help users recongize and call out different created outfits when multiple exist. Learn more.
Properties	Properties can exist at the Outfit level and are useful when needing to track metadata related to styling, or communicate information to Stylists or other on-set users. Learn more.
Readiness	The readiness status at the Outfit level is determined by the Readiness status of its individual components. Learn more.

Components

Components are the items that make up an Outfit. Components also have their own individual characteristics separate from Outfit Characteristics, like Strictness, Readiness, Size, Quantity & more.

Characteristic	Description
Components	Separated into Primary and Secondary components for an outfit. The Primary being the main 'Hero' item to be shot, and the Secondary being supporting styling items. Learn more.

Styling Tab

You can access Outfits via the Overview slide-in on the Production page, Product Requests page, or Sample page. After selecting the intended item, navigate to 'Styling' on the overview slide-in tabs.

On the Styling Tab, you will see any already related Outfits listed, have an option to interact with them, and/or an action button to create a new outfit altogether.

Viewing Outfits

When reviewing the Styling Tab, you will see a Primary/Secondary toggle; here, you can switch between Outfit lists where the item is a Secondary or Primary Component of the Outfit. If the item is not currently a component in any Outfits, they will be blank.

From the Outfit List, you can review individual components and select them to open a new tab overview of the specific linked component.

Outfit Actions

At the Outfit level, you can use the 3-dot menu () next to it to access additional options for the selected Outfit. When selected, a pop-up menu will appear.

Edit Outfit Properties

Change Outfit-level properties. There are standard system properties like Outfit Code, optional ones like Outfit Name, and completely custom ones you can create yourself via Studio Settings → Properties.

Outfit Display Image

Upload an optional display image that can be related to the outfit, visible in various apps throughout Creative Force. Outfit Display Images can also be seen when printing Outfit Sheets.

Print Outfit Sheet

Outfit Sheets are printable sheets that can display all of your related outfit data in a convenient, shareable layout.

Outfit Sheets can be triggered to print in various places in Creative Force. Bulk printing of outfit sheets is available in the Production, Product Requests, and Samples views. From any of these views, select the items you need and use 'Actions' → Print Outfit Sheets to generate sheets for the full selection in a single step.

See Full List & Description

Planning → Session Card: The action menu on a Session Card includes "Print Outfit Sheets." This gathers all outfits from the session's production items and sends them to print.

Planning → Production Tab → Bulk Select + Action: Inside a Session's Production tab, you can select multiple production items and use the "Print Outfit Sheets" bulk action to print outfit sheets for just the selected items.
Create/Edit Outfit Menu: Inside the modal where you create or edit an outfit, the action button menu includes "Print Outfit Sheets" for the outfit you're currently working on.
Product Request Slide-In → Styling Tab:When viewing a Product Request's outfits in the sidebar, you can select "Print Outfit Sheets" from the outfit's action menu. This prints a single outfit.
Job Details Page: In the action menu at the top of a Job's detail view, there's a "Print Outfit Sheets" option. This prints all outfits associated with that Job.

Duplicate/Delete

Select Duplicate Outfit to copy over the same characteristics (properties, display image, name) and components (products, samples, etc) from the existing outfit and apply it to a new Production Type.

Select Delete Outfit to remove it from the system entirely. This is a destructive action and may affect reporting, filtering, and other features in the system where the Code contains related data.

Outfit Builder

When selecting 'Create Outfit' from the top right of the Styling Tab, or selecting 'Edit' from the actions menu, you will be brought to the Outfit Builder.

The builder contains many actions and information windows discussed elsewhere, but condensed into a compact working view.

UI Map

Pin	Name	Description
	Actions	3-dot menu that allows selecting outfit-level actions.
	Properties	A list of outfit-level properties. Toggle between hiding and displaying properties. Use the pencil icon to edit values.
	Display Image	Product Request-level Display Image for the component is shown here.
	Primary List	Shows the related Product Code and Product Name for the component. The flag icon indicates it is the Primary component for the Outfit.
	Size & Strictness	For each component, the variant size and strictness level are displayed. To change the values, select the Size button to open a new menu.
	Barcode Field	Use your barcode scanner to scan a code from a label, or manually type a code to add it to the secondary components.
	Product Browser	Select to open a new window where you can browse your product catalog with additional filtering & selection options.
	Secondary List	The same listed attributes for your secondary components as explained for the primary in Pins

In addition, the Outfit Builder is where you can review and edit the components in an Outfit. You can manually scan or enter the barcode for a component or use the product browser to strategically browse and select a component.

Product Browser

The Product Browser is an optional level to the Product Builder where you are able to search for and filter items in your product catalogue. The top section has search, filtering, and display settings– to narrow down results as you see fit.

In the main window, you can scroll through the catalogue and select items by component– each size is represented as a variant per code. Use the select boxes to add multiple selections to the Outfit at once as 'Any Size', or add individual components by a specific Size by selecting a Size value.

All of your selected items will appear in the right-hand column. When you are satisfied with your build, just hit 'Close' to exit the browser and return to the builder.

Components

A component is an individual item within an Outfit. Of those components, there is a Primary Component– or the hero item– and its supporting Secondary Components.

Characteristics

Each component can carry its own size, quantity, match, and strictness settings. Together, these characteristics determine how the outfit components should behave as requirements when checking in samples to prepare for shooting.

Value		Description
Size		The allowed sizes of a variant that are acceptable to shoot.
Match		When multiple Size values are selected, the 'MATCH' option will become available. There are two options.
→ Match Any		Checking in any single listed size satisfies the requirement for readying the outfit.
→ Match All		Checking in all of the listed sizes satisfies the requirement for readying the outfit.
Quantity		Determine how many physical samples of the selected size the outfit needs to satisfy the requirement.
Strictness		The strictness of a component can be set between Mandatory and Substitutable, depending on the importance of the specific component to the Outfit as a whole.
→ Mandatory		(default*): the component is a required part of the Outfit, and the outfit cannot be shot without it.
→ Substitute		: the production can proceed without this item. When set, the component never blocks Outfit Readiness.

Component List

The overview table in the styling tab list will display information about the status of the production, outfit, and individual components. To understand more about the information being presented, review the UI map and table below.

Pin	Name	Description
	Production Type	The specific Production Type the Outfit is related to.
	Production Status	The status of that Production in the Workflow.
	Outfit Status	The overall Outfit Readiness status.
	Component Status	The individual Component Readiness status.
	Primary Flag	Indicator that the component is the Primary.
	Strictness Type	Whether the component is Mandatory/Substitutable.
	Quantity Chip	For components with quantities greater than one.
	Size Chips	Each size allowed or required for the component.
	Requirement Fulfilled Y/N	The border color of a chip indicates whether the requirement has been met or not. Requirement Met Requirement Not Met

Practical Example

We, as the stylist, are building an Outfit centered around a distressed plain-white T-shirt. The brand makes some components (tops, bottoms), but doesnt make others (shoes). They have specific preferences for how some items fit and drape on the model, but it's not always a requirement and is sometimes left up to the stylist.

In the table below, we will go over the selections made and the reasoning for each.

Overview	Requirements	Story
	Component: 2nd Size: M Quantity: 2 Match: – Substitutable: Y Prefer two Mediums, but it's flexible– a stand-in or nothing at all is also fine.	I know the model wears a medium, but the hats have unique hand-painted details, so I want options in case I prefer one or the other. The hat is accessory-level styling, not the product being sold– so if I dont like either, not having a hat at all is perfectly fine as well.
	Component: 1st Size: S Quantity: 1 only Match: – Substitutable: N Needs exactly 1 Small, no substitutes– a mandatory hero piece.	This is the hero piece– the actual product being shot. It has to be the exact sample the client approved, in the specified Small, because that's what the customer sees and buys. There's no creative wiggle room on the star of the shot, so nothing else can stand in. If it's not here, we don't shoot.
	Component: 2nd Size: S + M Quantity: 1 each Match: Any Substitutable: N Needs 1 Small or 1 Medium– either size satisfies it. Because any listed size works, a missing choice becomes a Fallback.	Although it's a secondary item, it is from the same brand as the shirt, and the client asked that they be shot together. I'm not sure how tight these actually run, and the client didn't state a preference. I can pull both, or eyeball at the shelf. But ultimately, either one is fine.
	Component: 2nd Size: S + M Quantity: 1 each Match: All Substitutable: N Needs both 1 Small and 1 Medium– all listed sizes are required, with no substitutes.	The client hasn't locked the fit. They want both the Small and Medium shot so they can see each on the model and approve one or the other. Both have to physically be here for that– it's not 'either/or from the shelf'; it's 'both present for a live decision.'
	Component: 2nd Size: Any Quantity: 1 only Match: – Substitutable: Y Needs 1 pair in any size, and even a stand-in is fine. If no shoes work, we can just shoot from the ankle up.	Footwear is just set dressing here, and the brand doesnt make its own shoes. It rounds out the styling but barely shows. Any size that fits works, and if the intended pair is missing, grab a comparable one– I'm not holding up the shoot over shoes.

Readiness

Readiness is measured both at the individual component and outfit level. When all components meet the requirements, the Outfit becomes ready to shoot.

Component Readiness

An easy way to think of component readiness is that each component is a Yes, No, or Maybe– depending on how the checked-in sample compares to the requirements set.

State	Signal	Y/N/M	Condition
Ready		Yes	The component's required sample is physically checked in in the correct spec (right size and quantity).
Ready		Auto-Yes	The component's sample is physically checked in. No actual requirements need to be met since the item is substitutable.
Fallback		Maybe	The ideal size isn't available, but an alternative is checked in.
Not Ready		No	The component has a hard blocker. A mandatory piece's required sample is missing with no acceptable substitute, so the outfit cannot be shot as defined.

Outfit Readiness

Depending on the Yeses, Nos, & Maybes of your individual components, your Outfit Status then takes on its own Outfit level readiness.

State	Signal	Y/N/M	Explanation
Ready		→ All Yes → No Maybe → 0 No's	Every mandatory component is checked in, satisfying its size requirement and its required quantity.
Fallback		→ Has Yes → Has Maybe → 0 No's	Every mandatory component is present, but the size requirement is only partially met. The shoot can proceed, but it is up to the stylist/producers' judgement.
Not Ready		→ Has No's	One or more mandatory components are entirely missing, or checked in with insufficient quantity. The outfit cannot be shot.

Readiness Examples

With what we have learned about component & outfit-level requirements, as well as readiness states, let's now review some live examples of Outfits in various states.

Component	Readiness Contribution
Component 1	The component does not have a size 'small' that is currently checked in. The component-level readiness is No, and therefore the outfit-level readiness is Not Ready.
Component 2	The component does not have two medium samples currently checked in, but has two smalls checked in instead. Because it is Substitutable, it is an auto-Yes.
Component 3	The component has a small and medium sample checked in. All requirements are met; it is a Yes.
Component 4	The component has a small and medium sample checked in. All requirements are met; it is a Yes.
Component 5	The component does not have any sample currently checked in, but because it is Substitutable, it is an auto-Yes.

Component	Readiness Contribution
Component 1	The component has the required small sample checked in. All requirements are met; it is a Yes.
Component 2	The component has two medium samples currently checked in, and because it is Substitutable, it is an auto-Yes.
Component 3	The component has a small but not a medium sample checked in. The requirements are partially met. This is a Maybe.
Component 4	The component has the required small and medium samples checked in. All requirements are met; it is a Yes.
Component 5	The component has a sample checked in of at least one size, and because it is Substitutable, it is an auto-Yes.

Component	Readiness Contribution
Component 1	The component has the required small sample checked in. All requirements are met; it is a Yes.
Component 2	The component has two medium samples currently checked in, and because it is Substitutable, it is an auto-Yes.
Component 3	The component has the required small and medium samples checked in. All requirements are met; it is a Yes.
Component 4	The component has the required small and medium samples checked in. All requirements are met; it is a Yes.
Component 5	The component has a sample checked in of at least one size, and because it is Substitutable, it is an auto-Yes.

Component	Readiness Contribution
Component 1	The component has the required small sample checked in. All requirements are met; it is a Yes.
Component 2	The component does not have two medium samples currently checked in, but has two smalls checked in instead. Because it is Substitutable, it is an auto-Yes.
Component 3	The component has the required small and medium samples checked in. All requirements are met; it is a Yes.
Component 4	The component has the required small and medium samples checked in. All requirements are met; it is a Yes.
Component 5	The component does not have any sample currently checked in, but because it is Substitutable, it is an auto-Yes.

Outfits Overview

Introduction

Characteristics

Components

Styling Tab

Viewing Outfits

Outfit Actions

Edit Outfit Properties

Outfit Display Image

Print Outfit Sheet

Duplicate/Delete

Outfit Builder

UI Map

Product Browser

Components

Characteristics

Component List

Practical Example

Readiness

Component Readiness

Outfit Readiness

Readiness Examples