Kibo CMS Integration Overview

Kibo CMS is the content management layer within the Kibo Composable Commerce Platform. It provides headless CMS capabilities and a visual Website Builder alongside Kibo’s commerce APIs, enabling teams to manage content and commerce data from a unified platform. This page explains the key integration points between Kibo CMS and the broader Kibo platform for implementation engineers and solution architects.

​

Architecture Overview

Kibo CMS operates as a composable layer that sits alongside the rest of Kibo’s commerce services. Content is authored and managed through the Kibo CMS admin interface, then delivered to storefronts and other consumers via a GraphQL API. The platform consists of three main functional areas:

• Website Builder — A visual page editor for building and publishing web pages, including dynamic pages that pull live data from the Kibo Commerce catalog.
• Headless CMS — A structured content management system with a GraphQL API, content models, and revision history for managing arbitrary content types.
• File Manager — Centralized asset storage and management for images and other media used across pages and content entries.

Kibo CMS is designed to be consumed headlessly. Frontend applications query the GraphQL API to retrieve published content, and the platform does not prescribe a specific rendering framework.

​

Multi-Tenant Model

Kibo CMS uses an isolated multi-tenant architecture. Each company or brand is provisioned as its own tenant with a dedicated content space — content, users, roles, and configuration in one tenant are completely isolated from all others. To provision a new Kibo CMS tenant, raise a support request with Kibo Support. Support will establish the isolated workspace and install default configuration for your company.

​

Kibo Commerce Integration

The Kibo CMS Website Builder connects directly to the Kibo Commerce product catalog. This allows content authors to create dynamic pages that render live product and category data rather than static copies.

​

Dynamic Page Types

Two dynamic page types are available in the Website Builder: These pages are bound to a specific product or category record at authoring time. In the page editor, authors use built-in product and category pickers to select the record. The picker supports free-text search by product name, product code, category name, or category code. At render time, the storefront receives the page configuration including the bound product or category identifier, then fetches the corresponding data from the Kibo Commerce API to populate the page.

​

Product Data Mapping

When a product is resolved from the Kibo Commerce catalog, the following fields are used by the Website Builder:

​

Category Data Mapping

When a category is resolved from the Kibo Commerce catalog, the following fields are used:

​

Content Delivery

Published content from both the Website Builder and Headless CMS is delivered through a GraphQL API. Consumer applications — storefronts, mobile apps, or third-party systems — query this API to retrieve content. Key characteristics of the content delivery API:

• All content is returned as structured JSON via GraphQL queries.
• Published and draft content states are tracked separately; consumers typically query published content only.
• The API supports filtering, sorting, and pagination for content entry lists.
• Responses include revision metadata, enabling consumers to implement caching strategies tied to content version.

​

Getting Started