Get started with Kaduno PIM EN
Create and enrich products, check content health and confirm publishing and field-ownership rules.
This English guide follows the Norwegian PIM guide,
with the activation and enforcement gates checked against source on 13 November 2026. It is not confirmation that your installation has passed acceptance.
Paths beginning /admin/ belong to your store's administration, not kaduno.com.
Before you start
Select the correct store. Normal product editing is under Products
(/admin/products) and requires write permission. The additional product-data
rules, sales channels and channel-publishing surfaces require Kaduno PIM under
Settings → PIM (/admin/settings/pim). The setting defaults to off; stores
already using these capabilities may have it enabled.
With PIM disabled, normal products remain available, saved rules/channels are retained, and PIM rules do not block publication. Availability also depends on the installed version, licensing and role. Do not change production settings as a test.
Create or import products
Create a product in Products, or open /admin/import and choose Products.
Inspect the import preview and map identity fields such as SKU, name and units.
A preview is not the import itself. Save a reusable column mapping where useful,
and validate a small agreed sample before committing a larger import. Prices use
the separate Prices data type. A supplier CSV is not automatically correct.
On the product, review category, attributes, variants and media. An existing product can be linked as a variant and detached again. Confirm product identity and variant structure before adding prices and stock: other systems may depend on these identifiers. Do not re-import an uncertain result without checking whether products were already created or updated.
Content health, SEO and publishing rules
Content health (/admin/content-health) groups gaps in products, PIM rules,
SEO, translations and pages. Follow a score to the affected records. A score
reflects configured rules; it is not certification that an external marketplace
will accept the product or that the product facts are correct.
Kai can help prepare missing text where AI is enabled. Review factual accuracy, claims and the actual save/approval flow before using it. Do not assume every AI operation shares one confirmation mechanism; see AI controls.
Under Settings → PIM, a data rule can be scoped to category or product type, weighted, enabled and marked as blocking. PIM rules block publishing is a separate setting, off by default. Blocking requires PIM and that setting to be active; a failing blocking rule without a waiver then blocks a change that would make a previously non-visible product visible. It does not automatically unpublish products that are already visible. Do not infer blocking from a score or a rule label alone.
Use /admin/seo and /admin/seo/missing to review SEO gaps. Correct the relevant
fields and check again. A successful SEO check is not a search-ranking promise.
Respect the system that owns each field
Where an ERP or external PIM owns fields, declare the ownership under Settings → PIM. Declaring ownership and enforcing it are different steps. The external PIM/field-ownership enforcement switch defaults to off. With it enabled, declared fields are read-only through the applicable staff, Kai, MCP and import paths, within the ownership policy's scope. The owning source, products it writes, fields actually written under its ingest policy and explicit unlock overrides affect that scope. Confirm these rules and installed enforcement before relying on a lock.
Descriptions, SEO and media can remain editable when they are not externally owned; do not assume those categories are always exempt. Per-source ownership can also keep a synchronization from overwriting fields maintained by staff. Agree ownership rather than repeatedly overwriting each other's changes.
Sales channels and approval
With PIM enabled, configure channels under Settings → Sales channels
(/admin/settings/channels). Channels can represent branded storefronts on the
same store; a catalogue channel can show products/search without selling.
Assign products to the intended channels from the product page.
Where product approval is required, use Submit for approval and let the appropriate reviewer approve or reject. Publishing in Kaduno and exporting to an external webshop are separate operations. External delivery needs a configured flow, correct mapping and a checked destination result.
Troubleshooting and acceptance
- Product absent: check store, status and channel assignment.
- Unexpected score or publication block: inspect active rules, blocking setting, waivers and whether the evaluation is current.
- Duplicate import: inspect SKU/identity mapping and existing records before retrying.
- Field cannot be changed: check the owning system and enforcement; do not disable ownership merely to bypass a rejected edit.
- External product incomplete: check mapping and export result. Internal publication does not prove external delivery.
Use synthetic products in an agreed environment to check a normal edit, a denied owned-field edit, a failed blocking rule and an approved publication. Publication or external export is a real action, not an automatic part of reading this guide. Record permitted effects and cleanup before testing. Continue with integration boundaries.