Skip to content
CRM ⇄ E-commerce

Kommo to Nuorder integration — real-time, two-way sync

Keep Kommo and Nuorder in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.

  • SOC 2 and 6 other compliance frameworks
  • POC with real engineers in minutes

Adopted by fast-scaling companies moving mission-critical data in real time

Case study
Migrated from MuleSoft
Case study
Migrated from Celigo
Migrated from Heroku Connect
Migrated from Matillion
Case study
Migrated from Fivetran
Case study
Migrated from Celigo
Why teams connect Kommo and Nuorder

Keep the customers and orders that Kommo and Nuorder share aligned in real time, so sales works from live purchase history and the store works from current account details.

Kommo holds the customer relationship: the contacts, accounts, and deals a go-to-market team works. Nuorder runs the buying side: who placed which order, what they bought, and where it ships. The two describe the same people and companies, and when they are connected only by exports, sales answers questions without recent orders in front of them while the store works from account details that changed weeks ago.

Stacksync links Companies, Pipelines & Statuses, Tasks, Notes in Kommo to Products, Orders, Companies, Line Items in Nuorder with bi-directional, real-time sync. New customers, order activity, and corrected contact details move in whichever direction you configure, field by field, with conflicts resolved by rules you set. A record created or changed on either side shows up on the other within seconds, with no CSV exports and no nightly job.

The shared entity is the customer, matched on email or an external ID, so both systems agree on who the buyer is and the order history sits next to the relationship instead of in a separate tab.

Common use cases

  • 01 Mirror pipeline stage changes into BI tools for forecasting
  • 02 Route leads that originate in WhatsApp or Instagram conversations into other systems of record
  • 03 Sync Inventory / ATS levels from a warehouse or ERP into NuORDER via /api/inventory/{id} so buyers see accurate available-to-sell quantities and oversell drops.
  • 04 Two-way sync Companies (retail accounts) between NuORDER and a CRM so buyers created in either system stay aligned on customer master data.

Common sync patterns

Where Nuorder records orders: purchase history on the account

Orders and their status from Nuorder appear on the matching contact or account in Kommo, so reps see what a customer has bought and what is in flight before the next conversation.

New buyers become CRM records

A customer created in Nuorder creates or updates the matching contact or account in Kommo, so first-time and repeat buyers land in the relationship system without a manual import.

Contact and address details stay consistent

An email, phone, or shipping and billing address corrected in either system updates the other, so the next order and the next outreach both use current information.

What you can sync between Kommo and Nuorder

Representative objects on each side — any object or custom field can map to any target. Schemas are auto-detected; types are converted between the two systems.

Kommo objects Nuorder objects How this pairing syncs
Companies Organization records map to accounts in ERPs and invoicing tools. Companies Retailer and customer accounts (buyers, doors); enumerated via /api/companies/codes/list and created through the customer-creation API, commonly synced with a CRM or ERP. Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions. Custom fields on either side are included in the mapping.
Notes Free-text and system notes attach context to synced leads and contacts. Products Fluent-schema catalog records (style, SKU, images, custom fields); brands push them in via /api/product/new (POST) and update via /api/product/{id} (PUT), typically mastered in a PIM or ERP. Notes is specific to Kommo and Products to Nuorder — each maps to any object or custom field on the other side.
Custom Fields Per-entity custom fields hold data written from external databases and enrichment. Orders Wholesale sales orders with nested line items and payment info; read via /api/orders/{status}/detail, created via /api/order/new (PUT), and advanced via /api/order/{id}/process and /cancel. Custom Fields is specific to Kommo and Orders to Nuorder — each maps to any object or custom field on the other side.
Users Account users map lead ownership to people in other systems. Line Items SKU, quantity, and price rows nested inside each Order; the unit ERPs and fulfillment systems consume when an order is written out. Users is specific to Kommo and Line Items to Nuorder — each maps to any object or custom field on the other side.
Chats Messenger conversations from WhatsApp, Instagram, and other channels attach to leads and contacts. Inventory (ATS) Available-to-sell stock levels updated via /api/inventory/{id} (PUT); usually written from a warehouse or ERP into NuORDER so buyers see accurate availability. Chats is specific to Kommo and Inventory (ATS) to Nuorder — each maps to any object or custom field on the other side.
Leads The central pipeline record; external signups and form fills sync in as leads. Pricing / Price Lists Wholesale and retail price data attached to products through the product data feeds; read out for margin reporting or written in during catalog loads. Leads is specific to Kommo and Pricing / Price Lists to Nuorder — each maps to any object or custom field on the other side.

How changes propagate between Kommo and Nuorder

Each direction of the sync is driven by what the source system can signal and what the destination accepts — detection, delivery, and expected latency below.

Kommo Nuorder Sub-second propagation

DetectionKommo notifies Stacksync of record changes through webhook events. Webhooks on record add and update events, plus polling for backfill.

DeliveryEach detected change is written to Nuorder through its API, with automatic retries and rate-limit backoff.

Nuorder Kommo Interval-based propagation

DetectionStacksync polls Nuorder for changes on an incremental schedule, reading only records changed since the previous pass. Polling on modified date: a date-range order endpoint returns the IDs of orders changed within a UTC start/end window.

DeliveryEach detected change is written to Kommo through its API, with automatic retries and rate-limit backoff.

Rate-limit considerations

  • Kommo: Subject to per-account request rate limits.
  • Nuorder: Results are cursor-paginated via lastId/lastValue exposed in a 'next' response header (null on the last page); published request-rate limits are not documented and are governed per integration.
What ships with Kommo ⇄ Nuorder

Connect Kommo and Nuorder for flexible, real-time data sync.

Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Kommo–Nuorder connection.

Real-time

Two-way sync

Changes in Kommo or Nuorder instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever Kommo or Nuorder data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.

At scale

Event queues

Handle millions of events per minute without losing a single Kommo or Nuorder record.

Observability

Monitoring

Track your Kommo ⇄ Nuorder sync health, view errors, and replay failed events in one click.

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between Kommo and Nuorder.

How the Kommo and Nuorder connectors work

Kommo

Integration surface
REST API
Authentication
OAuth 2.0 with refresh tokens
Change detection
Webhooks on record add and update events, plus polling for backfill
Capabilities
read · write · webhooks
Rate limits
Subject to per-account request rate limits

Nuorder

Integration surface
REST API (JSON), with optional SFTP flat-file data feeds
Authentication
OAuth 1.0 — consumer key/secret plus an access token/secret issued per approved application in the NuORDER Portal (Admin > Settings > API Management > Approved Applications)
Change detection
Polling on modified date: a date-range order endpoint returns the IDs of orders changed within a UTC start/end window; products and customers are pulled by last-modified date. No native webhooks.
Capabilities
read · write
Rate limits
Results are cursor-paginated via lastId/lastValue exposed in a 'next' response header (null on the last page); published request-rate limits are not documented and are governed per integration.
How it works

How to connect Kommo to Nuorder — three steps, no code

Configure and sync within minutes, no code. Whether you sync 50k or 100M+ records, Stacksync handles the queues, infra, and plumbing. Integrations are non-invasive and need zero setup on your systems.

  1. 01

    Connect your apps

    Authenticate Kommo and Nuorder with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.

    • OAuth 2.0
    • SSH tunnel
    • VPC peering
    Kommo connected
    Nuorder connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Kommo and Nuorder objects to sync — Stacksync auto-detects both schemas, including custom fields where the platform exposes them. Sync to existing tables, or let Stacksync create new ones with ideal data types.

    • Standard objects
    • Custom objects
    • Auto-schema
    objects · Kommo ⇄ Nuorder
    Customers 12,480
    Sales Orders 8,213
    Invoices 5,902
    Items 1,344
  3. 03

    Map fields

    Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.

    • Auto-map
    • Type casting
    • Transforms
    Kommo Nuorder
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
Try interactive demo
FAQ

Kommo and Nuorder integration FAQ

SECURITY

Security teams trust Stacksync

As a data company, we understand the importance of keeping your data secure. Stacksync is built with security best practices to keep your data safe at every layer, and is DPF-certified for US, EU, UK and CH data transfers.

Learn more about security
SOC 2 Type II
ISO 27001
HIPAA BAA
GDPR
CCPA
DPF US-EU-UK-CH
→ SECURITY WITH BENEFITS

SSO & SCIM

Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.

Alerts

Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.

Secure connection options

Securely connects to your systems with:

OAuth 2 SSH Tunnelling SSL certificates IP Whitelisting VPN gateway VPC peering and more

Related integrations

Every pair below is a real-time, two-way sync. Search all 381 integrations available for Kommo and Nuorder.

Popular · 7 of 381
All Kommo integrations All Nuorder integrations Browse all integrations
Coworkers laughing in front of a laptop in a casual office setting

Your last integration took months.
Your next one takes a prompt.

Book a demo Tour the platform on your own