Skip to main content

An Important Update to Creative Force

Clearer Language. Smarter Platform.

Written by Heather Camp Lopes
Updated today

What’s Happening

We’re making a terminology update within Creative Force, and we want to tell you about it early, explain why it matters, and give you a voice in the final decision.

Starting June 2, 2026, what you currently know as a “Product” in Creative Force, will be renamed to “Content Request.” (The exact name will be confirmed after we hear from you.)

Why We’re Making This Change

Today, the same product in your catalogue can have multiple "Products" in Creative Force, one for each time it goes into production. That means a single pair of shoes might appear as five separate "Products" in your account. The name describes a request for product content (images, videos, texts etc.), not the item itself, and that disconnect has always caused friction.

Solving it required something Creative Force has never had before: a true product record. One persistent entry for every item in your catalogue- with its own creative history, status, and context across every shoot and campaign. That's Product Hub.

Product Hub is the data intelligence layer that connects your product data to your creative operations. It consolidates product information from your existing systems, enables more intelligent production workflows, and lays the foundation for agentic capabilities that will allow Creative Force to act on your behalf. With a real product record now in the platform, the word "Product" finally means what it should.

To keep things clear, we're renaming the production task you've been working with , the job-level unit of creative work associated with a job, to "Content Request."

One word for your real-world product. One word for your creative task. No more confusion.

What’s Not Changing

We want to be direct about what this change does, and doesn’t, affect:

  • Your workflows and automations: Nothing changes about how jobs, tasks, or requests are processed.

  • Your API integrations: No API endpoints or field names are being changed. If you have integrations built on the Creative Force API, no action is required on your side.

  • Your historical data: All existing requests and history remain exactly as they are.

  • Your team’s day-to-day experience: The change is a label update. The platform works exactly as it does today.

We Want Your Input

We haven’t finalized the new name yet. Our two candidates are “Content Request” and “Production Request.” We’re running a short survey to gather your preference, and we’d love for you to participate.

Your input will directly inform the final decision.

Survey closes: April 15th, 2026

What to Expect between now and June

We will be running the survey over the next couple of weeks to get feedback from our customer-base. With the aim to share our final results in April. We will also be updating our knowledge base, academy and UI to better reflect the change as of the 2nd.

Questions?

Your Customer Success Manager is your first point of contact for any questions about this change. You can also reach the support team at support@creativeforce.io.

Did this answer your question?