Connect Kaduno to the systems you already use.

An integration should serve a workflow. Explore what each connection does, the setup it needs and where to learn more.

The right setup for your business

A listed connection is not automatically enabled for your store. Availability depends on modules, provider agreements, access and configuration. Before launch, we agree what data flows where, which system owns it and how errors are handled.

Accounting

Tripletex

Through the Kaduno accounting hub

Kaduno Finance Beta

Connect invoicing to Tripletex through the Kaduno accounting hub. The scope is agreed during setup.

Data and direction
Invoices, credit notes and payments go through the hub. Status and documents return through the hub, according to the configured capabilities.
Ownership and limits
Agree which system invoices. When the ERP creates the invoice, Kaduno must not create another. This is not a general two-way sync of all accounting data.
Before you start
Choose the invoicing provider and trigger. The platform administrator supplies the hub URL, API key and webhook secret. Tripletex credentials are not entered directly in Kaduno.
Operations and error handling
Check export status and the receiving system before retrying. Correct the cause before retrying the export; missing status does not mean the invoice is missing.

ERP and orders

Visma.net

Through PullPush; separate flows and access requirements

Connect new online orders to Visma.net and agree which ERP data Kaduno should receive. This covers Visma.net, not every Visma product.

Data and direction
New online orders can be created as Visma.net sales orders. Separate PullPush flows can mirror warehouses, stock, recipes and kits into Kaduno and transfer shipment data.
Ownership and limits
Order export creates orders; it is not general bidirectional synchronisation. Confirmed shipments and quiet history imports have different effects. Agree invoice ownership and stock responsibility.
Before you start
Requires PullPush configuration, field mapping and access to the correct Visma company. Sales Order Service has separate access requirements; a successful Financials test does not prove order export works.
Operations and error handling
Check orders and partial shipments in both systems before launch. Agree sync frequency, monitoring and discrepancy handling. Source review is not customer-specific production acceptance.

Payments

Vipps MobilePay · Klarna · Stripe · Two.inc

Requires a provider agreement and setup

Let customers pay with methods suited to their purchase. These are examples from the payment catalogue; the guide lists more providers.

Data and direction
Kaduno sends payment requests and receives transaction status. Authorisation, capture and refunds are distinct operations, depending on the provider.
Ownership and limits
The provider handles payment and settlement. A return request is not a refund. Features and eligible customer types vary with the agreement.
Before you start
Use the store’s own provider agreement and credentials. Choose customer groups, check Test or Live mode and test the full payment flow before activation.
Operations and error handling
Monitor failed payments in Kaduno and check provider status before repeating a charge. Agree who follows up discrepancies and settlement.

Payment providers: integration capabilities

Source reviewed 13 November 2026. This table describes implemented adapter capabilities, not activation or acceptance testing in your store. Scroll sideways on narrow screens; the table region supports keyboard focus and arrow-key scrolling.

Payment providers: integration capabilities
ProviderCheckout flowCaptureRefundBefore use
Vipps MobilePayImplementedImplementedImplementedRequires an agreement, credentials and store-specific flow testing.
KlarnaImplementedImplementedImplementedRequires an agreement, credentials and store-specific flow testing.
Nets EasyImplementedImplementedImplementedRequires an agreement, credentials and store-specific flow testing.
WorldlineImplementedImplementedImplementedRequires an agreement, credentials and store-specific flow testing.
BamboraImplementedImplementedImplementedRequires an agreement, credentials and store-specific flow testing.
StripeImplementedImplementedImplementedRequires an agreement, credentials and store-specific flow testing.
PayPalImplementedImplementedImplementedRequires an agreement, credentials and store-specific flow testing.
Dintero CheckoutImplementedImplementedImplementedRequires an agreement, credentials and store-specific flow testing.
Svea CheckoutImplementedImplementedImplementedRequires an agreement, credentials and store-specific flow testing.
Two.incBusiness purchases with eligibility checksDelivery / fulfilment flowPartial refunds require original line allocationConfirm company eligibility, agreement, invoice ownership and fulfilment before capture.
Faktura / InvoiceOrder recorded as unpaidNo provider authorisationHandled in the invoicing workflowThis is not a payment service or external credit approval.

Before production: confirm the provider agreement, access, environment, chosen services and data mapping. Test the complete flow and agree error handling and reconciliation. A catalogue entry is not evidence of operational readiness.

Shipping

Bring · PostNord · Cargonizer · nShift

Capabilities vary by provider

Connect checkout delivery choices to warehouse packing. These are examples; the shipping guide covers more carriers.

Data and direction
Address, parcel and service data are used for rates or booking. Labels and tracking return where supported by the carrier. Bring and PostNord can also offer pickup points.
Ownership and limits
The carrier owns booking and tracking status. Rate lookup does not imply booking, labels or returns are supported. Return labels are supported only for the carriers specified in the guide.
Before you start
Enable shipping management, configure the carrier agreement and sender, and test with correct weights, dimensions and addresses. Confirm the capabilities covered by the agreement.
Operations and error handling
Check whether the carrier already created the shipment before booking again. Follow up missing labels and agree responsibilities between the store, warehouse and carrier.

Shipping providers: rates, booking and returns

Source reviewed 13 November 2026. This table describes implemented adapter capabilities, not activation or acceptance testing in your store. Scroll sideways on narrow screens; the table region supports keyboard focus and arrow-key scrolling.

Shipping providers: rates, booking and returns
ProviderRatesBooking / labelReturn labelImportant limit
BringRate requestBooking and labelImplementedOutgoing bookings require sender phone; pickup points require recipient phone or email. Cancellation is handled with Bring.
PostNordFixed or zone rates, not a standalone live-rate APIBooking and labelImplementedPickup points supported. Cancellation must be handled with PostNord.
CargonizerRate requestBooking and labelBring/PostNord return servicesServices, agreements and the return product must be configured.
DHL ExpressRate requestBooking and labelNot supported by this adapterRequires an agreement, credentials and store-specific flow testing.
FedExRate requestBooking and labelNot supported by this adapterRequires an agreement, credentials and store-specific flow testing.
DSV XPressRate requestBooking and labelNot supported by this adapterRates and booking require separate service keys.
Gordon DeliveryDelivery window + window, zone or fixed priceBooking and tracking reference; no label in the adapter responseNot supported by this adapterCancellation is handled with Gordon. Confirm the actual delivery window.
nShift Ship / Shipment ServerRate requestNot through this adapter; ERP/BX workflowNot supported by this adapterPickup points require a product code. No tracking URL from this adapter.

Before production: confirm the provider agreement, access, environment, chosen services and data mapping. Test the complete flow and agree error handling and reconciliation. A catalogue entry is not evidence of operational readiness.

AI assistants

ChatGPT · Claude · MCP

Requires activation and personal access

Ask about the store and perform supported work from an AI assistant. Tools follow the user, role, store, modules and agent policy.

Data and direction
The assistant reads information and sends supported actions to Kaduno. Data received by the assistant is processed by the assistant provider.
Ownership and limits
Kaduno controls access to store data; the assistant grants no extra permissions. Not every admin function has a corresponding tool. Confirmations and client support must be checked.
Before you start
An administrator enables the interface. Each person connects with their own account or a scoped agent key. Check the store and test reads before writes.
Operations and error handling
For missing tools, check role, store, modules and policy. Check the result before repeating an external write. Access can be revoked.

Custom integrations

API · Webhooks

Requires integration development

Build your own workflows around Kaduno’s documented interfaces. The API reference describes fields, operations and limits.

Data and direction
Use the REST API for supported reads and writes. Webhooks send events to a receiver you operate. An event is not a complete synchronisation by itself.
Ownership and limits
Agree which system owns each field, the direction of data flow and conflict handling. An available API does not mean a ready-made connector exists.
Before you start
Grant only necessary access, keep keys server-side and test with sample data. Plan logging, data mapping and operations before production.
Operations and error handling
The receiver must verify signatures and handle repeated deliveries. Agree monitoring, alerts and who resolves errors on each side of the integration.

Working with another system?

Bring the system name, intended workflow and the data you want to exchange. We’ll clarify whether a suitable connection exists or requires development. New connections are not presented as available before they are verified.