What is Product Hub?
Product Hub is a fundamental change in Creative Force that introduces a true product record: a persistent, centralized entry for every product in your catalogue. It serves as the data intelligence layer that connects your product data to your creative operations, enabling more intelligent production workflows and laying the foundation for agentic capabilities that allow Creative Force to act on your behalf.
Until now, Creative Force has operated at the level of individual production tasks. Product Hub changes the frame of reference from job to product, giving your teams a single place to understand every products creative history, current production status, and business context, regardless of how many times it has gone into production.
Why does this matter?
Today, product data and creative operations live in separate worlds. Your PIM, ERP, and analytics platforms hold the business context. Creative Force holds the production activity. The two rarely speak to each other, which means content decisions are made without commercial or business context, and cross-functional teams have no visibility into what is happening in production.
Product Hub is the bridge. By establishing a product record that connects to both sides, it enables teams to answer questions that were previously impossible to answer quickly:
Has this product been shot before, and what did it produce?
What is the current production status across all active jobs for this SKU?
Which products are the highest priority given inventory or sales data?
Is there existing content that could be reused before scheduling a new shoot?
These are the questions your studio managers, merchandisers, and buyers are already asking. Product Hub gives them a place to find the answers.
Where we are today
Product Hub is currently in closed beta with a select group of customers, but rapidly expanding.
The beta is deliberately limited in scope. The goal for this phase is to validate the core product entity and views with real customer data, identify what is missing, and co-develop the long-term roadmap with customers who have seen the product firsthand.
What is live in the beta today:
Product Records: A persistent product entity identified by product code, data source sync, or automatically when a Content Request is created
Product List & Detail Views: A dedicated Product Hub area in Gamma, with a searchable, filterable product list and a full detail page per product
Production History: Every Content Request ever created for a product, linked to its Product Record, visible in a single view regardless of which job it belongs to
Asset Gallery: All assets produced across every production run for a product, consolidated in one place
Property Management: Reserved properties (product code, name, category, style code, color, brand) and custom properties, manageable at the product level with configurable sync rules for how changes propagate to linked Content Requests
Data Source Integration: Existing data sources to automatically populate and update Product Records as product data changes upstream
Product Display Image: Automatic and manual cover image selection per product record, with support for setting display images directly from production assets
What is not yet available:
Business context integrations (sales data, inventory, returns, etc.) — these external system integrations are currently in discovery
Analytics and performance dashboards
Agentic and AI capabilities
Any API updates, the Gateway API is unchanged and will remain so until a future version is released
General Availability is planned for H1 2026.
What does Product Hub solve for today?
The current version of Product Hub is already in use with a select group of customers. Here is what it is solving for right now.
"I can't see production history for a product across jobs." Studio teams frequently re-shoot products that have already been produced, not because the content failed, but because there was no easy way to know it existed. Product Hub gives every product a production history view: Every Content Request ever created for that item, across every job, with the assets it produced. Before briefing a new shoot, you can see exactly what has been done before.
"The same product appears multiple times and I can't tell them apart." One product in your catalogue can generate dozens of production tasks over its lifetime: seasonal reshoots, editorial uses, variant updates. Today those all appear as separate, disconnected entries, labeled as “Products”. Product Hub consolidates them under a single true product record, so you always have a unified view of a product's creative lifecycle.
"Product data is out of date by the time it reaches production." Several customers are manually updating product attributes in Creative Force every time something changes upstream in their PIM or ERP. Product Hub's data source integration allows product data to sync automatically, so the information your production team is working from reflects the current state of the product, not last week's import.
"I don't know what content exists for my range." Merchandisers and buyers often have no visibility into the creative status of their range without asking the studio team directly. The Product Hub list and detail views give non-studio users a direct, self-service view of what has been shot, what is in production, and what is missing, without needing to navigate individual jobs.
"We're producing content for products that shouldn't be a priority." Without a product-level view, it is difficult to connect production scheduling to commercial priorities. Product Hub provides the foundation for that connection, and in its current form already allows teams to see all production activity for a product in one place, making it easier to identify where effort is being spent.
What will Product Hub solve for next?
The foundation is the product record and views. What comes next is intelligence.
Connecting product performance to content decisions. Teams across multiple customers describe the same problem: Content is produced based on templates and opinions, with no feedback on whether it is actually driving results. The next layer of Product Hub will bring sales data, returns data, and engagement metrics directly into Product Hub, so production teams can see which products need attention, which content approaches have worked, and where to prioritise effort. Customers are manually managing this in Tableau, Google Sheets, and email today. Product Hub will replace that.
Monitoring product data changes and triggering corrective action. When a product's critical attributes change, dimensions, materials, sizing, after content has already been produced, the wrong imagery stays live and drives returns or customer complaints. Product Hub will monitor for these changes and surface alerts, enabling teams to take corrective action before it becomes a problem rather than after.
Identifying redundant content before it gets commissioned. Studios frequently produce content for products that already have perfectly good imagery, either from a previous season, an editorial shoot, or a related variant. Product Hub will surface existing content at the point of commissioning, reducing unnecessary production spend.
Consolidating cross-functional quality management. Today, QC defects, reshoot requests, and image quality issues are tracked in Jira, Google Sheets, email etc. — across multiple teams with no shared record. Product Hub will bring defect tracking onto the product record itself, giving studio, retouching, and merchandising teams a single shared view of quality issues and resolution status.
Launch date and priority tracking. Production teams are often working from manually maintained Google Docs to track which products need to be ready by which date. Product Hub will connect launch dates and priority signals directly to the product record, making it possible to plan and sequence production based on commercial deadlines without relying on spreadsheets.
Agentic operations. Product Hub is the data foundation that makes agentic capabilities possible. With a complete product record that includes history, attributes, and business context, Creative Force can coordinate intelligent actions on your behalf, from proactive reshoot recommendations and automated workflow triggers to quality assurance and content distribution. This is not AI layered on top of existing workflows; it is AI embedded in the platform's decision-making at the product level.
Who is Product Hub for?
Product Hub is designed to serve multiple personas, not just studio teams.
Studio managers and producers use it to track what is in production, identify blockers, access full product history before briefing a new shoot, and eliminate redundant work.
Merchandisers and planners use it to understand the creative status of their range — what has been shot, what is approved, what is missing — without navigating individual jobs.
Buyers and executives use it to connect creative output to commercial priorities, seeing which products have content and which do not relative to launch dates and sales targets.
Data and operations teams use it as the integration layer between their product systems and Creative Force, with configurable data source connections and property sync rules.
How does Product Hub relate to Content Requests?
A Product (in Product Hub) is a persistent record representing an item in your catalogue. It exists independently of any production activity.
A Content Request is a unit of creative work — a request to produce content for a product, scoped to a specific job. One product can have many Content Requests over its lifetime.
The relationship looks like this:
Job → contains one or more Content Requests → each associated with a Product Record in Product Hub
Previously, Creative Force used the term "Product" to refer to what is now called a Content Request. With Product Hub introducing a true Product entity, that term has been reserved for the product record — and the production task has been renamed accordingly.
Frequently asked questions
Is anything changing about how I use Creative Force today? No. Product Hub is an additive capability. Your existing jobs, Content Requests, workflows, and automations are unchanged. The only visible difference is a new Product Hub section in the navigation.
Does this affect our API integrations? No API endpoints or field names are being changed. If your team has integrations built on the Creative Force API, no action is required. A future API version will adopt updated terminology — we will communicate that well in advance.
Will our existing data be migrated into Product Hub? Yes. When Product Hub is enabled on your account, existing production history is linked to product records automatically based on product code. You will not lose access to any historical data.
Do we need a PIM to use Product Hub? No. Product Hub works with or without a PIM integration. You can create and manage product records manually, via file import, or through a connected data source. The PIM integration unlocks richer data and more automated workflows, but it is not a prerequisite.
How does Product Hub handle products that appear in multiple jobs? That is exactly the problem it solves. Regardless of how many jobs a product has been in, it has one Product Record. All production history, assets, and attributes are consolidated under that single record.
When will Product Hub be generally available? Product Hub is currently in closed beta. GA is planned for H1 2026. If you are interested in joining the beta, speak to your Customer Success Manager.
How is Product Hub priced? Product Hub is a fundamental change to Creative Force and will be available to and free for all users. Advanced features such as AI capabilities, Agentic operations, Dashboard and Reports, Alerts and monitoring may come at a price point, at a later stage. Your CSM will share details as they are confirmed.
Who should I contact with questions? Your Customer Success Manager is your first point of contact. For technical questions, reach out to support@creativeforce.io.




