Shared data. Clear boundaries.

Kaduno is one modular business platform. Products, customers, orders and inventory work in context, while PullPush handles connections to external systems.

How the work flows

A practical view of the process. The exact setup depends on your business and the capabilities you use.

  1. Choose a focused starting point

    A business can start with products, warehouse or sales. The agreed setup determines which parts the team uses and which external systems remain.

  2. Use shared business objects

    The catalogue product connects to order lines and stock flow. The customer connects to contact details, commerce and follow-up. Business data carries the context.

  3. Connect the rest through PullPush

    External synchronization has its own place. ERP, accounting, webshops, suppliers and other systems connect with agreed direction and ownership, and every run has a history. PullPush is in beta.

The details that matter in operation

Configuration, rules and boundaries to review before rollout.

Business domains, beyond navigation

Catalogue, orders, customers, inventory, purchasing and production have their own rules. The modules you buy group the relevant areas around the work you need to do.

Store and business context

Business data belongs to one store, and nothing is shown until a store is selected. This holds for every role, platform administrators included. A user’s permissions can also be set per store. Multi-store setups require agreement on roles and data sharing.

APIs, webhooks and synchronization

Kaduno has APIs and webhooks for integrations. PullPush runs the synchronizations with external systems, with its own connections and flows per store. A connected system does not become part of Kaduno’s shared data model merely through integration.

AI uses the same working environment

Kai works with the same data and permissions as the person asking. Changes go through a card you confirm, and what Kai may do is decided by the store’s settings, not by what Kai is asked.

Before you start

Do we need to understand the architecture to use Kaduno?

No. Your team works on its tasks. Architecture matters when assessing data ownership, integrations, security and expansion.

Which system is the source of truth?

This is agreed per area: products, customers, stock, orders and accounting. During phased rollout, some areas can live in Kaduno and others in existing systems.

Start with one module.
Expand when you need to.

Tell us where it hurts — and we will show you how Kaduno solves it. A 30-minute demo, in Norwegian or English.

NO/EN · GDPR · DATA HOSTED IN NORWAY