Kentico - Centric Integration and Automation

Common Integration Use Cases Between Kentico and Centric

1. Product launch content synchronization from Centric to Kentico

Data flow: Centric to Kentico

When a product reaches launch readiness in Centric, approved product attributes, descriptions, technical details, and imagery can be pushed into Kentico to create or update product pages automatically. This reduces manual rekeying, shortens launch timelines, and ensures the website always reflects the latest approved product information.

2. Enriched product storytelling using DAM assets across both platforms

Data flow: Bi-directional via DAM-connected processes

Centric can manage product development assets such as renderings, spec sheets, and line sheets, while Kentico uses approved marketing assets for web publishing. Integrating both platforms through a shared DAM workflow ensures that only approved images, videos, and documents are used in customer-facing content and product development materials. This improves brand consistency and reduces the risk of outdated or unapproved assets being published.

3. New product introduction workflow from PLM to digital commerce

Data flow: Centric to Kentico

As new products move through concept, sample, and approval stages in Centric, key milestones can trigger content preparation in Kentico. Marketing teams can begin building landing pages, campaign content, and category placements before launch, using structured product data from Centric. This supports faster go-to-market execution and better coordination between product, merchandising, and digital teams.

4. Product content updates and corrections from Kentico back to Centric

Data flow: Kentico to Centric

Customer-facing teams may identify content gaps, naming inconsistencies, or missing product details in Kentico after launch. Those corrections can be routed back to Centric so product teams can review and update the master product record. This creates a controlled feedback loop that improves product data quality over time and helps prevent repeated content errors across channels.

5. Campaign-specific product assortment publishing

Data flow: Centric to Kentico

Centric can provide approved product assortments, seasonal collections, or line plans to Kentico for use in campaign pages and promotional microsites. Kentico can then publish curated product sets aligned to launch calendars, regional promotions, or market segments. This enables marketing teams to build targeted experiences without manually assembling product data from multiple sources.

6. Centralized product attribute governance for web content

Data flow: Centric to Kentico

Centric can serve as the system of record for product attributes such as dimensions, materials, compliance details, and variant information. Kentico consumes this structured data to populate product detail pages, comparison tables, and downloadable content. This improves data governance, reduces duplication, and ensures that customer-facing information stays aligned with approved product specifications.

7. Regional and channel-specific content adaptation

Data flow: Bi-directional

Centric can provide core product data and approved variants, while Kentico can manage localized content, campaign messaging, and channel-specific presentation. Integration supports regional teams that need to adapt product pages for language, market requirements, or retail channels without altering the master product record. This helps maintain global consistency while allowing local flexibility.

8. End-to-end product and content approval workflow

Data flow: Bi-directional

Product teams in Centric and digital teams in Kentico can share approval status, launch readiness, and content completion signals. For example, once product specifications are finalized in Centric, Kentico can be notified to complete web content review, and once web content is approved, Centric can mark the product as ready for launch. This improves cross-team visibility, reduces launch delays, and creates a more controlled release process.