Brand Hub
Brand Hub is CataZenta’s brand-facing experience layer: a curated, consumer-style view of your catalog built on the same governed PIM and DAM data your team masters in the back office. It helps marketing, sales, and leadership see how products actually present — on the web and on mobile — without exporting spreadsheets or logging into marketplace admin tools.
Why Brand Hub exists
PIM is where teams edit and approve product truth. Marketplaces and Shopify are where you sell. Brand Hub sits in between for people who need to experience the brand:
| Audience | What they need |
|---|---|
| Brand & marketing | Proof that copy, imagery, and attributes read correctly before launch |
| Sales & wholesale | A trustworthy catalog to show buyers, reps, or partners |
| Leadership | Confidence that the “store” view matches what syndication will push |
| Field teams | Mobile access to the same approved products in showrooms and meetings |
Without Brand Hub, those teams often rely on outdated PDFs, screenshot decks, or sandbox stores that drift from the real catalog.
How Brand Hub relates to PIM and DAM
| Layer | Role |
|---|---|
| PIM | Source of truth: products, variants, attributes, locales, completeness |
| DAM | Hero and alternate images linked to SKUs; renditions for display |
| Workflows | Reviews before products are treated as customer-ready |
| Brand Hub | Read-oriented Store Front (and upcoming catalog tools) on approved data |
| Syndication | Machine exports to external channels — separate from the Brand Hub UI |
Brand Hub does not replace syndication. It gives humans a brand-correct preview and browse experience while syndication handles channel APIs and jobs.
Brand Hub in the web app
In the CataZenta web application, switch to Brand Hub from the top app switcher (alongside PIM). The Brand Hub area includes:
Store Front
Browse and open approved products in a storefront-style grid and detail layout:
- Product cards with linked DAM imagery
- SKU, family, and attribute summary on the detail page
- Search and filters aligned with how buyers discover products — see Search & filters guide
Store Front is the primary way teams validate “what shoppers or buyers will see” before or alongside channel publish.
Digital Catalog (rolling out)
Curated digital catalogs for seasons, collections, or B2B lines — packaged presentations of approved products without rebuilding decks by hand. Contact your CataZenta team for availability in your tenant.
Product Tags (rolling out)
Merchandising tags for campaigns, capsules, and internal groupings that span categories. Useful for sales narratives and curated Store Front views.
Product preview from PIM
When editing a product in PIM, use Preview and select Brand Hub to open the same Store Front detail experience for that SKU. Editors can check layout and copy without leaving the enrichment workflow.
CataZenta mobile app
The CataZenta mobile app (iOS and Android) extends Brand Hub for people who are not at a desk:
| Use case | Benefit |
|---|---|
| Showrooms & trade events | Pull up the live approved catalog on a phone or tablet |
| Field sales | Share accurate SKU facts, images, and attributes in meetings |
| Buyer conversations | Avoid “I’ll email you the sheet” — show the same data as PIM |
| Executive review | Quick spot-check of how a launch collection presents |
The mobile app uses your organization sign-in and tenant scope — the same identity boundary as the web PIM. Only products and media your team has approved for publication appear in the mobile browse experience, consistent with Store Front on the web.
Mobile vs web Brand Hub
| Web Brand Hub | Mobile app | |
|---|---|---|
| Best for | Merchandising review, desktop detail work | Field sales, events, on-the-go browse |
| Data source | Tenant PIM + DAM APIs | Same tenant APIs |
| Sign-in | Browser session | Native app with secure token refresh |
| Offline | Requires connectivity | Optimized for brief connectivity gaps where supported |
Your administrator provisions mobile access with the same user and role model as the web platform.
Who should use Brand Hub
| Role | Typical tasks |
|---|---|
| Brand manager | Validate collection presentation before campaign launch |
| Sales / wholesale | Present catalog to buyers with correct imagery and claims |
| Marketing ops | Align Store Front with D2C or marketplace copy |
| PIM editor | Preview Brand Hub while enriching attributes and DAM links |
Developers automating catalog changes still use the REST API or MCP; Brand Hub is the human-facing surface.
Permissions and governance
Brand Hub respects tenant isolation and your role permissions. Users without Brand Hub access do not see Store Front or the mobile catalog for that tenant.
Governance practices that keep Brand Hub trustworthy:
- Completeness — required attributes filled before approval (guide)
- Workflows — legal/brand sign-off before products are approved (guide)
- DAM — only linked, approved assets surface on cards and detail pages (guide)
Getting started
- Sign in to the CataZenta web app with your tenant.
- Open Brand Hub → Store Front and search for an approved product.
- In PIM, open a product → Preview → Brand Hub to compare edit vs presentation.
- Install the mobile app from your organization’s invite (App Store / Play Store links provided at onboarding).
- For API-based custom storefronts, use the same product and DAM APIs documented under API overview.
Related reading
- How brands win — platform story for brand teams
- Why PIM — master data foundation
- Why DAM — media at scale
- Using the PIM UI — back-office navigation
- Zen AI — enrichment before Brand Hub preview