Enterprise
Built for Serious Commerce Teams
Large catalogs need more than a clever model. They need control over who can change product information, a record of every change, and clean ways in and out for the data. This page shows how Creator Hub is designed to provide that.
FAQ: “Can it crush ice?”Orbit Go · drafted by AI from a creator videoAwaiting approver- Attribute: self-clean modeOrbit Go · edited by Marco, EditorAwaiting approver
Claim: “works under sunscreen”Glow Daily Serum · no matching specificationFlagged
Specification: 30-hour batteryPulse Headphones · approved by Priya, ApproverApproved
Platform architecture
Five layers, one governed product record
Information moves left to right. Nothing crosses from Intelligence to Distribution without passing through Governance.
1 · Sources
- Catalog and feeds
- Creator video
- LIVE sessions
- Reviews and questions
- Brand documents
2 · Ingestion
- Connectors Planned
- File and video upload
- Transcription
- Classification
3 · Intelligence
- Attribute and FAQ drafting
- Product Intelligence Passport
- Product knowledge graph
- Readiness scoring
4 · Governance
- Roles and permissions
- Approval workflow
- Claim flagging
- Audit trail
5 · Distribution
- Product feeds Coming Soon
- API and webhooks Planned
- Channel preparation
- Data export
Across every layer: team workspaces · access policies · activity logging
This diagram shows the product design. Components marked Planned or Coming Soon are not yet available. Security details are confirmed in writing during evaluation.
Governance workflow
Every field has an owner and a status
AI can draft. Only a person with the right role can publish. Step through the path one field takes.
Who
The AI Commerce Engine.
What happens
An attribute, FAQ or answer is drafted from a source such as a creator video. It is marked Human Review Required and stays inside the workspace.
What is recorded
The source, the timestamp in the source, and the draft text.
Who
An Editor.
What happens
The editor checks the draft against the source and the specification, corrects it, and sends it for approval. Claims with no matching specification are flagged.
What is recorded
Who edited, what changed, and any flag raised.
Who
An Approver. Editors cannot approve their own work unless your policy allows it.
What happens
The approver accepts, returns or rejects the field. Only accepted fields become eligible for distribution.
What is recorded
The decision, the approver and the time.
Who
The platform, on the channels an Admin has enabled.
What happens
Approved information is prepared in the shape each connected channel expects. Unapproved fields are left out.
What is recorded
Which channels received which version.
Who
Admins and Approvers.
What happens
Anyone with access can trace a published statement back to its source, its editor and its approver.
What is recorded
The full history of the field, kept with the product.
Role-based access
The right people, the right permissions
An example role model. Pick a role to see what it can do. Roles are designed to be adjusted per workspace.
| Permission | Admin | Editor | Approver | Creator | Viewer |
|---|---|---|---|---|---|
| View product intelligence | Allowed | Allowed | Allowed | Assigned only | Allowed |
| Edit product data | Allowed | Allowed | Not allowed | Not allowed | Not allowed |
| Review and edit AI drafts | Allowed | Allowed | Allowed | Not allowed | Not allowed |
| Approve for distribution | Allowed | Not allowed | Allowed | Not allowed | Not allowed |
| Submit creator content | Allowed | Allowed | Not allowed | Allowed | Not allowed |
| Manage integrations | Allowed | Not allowed | Not allowed | Not allowed | Not allowed |
| Manage users and roles | Allowed | Not allowed | Not allowed | Not allowed | Not allowed |
| Export data | Allowed | Allowed | Not allowed | Not allowed | Not allowed |
| View audit trail | Allowed | Not allowed | Allowed | Not allowed | Not allowed |
Audit trail
Who changed what, and when
Every draft, edit, flag and approval is kept with the product. Filter the demo log by who acted.
| Time | Actor | Action | Object | Result |
|---|---|---|---|---|
| 09:14 | Priya Approver | Approved FAQ | “Can it crush ice?” | Published to 3 channels |
| 09:03 | Marco Editor | Edited AI draft | “Can it crush ice?” | Sent for approval |
| 08:52 | Engine AI | Drafted FAQ | From creator video, 0:15 | Awaiting review |
| 08:52 | Engine AI | Flagged claim | “Lasts all week on one charge” | No matching spec |
| 08:40 | Maya Creator | Submitted content | Orbit Go demo video | Linked to 1 product |
| Yesterday | Platform System | Feed check | Inventory feed | 3 days old |
API preview
Product intelligence your systems can read
The Product Intelligence Passport is designed to be machine-readable. Every field carries its source and its review status, so your storefront, search or assistant can decide what to trust.
- REST endpoints for products, fields and content
- Webhooks when a field is approved, edited or flagged
- Bulk export of approved data
The API is planned and not yet available. These examples show the intended shape and may change.
GET /v1/products/NL-BLD-0420/passport
Authorization: Bearer <your-api-key>
Accept: application/json{
"sku": "NL-BLD-0420",
"name": "Orbit Go Portable Blender",
"brand": "Northlane",
"price": { "amount": 59.00, "currency": "USD" },
"availability": "in_stock",
"readiness": { "score": 84, "metric": "creator_hub_internal" },
"attributes": [
{ "name": "capacity", "value": "13 oz",
"source": "product_feed", "status": "approved" },
{ "name": "self_clean", "value": true,
"source": "creator_video", "status": "needs_review" }
],
"faqs": [
{ "question": "Can it crush ice?",
"answer": "Small cubes, with liquid added.",
"drafted_by": "ai", "status": "approved",
"approved_by": "priya" }
],
"content": [
{ "type": "product_demo", "creator": "maya",
"timestamps": [4, 15, 27] }
]
}{
"event": "passport.field.approved",
"sku": "NL-BLD-0420",
"field": "faqs[0]",
"previous_status": "needs_review",
"status": "approved",
"approved_by": { "id": "priya", "role": "approver" },
"channels_updated": 3
}Your stack
Where Creator Hub fits
Creator Hub works alongside the systems you already run. It does not replace your commerce platform, PIM or DAM.
| System you run | What it is the record for | What Creator Hub adds beside it |
|---|---|---|
| Commerce platform | Storefront, checkout and orders | Approved product knowledge and creator content for your product pages. Creator Hub is not a storefront. |
| PIM | Catalog structure and core attributes | Attributes and answers found in creator content and customer questions, each with a review status. |
| DAM | Media files and usage rights | What each video says about each product, with timestamps. |
| Creator platform | Creator relationships, briefs and payments | The product knowledge inside the content creators deliver. |
| Feed management | Channel-specific feed formatting | A reviewed source of attributes and answers to feed from. |
Rollout
Start with one category, not the whole catalog
Four phases. Timing depends on your catalog and is agreed with you, so none is quoted here.
- 01
Discover
Map your catalog, channels, creators and review process. Agree who holds which role.
- 02
Connect
Import one product category and the creator content that features it.
- 03
Pilot
Your editors and approvers work the queue. Measure completeness before and after.
- 04
Scale
Extend to more categories, brands and channels using the roles and workflow you proved.
Procurement
Questions your security and legal teams will ask
We answer these in writing during evaluation. Talk to sales.
Do you hold SOC 2, ISO 27001 or other certifications?
No certification is claimed today. We will list a certification only after it has been achieved, and we will tell you where we are in any audit when you ask.
Where is our data hosted?
Hosting region and data residency options are confirmed in writing during evaluation. We do not publish commitments here that we cannot yet guarantee for every customer.
Is our content used to train AI models?
Data-use terms, including whether any customer content may be used to improve models, are set out in the contract and data processing terms. Ask us for the current version before you share data.
Do you support single sign-on?
Single sign-on and user provisioning are planned. Tell us which identity provider you use so we can confirm timing for your setup.
Is there a service level agreement?
Service levels are agreed per contract. No uptime figure is quoted on this site because we have not yet published one we can stand behind.
Can we get our data out?
Yes, by design. Data export is part of the platform so that approved product information is never locked in.
Talk to Sales
Bring your requirements
Tell us about your catalog, your review process and your security questions. We reply by email with next steps.
- Answers to security and legal questions in writing
- A walkthrough built around your own category
- No commitment and no payment details