Overview
The Marketplace Hub is a B2B content exchange where workspace owners can publish catalogs for other businesses to discover, clone, or subscribe to. It works both as a distribution channel (publisher perspective) and a content sourcing tool (consumer perspective).Publisher perspective
As a publisher, you expose your catalog to the marketplace ecosystem — whether for free or for a fee.Publishing a catalog
- Ensure your catalog has completed at least the Silver pipeline stage
- Navigate to the catalog → Marketplace tab
- Configure visibility, pricing, and category
- Click Publish to Hub
Pricing models
| Model | Description |
|---|---|
| Free | Catalog is freely cloneable and subscribable |
| Paid (via Stripe) | Consumers pay a one-time or recurring fee managed via Stripe Checkout |
Catalog versioning
Every time you update a published catalog (add products, run Silver/Gold, edit metadata), a new version is created automatically. Versions are immutable snapshots.| Version field | Description |
|---|---|
version | Auto-incrementing integer (v1, v2, v3…) |
createdAt | Timestamp of the version |
changeCount | Number of products added/updated/removed |
publishedBy | Member who triggered the publish |
Publisher analytics
Track catalog performance from the Analytics tab or via API:- Views — how many times the catalog preview was opened
- Clones — total one-time copies made
- Active subscribers — workspaces with live subscriptions
- Revenue — total collected (for paid catalogs)
Unpublish / delist
To remove a catalog from the Hub:- Navigate to the catalog → Marketplace tab
- Click Unpublish
Consumer perspective
As a consumer, you browse the Hub to discover catalogs, preview products, and either clone or subscribe.Browse and discover
The Hub browse page supports:- Search by keyword (catalog name, brand, description)
- Filter by category, price (free/paid), minimum score
- Sort by: Popular, Recent, Optimization Score
Preview without committing
Every published catalog offers a preview of its first 10 products plus aggregate stats (total count, average score, top categories, top brands) — no clone required. Use preview to evaluate fit before subscribing.Clone — one-time copy
Clone creates a local snapshot of the catalog in your workspace. It does not establish an ongoing connection.- All products are copied into a new catalog in your workspace
- You can edit, enrich, and redistribute freely
- No sync — you won’t receive future updates from the publisher
Subscribe — live sync
Subscribe creates a live link between your workspace and the publisher’s catalog. When the publisher releases a new version, you are notified and can sync.Sync strategies
| Strategy | Behavior |
|---|---|
auto | New versions are automatically applied to your local catalog |
manual | You review and approve each sync via the UI or API |
Conflict resolution strategies
When a synced product has local edits that conflict with publisher updates, the conflict resolution strategy determines the outcome:| Strategy | Behavior |
|---|---|
keep_local | Your local edits always win; publisher changes are discarded for that field |
accept_remote | Publisher changes always win; your local edits are overwritten |
manual_review | Conflicts are queued for manual resolution — neither side auto-wins |
Conflict resolution flow
Catalog versioning model
Each subscriber can be on a different version. Syncing always moves forward — you cannot roll back to a previous publisher version.Access control
| Action | Who can do it |
|---|---|
| Publish catalog | Workspace owner or admin |
| Set pricing | Workspace owner only |
| View analytics | Workspace owner or admin |
| Unpublish | Workspace owner only |
| Clone/subscribe | Any authenticated workspace |
| Preview | Anyone (public) |
Best practices
Run Silver before publishing
Run Silver before publishing
Consumers judge catalog quality by normalized data. Publish after Silver (and ideally Gold) to maximize discoverability and subscriber conversion.
Version your catalog intentionally
Version your catalog intentionally
Each save to a published catalog creates a new version and notifies subscribers. Batch your edits and publish once rather than making many small changes.
Choose conflict resolution per use case
Choose conflict resolution per use case
Set
keep_local when your downstream team adds custom descriptions or pricing. Set accept_remote for supplier feeds you use verbatim.Monitor analytics after publishing
Monitor analytics after publishing
High view counts with low clone rates indicate a mismatch between catalog metadata and content. Improve your title, description, and category tagging.