Kontent CMS: retail content in 2026

Assess Kontent’s CMS for structured retail guidance. Check content relationships, editorial workflow and delivery while keeping it distinct from Kentico.

Kontent CMS, now Kontent.ai, suits retailers that need reusable, governed content delivered to separately built customer experiences. Its headless model lets a category guide and a customer-answer service draw from the same approved guidance. Your team still owns the storefront and its connections to commerce and search.

Identify Kontent and its naming history

Kontent.ai is the current product behind the historical Kentico Kontent and Kontent by Kentico names. Its company introduction identifies it as a standalone company with a headless content management system (CMS). Historical naming explains older implementation material. It does not make current Kentico features part of Kontent.ai.

Assess Kentico separately when comparing that product. For Kontent.ai, the central job is creating structured content and delivering it through an application programming interface (API). That interface lets another application request approved content fields.

The retail implementation needs a frontend to render those fields into pages. It also needs a commerce system for transactional product facts and a search service for retrieving products. Kontent.ai’s pricing guidance describes connections to commerce platforms and search engines. Treat each connection as a defined implementation, with an owner and supported data flow.

Model reusable product guidance

Model guidance as content items with references to shared policies and external product identifiers. This keeps an editor’s advice reusable without turning it into a second source of price or stock.

Consider a fictional bedding retailer. Its mattress-buying guide explains firmness and care, links a delivery-policy item and stores catalogue identifiers for illustrative products. Each identifier points to a product in the retailer’s commerce system. The guide stores no copied stock count or selling price. The frontend retrieves those changing values from the commerce system when it displays a product.

Kontent.ai’s linked items documentation describes adding a Linked items element to a content type. That element can be limited to an allowed content type. In the fictional model, the guide’s policy reference accepts policy items. Editors select the shared delivery policy instead of pasting its wording into every guide.

A content item and its language variants have different responsibilities. The item keeps its identity, while each variant has its own workflow information and versions. Kontent.ai documents this distinction in its language variants guide.

For an Australian-English guide and another language, record which policy variant each audience receives. Linked content can follow configured language fallbacks. A fallback can return content in a different language, so a populated response alone does not prove the policy is suitable for the shopper’s market.

Publication states need the same care. A guide can reference a policy that is still in draft. Kontent.ai’s publishing process lets editors publish linked items alongside the parent. Your editorial rule must establish whether that policy is approved for release before selecting it.

Deliver the right version to customer answers

Send approved content through the published Delivery API and keep draft review in an authenticated preview application. Publishing in the CMS is one stage in a longer path to the customer’s answer.

In the fictional mattress guide, an editor corrects the care instructions and submits the change for review. The reviewer opens the preview application to inspect the latest content. Kontent.ai’s preview configuration instructions require an API credential for preview requests and server-side handling to keep it secret. The preview URL also needs access control so unauthorised visitors cannot read drafts.

After approval, the publisher releases the guide and any required linked policy variant. The production application requests the published content. Kontent.ai distinguishes published versions from the latest draft versions through its published-content and preview interfaces. Published content is public by default unless secure access is enabled.

Kontent.ai’s delivery-cache documentation says cached API responses are removed when their content changes. Your application can have additional stored copies. A static page or a service that retrieves passages for customer answers needs its own refresh process.

Store the source item identifier and language with each retrieved passage. Keep an internal record of the version or content fingerprint imported. When the guide changes, replace the stored passage and check that the next answer uses the corrected instruction.

Before using that pipeline for retail assistance, define these acceptance checks:

  1. An unauthorised visitor cannot open draft guidance through the preview route.
  2. A published correction reaches the public page and the answer service after their refresh processes.
  3. An unpublished guide is removed from stored answer material and stops appearing in new answers.
  4. A missing policy reference produces a controlled fallback, such as withholding the affected answer and offering staff help.
  5. The guide and every retrieved policy use an approved language variant for the customer’s market.

These checks belong to your implementation. A successful CMS publish action alone cannot establish the result in a separately maintained answer service.

Assess editors and operating work

Match Kontent.ai’s permissions and subscription capabilities to the decisions your editors actually make. A guide writer, a policy reviewer and a publisher need different authority over the shared content.

Kontent.ai’s workflow documentation supports role restrictions on workflow steps and configurable transitions. Adding separate workflows requires Multiple workflows to be enabled for the subscription. In a proposed retail process, category writers prepare guides, policy reviewers approve mandatory wording and publishers release the approved variants.

Compare that process with the contracted user access and workflow scope. Include environments, required languages, delivery usage and support coverage in the commercial assessment. The pricing page states that plans can be adjusted and users added. Its support description includes in-app chat across plans, with dedicated customer-success and customised onboarding support for Enterprise plans. Keep those support services separate from responsibility for your storefront code.

Migration work starts with deciding which existing text becomes a shared item and which stays within a guide. Map identifiers before importing content, rebuild policy references and assign each language variant to its review process. Then implement page components and the connection that joins catalogue identifiers to current product facts.

Ongoing work includes reviewing ageing guidance and removing references to retired products. Assign an owner to failed content refreshes and withdrawn advice. Kontent.ai is a strong fit when shared content and editorial controls solve a recurring publishing problem. Include that maintenance work when comparing CMS platforms, so the choice reflects the complete route from an editor’s correction to the customer’s answer.

Give your store its own shopping agent

Customers ask in their own words. Your agent finds, compares and checks out from your catalogue, right on your site.

See it in actionFree trial · Simple setup