Product Records are the core component of Product Hub, a master level entry for tracking all downstream data in Creative Force– from the productions completed to the assets shot, styling and outfit data it has been involved in, and so much more. In this article, we will take a look at what a record is, how it relates to the work you do in Creative Force, and where to find more information for details and deep dives.

A Product Record is the single, permanent entry for one item in your catalog, like the "T-shirt design" in the visual below. It holds the core details (product code, name, category, style code, color, brand) plus any custom properties. A Product Record lasts across many shoots, so it shows every production done for that product.

The Product Hub is the central location for interacting with your Product Records. From the Hub in Gamma, you can review, manage, and take action on your records– including creating Product Requests directly.

Product Records can be created in a few different ways tailored to the amount of data you have on the products and where that data lives.

You can manually create a new Product by going to Product Hub → Create Product → New Product. Designate standard system properties like Product Code and Product Name, as well as any custom properties your studio has previously configured.

Once the record has been created, you can add a Display Image, create Variants and Samples– then export directly to a Job as a Product Request.

You can manually create a set of new Product Records by going to Product Hub → Create Product → From File.

Using an existing list of Product Codes on a spreadsheet, you can bulk create blank products and then edit more details into them separately at a later time.

• One Product Record is created for each code. The product name is set to the same value as the code. No other properties or variants are filled in, so you add those later or through a file import.
• Creation runs in the background. Follow progress in the Message Center.
• Blank lines are ignored. If the same code appears twice in your sheet, it's only created once.
• Codes that already exist in the workspace are not overwritten. They're skipped and show up as failures in the import results

External data that exists outside of Creative Force in a compatible PIM can also be used to sync Product Records directly to Product Hub. After having created a Data Source connection in Studio Settings, head to Workspaces → 'Edit' → Data Source

After enabling the toggle for 'Product Hub Synchronization Criteria', you will have the option to set a sync rule. To learn more about logical operators, see the article here.

Once set, all matching data in your source will be imported directly to Product Hub as Product Records when synced.

Since Product Records and Product Requests are closely tied together, they share product-level properties. However, the exact nature of how the values of these properties behave in relation to each other is controlled by its Sync Mode setting.

When creating a new property, you are able to select between three sync options. Each option carries different logic for how values should be treated when writing to Product Requests and Product Records.